At 12/31/01 12:01 PM, "Nick Riemondi" <[EMAIL PROTECTED]> wrote:
>First off, thank all of you immensely for your help. I have actually >created my own problem and it brings up a general set up issue for virtual >domains. > >I'm hosting many, many domains... and I need to keep them seperate because >everyone wants an info@mydomain, etc. > >My problem is I used "[EMAIL PROTECTED]" as the login field (I'm using >pgsqlauth), and alot of email clients REFUSE to let you enter an @ sign in >the username field (Netscape Communicator 4, Outlook on Mac, etc). I >realize I could just have easily made the login name "user.domain.com", >and then create aliases to the local accounts: >[EMAIL PROTECTED]: user.domain.com >I just wanted to ask: > >1) if there's a way around this (by sending some other character Courier >will interpret as an @ sign), >2) how other's have accomplished this. You could have multiple schemes in operation at the same time. For each user, I have two entries in my /etc/userdb: [EMAIL PROTECTED] home=... domain.com-user home=... All the other information for each pair is identical (the userdb gets regenerated from a database, so it's no big deal to maintain -- I just have a perl script that creates two separate userdb lines for each database entry. Note, however, you can no longer use the standard Courier tools to do things like change passwords in the userdb.dat file... but if it's all in a database, you don't need to). That way the users can use either one when they login, and you can give instructions as appropriate. (I tell 'em to use domain.com-user in their e-mail client, yet they can still use [EMAIL PROTECTED] for SqWebmail, for example.) -- Robert L Mathews, Tiger Technologies _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
