Markus Berger writes:
Evidence, well....I was forwarded one mail, where our marketing guy and somebody external have been addressed. The marketing guy did not receive the mail, while the other person did. I would not try to dare asking for their server logs, since the person which sent the mail which we did not receive is a business partner, and it would be an unprofessional manner if I contact one of our investors asking for their mail server logs. So all what I have is a forwarded mail, addressed to 2 persons, and one person (which uses our mailserver) did not receive the mail. I checked from that day on all mail.log mail.warn and mail.err , but there is not even any hint about this mail...Okay, you might say, the mail has never arrived at our server (that was also my guess the first times when this happened). But since we have at least 1 case per week where people wrote us, and the mail never arrived (in addition the sender never received any error or reject mail), I personally think it is a bit suspicious.
There's nothing suspicious about it. Email has never been, and will never be, a 100% reliable message delivery platform.
If the mail logs show no trace of any connection attempts, then no connection attempts have been made. As soon as a connection attempt is received, it gets logged. If you're searching by email address, it's possible that some error occured before the sender's address as provided, so all the logs would show is the sender's IP address. You'll need to obtain the sender's IP addresses and search your logs for them.
It is the sender's responsibility to accurately report mail delivery failures. If the sender's mail server is unable to deliver its mail, it should return a non-delivery notice. It is the sender's responsibility to report delivery errors, not the recipient's.
And if the sender was left with the impression that the message was succesfully set, it would've been logged plentifully. Log messages would've been made long before the sender went anywhere near the final stages of mail delivery.
There's only a very limited set of circumstances that could possibly fit all the information you stated:
1) The sender's mail server was not able to connect, or deliver the message. The sender did not configure a correct return address, as such the sender did not receive a bounce. It is the sender's responsibility to make sure their mail software supplies a correct, deliverable, return address to which all undeliverable mail gets returned.
2) The sender's mail server cannot deliver mail due to some error condition that's considered temporary in nature, so the sending mail server keeps trying, periodically, until the message expires. The message is still queued up and the sender keeps trying, so any non-delivery notice has not been generated yet. Courier's default queue expiration is, for example, one week, so if you send a message and it could not be delivered immediately for reasons that are considered transient, Courier will not return it, as undeliverable, until a week goes by.
I can't think of any other possibilities.
pgpOcBz5Xf4U8.pgp
Description: PGP signature
------------------------------------------------------------------------------
_______________________________________________ courier-users mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
