So after using Courier for personal use over many years I finally convinced my current company to allow me to replace our exchange server with a Courier implementation. I have found a couple issues in 'enterprise' use that I'm hoping to resolve.
1) Backscatter suppression on Aliased accounts If one account in an alias that points to a group of accounts has a local delivery issue, the entire alias gets shut down by backscatter suppression. While this may seem to be a reasonable thing to do, the net effect is that one stupid engineer can bork the entire emergency mail alias with a bad mailfilter rule. It would be nice if there was some way to isolate this behavior without having to disable backscatter suppression entirely. I know aliases work like a blind mailing list, so an error on one account in the group means the server has to send a delivery notice for the mail itself, but perhaps there is a more elegant way to handle this kind of thing for aliases that need to be 'high availability.' Some sort of alias indirection trick would be acceptable here. 2) "Local" aliases [email protected], [email protected], etc.. are extremely handy sorts of aliases. I know that you can create 'local' aliases, but they don't work in the way I was hoping, in that they would be accessible to smtp users 'local' to the server. I think what I really am asking for is an smtp-auth set of aliases that only work for authenticated smtp users, which I realize I can set up with some clever global filters, but must have broad enough applicability that it might be nice if it were a built in feature. Something like "makealiases -protocol=esmtp-auth" would be very useful. I know a mailing list would probably be the standard solution, but that's a lot heavier than what most non technical people would want. Correct me if I'm wrong here or I'm missing something obvious. 3) Mailfilters I realize that these are powerful and potentially dangerous, and attempting to protect people from themselves is usually an exercise in futility, but a BOFH option to case errors to do delivery to the default Maildir would be nicer than a tempfail in the case where the user doesn't know what they are doing. It takes the pressure off the BOFH having to watch the logs to see who is not getting mail and doesn't know it yet. Mail going in the default mailbox is a better clue that they are misconfigured than not getting mail at all for most users, and at least they aren't any worse off than when they started with no filtering. It also would eliminate them from doing potentially horrific things like blocking the emergency alias via backscatter suppression as outlined in my first comment. Please let me know if I'm missing some obvious configuration tweaks. I'm happy to try and create some patches for these things if there is not already simple solutions and the functionality is desired. ------------------------------------------------------------------------------ ThinkGeek and WIRED's GeekDad team up for the Ultimate GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the lucky parental unit. See the prize list and enter to win: http://p.sf.net/sfu/thinkgeek-promo _______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
