The problem isn't mail sent to valid addresses, it's mail sent to
non-existant ones. Normally they would be rejected by esmtpd, but when
you have a .courier-default alias they are accepted. ...
I suppose you have a couple of options. You could add some logic to your
courier-default file to check for a valid address in the new syntax and drop
the message if it's not valid. ...
Well, what I'm suggesting isn't as elegant, but it's simple. Create a .courier-default, and have it do what you want. In my case, my .courier-default looks at the extension (say, -courier), and tries to find an IMAP folder that contains that name, so all messages to my dash-extensions addresses automatically get written to the appropriate folder, nice and neatly sorted. (Dang, now I've blown my cover!)
Then, if one of the dash-extensions goes bad, (say, user-bigcorp), create a .courier-bigcorp which just... does nothing. The purists will argue that you should generate a dsn (bouncesaying), but if you've only ever used that addess with bigcorp; just update the address in bigcorp's records (or stop doing business with them!). This system works because the more specific .courier file always takes precedence, so the -default file won't even be consulted in this case.
best, Jeff
------------------------------------------------------- This SF.Net email is sponsored by: SourceForge.net Broadband Sign-up now for SourceForge Broadband and get the fastest 6.0/768 connection for only $19.95/mo for the first 3 months! http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
