In my tests what happens now is that your inbound Email, hits dbmail, the alias look up says that it has to invoke SMTP to send the message, so it's back to your SMTP server, which then turns around and sends it back to DBMail with the new address, which then, once again, invokes the SMTP to send the message to the forward location.
If the user_idnr is used in the deliver_to then the message is immediately stored in the database making it much more efficient. The only problem I have with the dbmail_aliases table is that there is no DB reference to a user_idnr. I added a column (called user_idnr) in dbmail_aliases, which is a foreign key reference to dbmail_users(user_idnr), and support cascade on delete. This way when I get rid of a user, everything goes. I also then have an easier way to tie them all together. The down side is that I have broken dbmail-users -a since I can't add an alias now, but I'm working on fixing that. -- David A. Niblett | email: [EMAIL PROTECTED] Network Administrator | Phone: (352) 334-3400 Gainesville Regional Utilities | Web: http://www.gru.net/ -----Original Message----- From: Matt Salerno [mailto:[EMAIL PROTECTED] Sent: Tuesday, June 14, 2005 10:42 AM To: DBMail mailinglist Subject: Re: [Dbmail] send mail to alias -> Real Account -> forward > That worked! > > I have already dropped my database, and I will rewrite the scripts for > the conversion. I will test it more and post back with results. > > Thanks for the assistance. > > Regards > My apologies for not completing my thought in the last e-mail, but does it make any sence to use the user_idnr in the deliver_to field? My guess is that if we use and e-mail address in the deliver_to field, dbmail sees it as a forward. How does this change the delivery path? _______________________________________________ Dbmail mailing list [email protected] https://mailman.fastxs.nl/mailman/listinfo/dbmail
