[quote user="Alar.Pandis@mtk.ut.ee"]
Hi!
Probably this is described already, but ...
So far we did use Pegasus with Novell NetWare (NDS mode). Now we have plans to setup mail system little bit differently and not rely on NDS mode. So, my plan is to install Pegasus (4.6.1) locally on every computer and user run it from there (using POP3 etc.), but they don't (and will not) have admin privileges, so. there is no option to save/update cfg-file in initial Pegasus dir. Also, is somehow possible to avoid this first dialog about mailbox location? I mean, lets after starting Pegasus create it by default under user profile? So, I mean, is there a option to automate Pegasus mailbox etc. conf?
More thanks, Alar.[/quote]
AFAIK the problem of running PM in a Netware environment is that it automaticaly detects Netware (PM on the server or on the computer gives the same result.
The solution is to add -A to the target in the shortcut options, this forces PM to ignore Netware connections.
[quote]
For example, when Pmail.cfg could accept and use %USERPROFILE% in
mailbox location path ... wonderful! =)
Alar.
[/quote]
Unfortunatly it's not possible. The solution I use is to create users and their PM parameters via script. I've a template folder of a PM user, when I create a user I add his/her name to pmail.usr, I create his/her folder in the hierarchy, in the folder I've a pmail.ini file containing variables in place of the definitive value and change them via script (ie $user is replaced by the username etc) then I apply the correct ntfs rights.
You should also have only one installation of PM on the server (network installation) and put a shortcut to it on the shared desktop. Easier to do and to maintain.
Regards
[quote user="Alar.Pandis@mtk.ut.ee"]<font size="2">
</font><p><font size="2">Hi!
Probably this is described already</font><font face="Courier New" size="2"><font face="Courier New" size="2"><span lang="EN">, but ...
</span></font></font><font size="2"><span lang="ET">So far we did use Pegasus with Novell NetWare (NDS mode). Now we have plans to setup mail system little bit differently and not rely on NDS mode. So, my plan is to install Pegasus (4.6.1) locally on every computer and user run it from there (using POP3 etc.), but they don't (and will not) have admin privileges, so. there is no option to save/update cfg-file in initial Pegasus dir. Also, is somehow possible to avoid this first dialog about mailbox location? I mean, lets after starting Pegasus create it by default under user profile? So, I mean, is there a option to automate Pegasus mailbox etc. conf?
More thanks, Alar.</span></font>[/quote]</p><p>AFAIK the problem of running PM in a Netware environment is that it automaticaly detects Netware (PM on the server or on the computer gives the same result.</p><p>The solution is to add -A to the target in the shortcut options, this forces PM to ignore Netware connections.
</p><p>&nbsp;</p><p>&nbsp;[quote]</p><p>For example,&nbsp;when Pmail.cfg could accept and use %USERPROFILE% in
mailbox location path ... wonderful! =)
Alar. </p><p>[/quote] </p><p>Unfortunatly it's not possible. The solution I use is to create users and their PM parameters via script. I've a template folder of a PM user, when I create a user I add his/her name to pmail.usr, I create his/her folder in the hierarchy, in the folder I've a pmail.ini file containing variables in place of the definitive value and change them via script (ie $user is replaced by the username etc) then I apply the correct ntfs rights.</p><p>You should also have only one installation of PM on the server (network installation) and put a shortcut to it on the shared desktop. Easier to do and to maintain.</p><p>Regards
</p>