Marc, I see where you're going here, and I suppose we could add some better support for rewrites, because in many instances it makes sense that these go along with the user management rather than the 'domain management' of the MTA.
We could put this on list of items to do during 2.3 development. I would not like to add any sort of rewrite support to 2.2, however, because I think that's crossing the vague gray chasm that, say, @.domain support did not cross. More inline... On Tue, 2007-03-20 at 17:15 +0100, Marc Dirix wrote: > Yes your proposition works as stated for local users, however the to > adresses are external. > > So changing to the stated below works for now, but it is not convenient: > > alias | deliver_to > ------------------------------------------------------ > [EMAIL PROTECTED] |[EMAIL PROTECTED] > [EMAIL PROTECTED] |[EMAIL PROTECTED] > [EMAIL PROTECTED] |[EMAIL PROTECTED] > [EMAIL PROTECTED] |[EMAIL PROTECTED] These rewrites based on the local-part rather than the domain-part, but your first post was about rewriting domain-parts. The MTA is the right place to rewrite domain-parts. > I would also like this to work. > > alias | deliver_to > ------------------------------------------------------ > @foo.com |@bar.com > [EMAIL PROTECTED] |5 > [EMAIL PROTECTED] |5 > > Which is basically the same I'm trying but not external. This is exactly the domain rewrite I would expect to see in MTA configs. > > It does not really require much more address rewrite than it already > does, because sending to [EMAIL PROTECTED] > does deliver the mail to [EMAIL PROTECTED] which rewrites the > "to" address. Sort of, but not really. > However I'd expect it to also work in multiple lookups. Somehow it > rewrites too much or looses part of > the adress in the lookup, when there is an alias @foo.com => @bar.com. It doesn't rewrite anything, the deliver_to is used in place of the alias, verbatim, no rewrites involved. Aaron > Kind regards, > > marc > > Op 20-mrt-2007, om 16:48 heeft Aaron Stone het volgende geschreven: > > > The aliases are not rewrites. Deliveries can only target fully > > qualified > > addresses or user id numbers. > > > > I suspect that this would work (but I haven't tested it): > > > > alias | deliver_to > > ---------------------- > > @foo.com | @bar.com > > @bar.com | 5 > > > > Aaron > > > > > > On Tue, 2007-03-20 at 13:58 +0100, Marc Dirix wrote: > >> Hi > >> > >> > >> I have in my alias table the following setup: > >> > >> alias | deliver_to > >> ------------------------------------------------------ > >> @foo.com |@bar.com > >> [EMAIL PROTECTED] |[EMAIL PROTECTED] > >> [EMAIL PROTECTED] |[EMAIL PROTECTED] > >> > >> Now I get this in my Level4 log: > >> > >> Mar 20 13:39:09 hercules dbmail/lmtpd[22646]: Message incoming > >> connection from [10.0.0.7 (hephaestus.fw.cuci.nl)] by pid [22646] > >> Mar 20 13:39:22 hercules dbmail/lmtpd[22646]: Info Found > >> [EMAIL PROTECTED] of length [16] between '<' and '>' so next skip > >> [22] > >> Mar 20 13:39:27 hercules dbmail/lmtpd[22646]: Info Found > >> [EMAIL PROTECTED] of length [44] between '<' and '>' so next skip [48] > >> Mar 20 13:39:27 hercules dbmail/lmtpd[22646]: Info checking if > >> [EMAIL PROTECTED] is a valid username, alias, or catchall. > >> Mar 20 13:39:27 hercules dbmail/lmtpd[22646]: Info username not found > >> [EMAIL PROTECTED] > >> Mar 20 13:39:27 hercules dbmail/lmtpd[22646]: Info user > >> [EMAIL PROTECTED] checking for domain forwards. > >> Mar 20 13:39:27 hercules dbmail/lmtpd[22646]: Info delivering > >> [EMAIL PROTECTED] as a domain catchall. > >> Mar 20 13:40:31 hercules dbmail/lmtpd[22646]: Info delivering to [1] > >> external addresses > >> Mar 20 13:40:31 hercules dbmail/lmtpd[22646]: Message unable to parse > >> email address [EMAIL PROTECTED] > >> Mar 20 13:40:31 hercules dbmail/lmtpd[22646]: Message could not > >> prepare 'to' address. > >> > >> With internal delivery this does not seem to happen!!! > >> > >> > >> *** DBMAIL: dbmail-users version $Revision: 2416 $ Copyright (C) > >> 1999-2004 IC & S, [EMAIL PROTECTED] > >> > >> > >> Marc > >> _______________________________________________ > >> DBmail mailing list > >> [email protected] > >> https://mailman.fastxs.nl/mailman/listinfo/dbmail > > > > _______________________________________________ > > DBmail mailing list > > [email protected] > > https://mailman.fastxs.nl/mailman/listinfo/dbmail > > _______________________________________________ > DBmail mailing list > [email protected] > https://mailman.fastxs.nl/mailman/listinfo/dbmail _______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
