Chris Petersen wrote:
This doesn't solve your current problem since you've already done things this way, but I think a better way to do this in the future is to create an account called "[EMAIL PROTECTED]", and submit email addresses in the form of "[EMAIL PROTECTED]" (letting the .courier-default file send them to [EMAIL PROTECTED]). Or you could just use the hyphen trick with your regular email account (that's what I do).


Yes.  Unfortunately, I was doing this for a LONG time before I had even
heard about courier, let alone had the resources to run my own server.

I may start doing this, though. thanks for the reminder.

Couldn't you just put the filtering inside the .courier file for the alias account? Something like:


| echo $SENDER | grep -iE '\.[a-z]{2,4}$' &>/dev/null || exit 64
[EMAIL PROTECTED]

I think that last bit (exit 64) will make courier return the message to the sender as undeliverable if it doesn't match your regex. If you set it to 99, it'll just drop the message silently. Or at least that's what the dot-courier docs say:

"If the external command terminates with any of the following exit codes: 64, 65, 67, 68, 69, 70, 76, 77, 78, or 112, the E-mail message will be returned as undeliverable, and no further delivery instructions will take place."

Which makes me curious: Sam, what's the deal with those numbers? Do they have some meaning?

m.




------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. Does SourceForge.net help you be more productive? Does it help you create better code? SHARE THE LOVE, and help us help YOU! Click Here: http://sourceforge.net/donate/ _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users

Reply via email to