The following issue has been CLOSED ====================================================================== http://www.dbmail.org/mantis/view.php?id=860 ====================================================================== Reported By: Disconnect Assigned To: ====================================================================== Project: DBMail Issue ID: 860 Category: general delivery Reproducibility: have not tried Severity: minor Priority: normal Status: closed target: Resolution: won't fix Fixed in Version: ====================================================================== Date Submitted: 22-Sep-10 18:43 CEST Last Modified: 23-Sep-10 11:14 CEST ====================================================================== Summary: Domain wildcard (@foo.com) overrides user wildcard (user@) Description: Looking at issue 105, I should be able to have the following entries: joe -> joe@ jane -> @foo.com with "j...@foo.com" going to Jane, and "j...@foo.com" going to Joe. Instead, the more general @foo.com overrides the j...@.
Non-wildcard (j...@foo.com) overrides the wildcards, as expected. ====================================================================== ---------------------------------------------------------------------- (0003109) Disconnect (reporter) - 22-Sep-10 18:44 http://www.dbmail.org/mantis/view.php?id=860#c3109 ---------------------------------------------------------------------- Doesn't seem like it will let me edit, so updated description: Looking at issue 105, I should be able to have the following entries: joe -> joe@, j...@foo.com jane -> @foo.com "j...@foo.com" should go to Jane, and "j...@foo.com" should go to Joe. Instead, the more general @foo.com overrides the j...@. Non-wildcard (j...@foo.com) overrides all the wildcards, as expected. ---------------------------------------------------------------------- (0003110) paul (administrator) - 23-Sep-10 11:12 http://www.dbmail.org/mantis/view.php?id=860#c3110 ---------------------------------------------------------------------- I strongly disagree here. User wildcards are *not* more specific than domain wildcards. They are meant to be used as a relay of last-resort, and should be used sparingly. Assigning @example.com to a user, means that user should get all email for 'his' domain, no matter what mailbox part was specified. As a user I would be very unhappy to learn that some other user who (accidently) had a mailbox wildcard assigned to his account, started getting email that was destined for my domain! As a email hosting provider such a scenario would be cause for some serious PR headaches. What a nightmare. Finally, changing this kind of policy decision will create backward compatibility issues for current installations. Again nightmares ensue. Unless someone manages to convince me it is indeed necessary to do this, and do it gracefully, this is one change that's not going in. Issue History Date Modified Username Field Change ====================================================================== 22-Sep-10 18:43 Disconnect New Issue 22-Sep-10 18:44 Disconnect Note Added: 0003109 23-Sep-10 11:12 paul Note Added: 0003110 23-Sep-10 11:14 paul Status new => closed 23-Sep-10 11:14 paul Resolution open => won't fix 23-Sep-10 11:14 paul Category Database layer => general delivery ====================================================================== _______________________________________________ Dbmail-dev mailing list Dbmail-dev@dbmail.org http://mailman.fastxs.nl/cgi-bin/mailman/listinfo/dbmail-dev
