On Samstag, 16. Dezember 2006 09:36 Aaron Stone wrote: > The code in question leads to bug #477 that I just filed and fixed!
Oh good. > You will *crash* DBMail < 2.2.2 if your deliver_to field is in the > form 'username@' or '@domain'. With the fix in place, messages that > deliver to such an address will be dropped flat on the floor. Looking > at pipe.c, some more work is needed to let the forward state bubble > back up so that it can be reported via dbmail-smtp or LMTP. "will be dropped flat on the floor"? Does that mean it won't work? Then the official and supported way for domain aliases would be to create all aliases of all alias domains? So when I have [EMAIL PROTECTED] [EMAIL PROTECTED] [EMAIL PROTECTED] I need aliases [EMAIL PROTECTED] -> [EMAIL PROTECTED] [EMAIL PROTECTED] -> [EMAIL PROTECTED] [EMAIL PROTECTED] -> [EMAIL PROTECTED] and also [EMAIL PROTECTED] -> [EMAIL PROTECTED] [EMAIL PROTECTED] -> [EMAIL PROTECTED] [EMAIL PROTECTED] -> [EMAIL PROTECTED] and so on? That would create thousands of new alias entries for us - most customers have 3-15 alias domains, and sometimes 100 user entries.. mfg zmi -- // Michael Monnerie, Ing.BSc ----- http://it-management.at // Tel: 0676/846914666 .network.your.ideas. // PGP Key: "curl -s http://zmi.at/zmi3.asc | gpg --import" // Fingerprint: 44A3 C1EC B71E C71A B4C2 9AA6 C818 847C 55CB A4EE // Keyserver: www.keyserver.net Key-ID: 0x55CBA4EE
pgpy7CkH6glo2.pgp
Description: PGP signature
_______________________________________________ DBmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
