[quote user="dkocmoud"]

I don't understand why the original poster is not interested in using Mercury/32 to download the POP3 mail via Mercury/32's MercuryD module and have it placed into the public folder (once the next version ships, which supports delivering new mail to a public folder). [/quote]

euh... i'm not using Mercury because i'm using a other mailserver at this moment.  I know Mercury only by name... never installed it ...never seen it..
But... you made me curious ... just put my finger on the Mercury manual.... maybe i will install it and play around with it for a while

looking forward to the most intresting part (concerning this thread) ... dropping mail in a publc folder

This thread is closed for me, or resolved.

Most important things are :
Use public folders to share  mailfolders
Prevent that several users have access to a same mailbox at the time
Only share the new mail folder in a "add mailbox to list" option
Be aware that there is a "user training issue" involved

or keep it simple and
Start Pegasus Mail with the "-U <username>" commandline option to force Pegasus Mail to start up as that other user.
 

greetings and txs.

 

Hello,

I'm using Pegasus on a Novell network.  Each user has access to his own default-mailbox.

Is it possible to allow users to have access to different mailboxes. (or shared mailfolders ?)

Use public folders for this - go to Tools|Public folders for more info. The help is quite extensive.

As an aside, one of the new features in Mercury/32 v4.5 (which really *will* be out very soon now) is the ability to deliver mail directly into Pegasus Mail public folders via aliases.

Cheers!

-- David --

As an alternative to the public folder option (which is btw best suited for the job): <?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" />

1.  Create a new folder somewhere on the Netware server. Make sure the users (or groups) have file system access to this folder. 

From Pegasus: Folders, Add mailbox to list, Directory path, <enter the path of the directory you just created> and give the mailbox a name

I've got such ‘shared’ mailboxes for multiple groups of users. They can create folders, share e-mail etc. You can’t use filing trays though.

2.  In the same way you can add an extra mailbox that point to another user’s default mail directory.

As long as the user that tries to access the mailbox got sufficient file system rights that works just fine:

From Pegasus: Folders, Add mailbox to list, Username, <enter the full NDS username> and give the mailbox a name

If you simply want to connect to another user's mailbox (whether in one of the NetWare modes or in multi-user standalone mode), you can do that via 2 different ways:

* You can mount their mailbox within your Pegasus Mail session via the Folders -> Add Mailbox To List... menu option, then select the Username radio button and type in the other user's username; or

* Start Pegasus Mail with the "-U <username>" commandline option to force Pegasus Mail to start up as that other user.  For multi-user standalone mode, use the "-i <username>" commandline option instead.

Of course you will need file rights to the other user's mailbox and (for NetWare Bindery or NDS mode) you will need to be a member of the BECOME group (in NDS mode, this group should be created within your OU).

[quote user="NetwareRulez"]

As an alternative to the public folder option (which is btw best suited for the job): 

1.  Create a new folder somewhere on the Netware server. Make sure the users (or groups) have file system access to this folder. From Pegasus: Folders, Add mailbox to list, Directory path, <enter the path of the directory you just created> and give the mailbox a name. I've got such ‘shared’ mailboxes for multiple groups of users. They can create folders, share e-mail etc. You can’t use filing trays though.

Thanks for the feedback David!   I guess I'm just lucky not having any kinda problems over all these years.....  I'll keep my fingers crossed and wait for Merc 4.5

Ron

[quote user="NetwareRulez"]

2.  In the same way you can add an extra mailbox that point to another user’s default mail directory.

As long as the user that tries to access the mailbox got sufficient file system rights that works just fine:

From Pegasus: Folders, Add mailbox to list, Username, <enter the full NDS username> and give the mailbox a name

[/quote]

txs. this was just the solution I'm looking for.

Now UserA has access to the mailbox of userB.
Is it also possible that UserA gets a new-mail notification if UserB gets newmail ?

just recieve a notification... so it's Ok.

[quote user="NetwareRulez"]

As an alternative to the public folder option (which is btw best suited for the job): 

1.  Create a new folder somewhere on the Netware server. Make sure the users (or groups) have file system access to this folder. 

From Pegasus: Folders, Add mailbox to list, Directory path, <enter the path of the directory you just created> and give the mailbox a name

I've got such ‘shared’ mailboxes for multiple groups of users. They can create folders, share e-mail etc. You can’t use filing trays though.

[/quote]

 Ok, but David wrote :

"This really isn't a good idea, and will lead to folder damage and/or loss of data eventually.  "
So this is not a option.
 
[quote user="NetwareRulez"]

2.  In the same way you can add an extra mailbox that point to another user’s default mail directory.

As long as the user that tries to access the mailbox got sufficient file system rights that works just fine:

From Pegasus: Folders, Add mailbox to list, Username, <enter the full NDS username> and give the mailbox a name

[/quote]

Is this a good option, or should it also be avoid ?

the public folder option isn't useable because there is no direct delivery on a public mail folder 

Please note that whenever you access another mailbox (whether it be another user's mailbox or just a folder on a server's shared drive somewhere), you need to make sure that only one person at a time is accessing that mailbox.  In these terms, then, it can be a good option if you are checking mail for another employee who is out sick, but it would be bad if 2 or more users are actively modifying and deleting emails from the same mail folders within the same mailbox simultaneously.  Many folks have said they've been lucky to not have had any problems yet, but they may be playing with fire.

Concerning the public folder delivery from Mercury/32, this will be supported in v4.5.  From the help file concerning the Aliases feature of Mercury/32:

Public folder aliases

Mercury's companion mail client, Pegasus Mail, supports the idea of Public Folders - folders that can be accessed by more than one user at a time. Mercury can deliver mail directly into Pegasus Mail's public folders in the proper format, ready to read. To allow Mercury to do this, you need to create an alias for each public folder to which delivery is to be enabled. The alias type for public folders is PUBLIC:, followed by the full path to the directory. So, if you have a public folder in P:\PUBLIC\MAIL1, and want any message sent to public1@example.com to be delivered automatically into that folder, you would create this alias:

public1@example.com = PUBLIC:p:\public\mail1

txs for your reply....

so this way is only a fine option if i'm sure this mailboxes only will be used by 1 person at the time. (and i'm not sure of this...)
I'm also not using (and have no intentions to do this) Mercury... so the v4.5 is also not a option.

is this possible :
I create a new shared folder something like Public\mailfolder\shared for user1,User2,...User5
I activate the multipop for user1, user2...user 5 extention and set "Pace mail in  : Public\mailfolder\shared"

is this possible ?
 

[quote user="tsar"]

txs for your reply....

so this way is only a fine option if i'm sure this mailboxes only will be used by 1 person at the time. (and i'm not sure of this...)
I'm also not using (and have no intentions to do this) Mercury... so the v4.5 is also not a option.

is this possible :
I create a new shared folder something like Public\mailfolder\shared for user1,User2,...User5
I activate the multipop for user1, user2...user 5 extention and set "Pace mail in  : Public\mailfolder\shared"

is this possible ?


[/quote]

seems this will not work like it should  :-(

how should i solve this out:

we are receiving a lot of mail addressed to ourl contact@mydomain.com. It's important for us that we make asap a reply on every recieved mail.  (a autorespond message is not a option).

Most of the time UserA is collection this mail on his mailbox.
If userA is in a meeting (or his is not here, or he is talking a break, or....) UserB should do the follow up of this mail.

A public folder seems a good idea but pegasus can't drop new mail in a public folder, adding a user's mailbox is only possible if i'm sure that only 1 user at the time is using this box, so neither this is a  option...

other suggestions ? 

Though I wouldn't dare to argue simultanious mailbox access can (and as David told us -will-) lead to damaged folders, I'm using it for many years without any kind of problems, folder damage or data loss. Of course I could just be extermely lucky, but could it be if you only 'share' the New mail folder folder damage cannot occur, because the new mail folder isn't a real mail folder ?

[quote user="NetwareRulez"]

could it be if you only 'share' the New mail folder folder damage cannot occur, because the new mail folder isn't a real mail folder ?

[/quote]

Yes, you can share the new mail folder with reasonable safety, but not any other folder in a user's mailbox.

Cheers!

-- David --

euh... maybe a silly question...but...

and how can i share this new mail folder ? without all other folders in a user's mailbox

AFAIK you can't. Indeed, you'll get all folders

Correct. This is a user training issue.  Of course, if you don't have any other folders in that mailbox other than the inbox itself, then there's no issue.  ;-)

I don't understand why the original poster is not interested in using Mercury/32 to download the POP3 mail via Mercury/32's MercuryD module and have it placed into the public folder (once the next version ships, which supports delivering new mail to a public folder).