Christian G. Warden wrote: > The destination mailbox doesn't have to be hard-coded into the MTA. For > example, I configured a transport (Exim) that takes addresses of the > form /username~mailbox/ and delivers them to the correct mailbox using > dbmail-smtp. The mailbox to deliver to is the result of a > user-configurable filter which is stored in the users table in the > database.
It is not always easy to retrieve such delivery-oriented configuration data at transport time. As an example: You can use DBMail to easily build mail-reflectors. You can insert multiple rows into the table 'aliases' with the same 'alias' but different destinations to 'deliver_to'. DBMail will duplicate a mail to such an alias and deliver it to all destinations/users. These users can have different settings (should headers be added, should headers or body be modified, in which folder should 'spam suspects' be delivered, ...). Which of these users' settings should be applied at transport time? At this point of time it is still only one message. The duplication process later on is completely unknown to the MTA. >>Finally, as I mentioned, I have no experience with IMAP, so should a >>spam mailbox be called 'Spam', '/Spam', or something else? > 'Spam' is fine, or 'Quarantine/Spam' or similar. Maybe it should be user-configurable? Best regards, Michael P.S.: Sorry to the list-admin for previously sending two (now obsolete) mails with the wrong from-address.
