PMAIL.USR is required when you use Pegasus Mail in multiuser mode (or network mode which is the same but the mail directory structure is then located on a share on the network). PMAIL.USR does not exist when you run Pegasus Mail in standalone mode, as there is only *one* user.
PMAIL.USR records the names of the users (not identities) who have a mail directory on the system. PMAIL.USR is a text file whom structure is :
U (or A);username;fullname :
- U for a 'normal' user, A for an admin (the guys who can add users if the FS allows them to write in this directory)
- username: what you type to be identified by Pegasus Mail
- full name: what you see when you click on Adresses/Local users
PMAIL.USR has nothing to do with the rights to read/modify the mail structure, these rights are given by the fs. A mail directory structure can be as follow (3 users):
Mail\pmail.usr
\admin
\user1
\user2
Where pmail.usr is :
A;admin;mail administrator
U;user1; full name of user1
U;user2; full name of user2
Admin has the right 'modify' on the structure
user1 has the rights 'read' on pmail.user and 'modify' on the content of Mail\user1
user2 has the rights 'read' on pmail.user and 'modify' on the content of Mail\user2
if you want user1 to be able to send mails to user2 using the mail transport included in Pegasus Mail you have to give him the right 'add files' on Mail\user2, a better solution is to create a group including the mail users and to give the right 'add file' on each user mail directory and the right 'read' on PMAIL.USR to that group
HTH
<p>PMAIL.USR is required when you use Pegasus Mail in multiuser mode (or network mode which is the same but the mail directory structure is then located on a share on the network). PMAIL.USR does not exist when you run Pegasus Mail in standalone mode, as there is only *one* user.
</p><p>PMAIL.USR records the names of the users (not identities) who have a mail directory on the system. PMAIL.USR is a text file whom structure is :</p><p>U (or A);username;fullname : </p><ul><li>U for a 'normal' user, A for an admin (the guys who can add users if the FS allows them to write in this directory)</li><li>username: what you type to be identified by Pegasus Mail</li><li> full name: what you see when you click on Adresses/Local users</li></ul><p>PMAIL.USR has nothing to do with&nbsp; the rights to read/modify the mail structure, these rights are given by the fs. A mail directory structure can be as follow (3 users):</p><p><i>Mail\pmail.usr</i></p><p><i>&nbsp; &nbsp; &nbsp; \admin</i></p><p><i></i><i>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \user1</i></p><p><i>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; \user2 </i></p><p><i> </i></p><p>Where pmail.usr is :</p><p><i>A;admin;mail administrator</i></p><p><i>U;user1; full name of user1</i></p><p><i>U;user2; full name of user2</i></p><p>Admin has the right 'modify' on the structure</p><p>user1 has the rights 'read' on pmail.user and 'modify' on the content of&nbsp; Mail\user1</p><p>user2 has the rights 'read' on pmail.user and 'modify' on the content of&nbsp; Mail\user2</p><p>if you want user1 to be able to send mails to user2 using the mail transport included in Pegasus Mail you have to give him the right 'add files' on&nbsp; Mail\user2, a better solution is to create a group including the mail users and to give the right 'add file' on each user mail directory and the right 'read' on PMAIL.USR to that group
</p><p>HTH
</p>