Would you also want to handle username forwards? For example:
@domain -> username@
squashes all [EMAIL PROTECTED], [EMAIL PROTECTED] down to [EMAIL PROTECTED]
This can already be done, doesn't it?
An alias @domain -> [EMAIL PROTECTED] replaces everything not?
username@ -> otherusername@
changes any instance of username to otherusername.
I can't see this being usefull for any service provider. Maybe in a
setup with multiple domains but
only 1 client. However this might also be done with multiple lookups:
@domain1 -> @domain
@domain2 -> @domain
[EMAIL PROTECTED] -> 3245
[EMAIL PROTECTED] -> 3245
What would you do about +mailbox subaddressing? Just leave it on
there?
Kept as is, if possible.
At what point are we writing too many special cases, and should
instead
just do some kind of regular expression replacement? This was
something we
talked about doing for 2.2 but didn't have time to get done. I
suppose we
can put it back on the todo list...
Basically my *only* need at the moment is doing domain rewrites.
@domain -> @domain2 with keep everything before the @ in takt.
That way I can have a client with multiple domains, and only having
to define users for 1 domain.
Marc
_______________________________________________
DBmail mailing list
[email protected]
https://mailman.fastxs.nl/mailman/listinfo/dbmail
