just clue anyone who cares in on my fix... My server (for example) is
mail.mxdomain.com, so I first set the default domain in authpgsqlrc
DEFAULT_DOMAIN mail.mxdomain.com
I wrote scripts to do everything, so if a user is marked to login with
prefix.domain.com instead of [EMAIL PROTECTED] I create an alias:
[EMAIL PROTECTED]: [EMAIL PROTECTED]
and in my postgres database the login which would have been
[EMAIL PROTECTED] is now [EMAIL PROTECTED] It works
great.
Only problem I've noticed is with squirrelmail. It authenticates them
fine if they login with prefix.domain.com, but when they try to send mail
it tries to send from prefix.domain.com, which doesn't work. BUT, if they
login as [EMAIL PROTECTED] (geez that's long)... it
works fine. I haven't looked yet, but I assume I can easily get in there
and fix that.
Thanks for all the help / insight.
Nick
[EMAIL PROTECTED] writes:
>We use the asterisk. ("*") It works fine for those clients that have had
>the issues, namely, Outlook for Mac. We also use Postgres on the
>backend,
>however, we only use Courier for the IMAP and POP services. We use Qmail
>for the routing, and the users/assign is generated by a perl script the
>dumps the pgsql table used by IMAP & POP. Inbound SMTP-AUTH
>authenticates
>against this same pgsql table. Additionally we use TWIG and
>a locally customized version of IMP (easy changes, really) for web access.
>
>YMMV.
>
>-John
-=-=-=-=-=-=-=-
Nick Riemondi
OuterScape
[EMAIL PROTECTED]
451-0535
_______________________________________________
courier-users mailing list
[EMAIL PROTECTED]
Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
