I sent you the log file as you requested. I did some further investigation after reading that log, and now fully understand what is happening, I just don't know how to fix it. After changing the logging options as you suggested I did two tests:
Test 1: (aswMaiSv.log at 08/16/05 18:44:42)
I sent an email to ***@msn.com with avast! enabled. The msn server responded with: <-SMTP 550 Requested action not taken: mailbox unavailable
avast! changed that error to <-SMTP 503 Need Rcpt command. and the email was returned to me.
When I disabled avast! and resent the message I got the correct failure back (<-SMTP 550 Requested action not taken: mailbox unavailable)
Test 2:(aswMailSv.log at 08/16/05 18:53:40)
I sent an email to ***@HealthComptpa.com with avast! enabled. TheHealthComptpa server responded with: <-SMTP 451 4.7.1 message delayed, see
http://projects.puremagic.com/greylisting ; Please try again later
I read through the white paper located at that url (it's really informative) and now understand what is happening.
avast! changed that error to <-SMTP 454 4.5.0 no valid recipients given. and the email was returned to me so my computer interprets that as a permanent failure so it doesn't try to resend it like greylisting assumes it will.
When I disabled avast! and resent the message my computer got the correct failure back (<-SMTP 451 4.7.1 message delayed) and resent it and it was delivered successfully like greylisting assumes will happen.
Question: Why is avast! changing the error code the server sends back? Thank you for your response.