Hello,
What you're wanting isn't currently supported in dbmail as,
as you mentioned, there is no "default domain" type setting.
We had a quite similar need for that here (to ease migration
from "user" userids to "[EMAIL PROTECTED]" style) and wrote a small
patch to auth_{,md5_}validate() to lookup a user_idnr from a
usermap table if the userid wasn't found in the users table.
Ie. you would put "[EMAIL PROTECTED]" in the users table and make
a "user" entry in the usermap table pointing to the right
user_idnr. It's just a hack though - it'd be nice to have
something natively supported in dbmail for a default domain
to append to usernames w/o one. You could also use it to
support user%domain entries by just adding those in, too.
I'll post it here if you'd like to try it, but again, it's just
a hack that may need changed from time to time as dbmail evolves
(ie. if the patch doesn't apply cleanly). We're just using it
for a migration period and plan to drop it eventually. It's not
been tested under mysql, just postgres, but it should work fine.
:)
Jesse
---- Original Message ----
From: Michael Shuler <[email protected]>
To: <[email protected]>
Subject: [Dbmail] Virtual Domain Login Issues
Sent: Thu, 15 May 2003 23:49:53 -0500
> We are trying to migrate from Communigate Pro to Postfix+dbmail+MySQL. When
> I was testing dbmail it was originaly with only one domain, eveything worked
> great. I ran into a snag when I added a second domain because I could no
> longer just put in only the username without the domain; otherwise the
> username could not be repeated i.e. [EMAIL PROTECTED] and
> [EMAIL PROTECTED] would just be sales (how would it know which was which
> was for which domain?). I want users from mydomainA.com to be able to login
> using only their username OR their [EMAIL PROTECTED] I want users
> from mydomainB.com (and any future domains) to be able to login only as
> [EMAIL PROTECTED] (or whatever the new domain name is). I also need
> the ability for them to use a % instead of an @ (stupid Communigate Pro
> limitation but 10K+ people already have it in their outlook settings so it
> would be nice to have). It seems that the dbmail's IMAP and POP servers
> don't support the concept of a default domain if one is not specified in the
> login username and I can't figure out a way around this... Any help would
> be greatly appreciated.
>
>
> Here is a quick dump of my users table:
> +-----------+-------------------------+----------+-------------+------------
> --+-----------------+---------------------+
> | user_idnr | userid | passwd | client_idnr |
> maxmail_size | encryption_type | last_login |
> +-----------+-------------------------+----------+-------------+------------
> --+-----------------+---------------------+
> | 1 | [EMAIL PROTECTED] | password | 0 |
> 0 | | 2003-05-15 21:50:13 |
> | 2 | [EMAIL PROTECTED] | password | 0 |
> 0 | | 2003-05-15 21:49:56 |
> +-----------+-------------------------+----------+-------------+------------
> --+-----------------+---------------------+
>
> And my aliases table:
> +------------+--------------------------+------------+-------------+
> | alias_idnr | alias | deliver_to | client_idnr |
> +------------+--------------------------+------------+-------------+
> | 1 | [EMAIL PROTECTED] | 1 | 0 |
> | 2 | [EMAIL PROTECTED] | 1 | 0 |
> | 3 | [EMAIL PROTECTED] | 1 | 0 |
> | 4 | [EMAIL PROTECTED] | 2 | 0 |
> +------------+--------------------------+------------+-------------+
>
>
>
> Thanks in advance!
>
> PS: SMTP deliver seems to work with the above tables.
>
> ----------------------------------------
>
> Michael Shuler
>
> _______________________________________________
> Dbmail mailing list
> [email protected]
> https://mailman.fastxs.nl/mailman/listinfo/dbmail
>
-- End Original Message --
--
Jesse Norell
jesse (at) kci.net
