Thanks Sam, that is very informative!
I guess what I'm struggling with is the ability to actually correlate all that stuff in the log with the actual delivered message file. I was hoping there would be some possible way of doing that.
I can follow the id's in the log and trace everything that happens, but I don't know which message it is, all I know is the recipient(s). So if a user asks "what happened to my message such and such", I have no way of determining that. That's the sort of thing I was trying to figure out.
If your user wants to know that, your user should simply have his mail client request a delivery status notification, which is a popular SMTP extension that most mail clients support.
That's why I wondered if there was any sort of custom logging capabilities... if I could for example log the message subject, at least it would give me an additional parameter for logging/tracing.
Nope.
Incidentally, when a message is received, Courier's response to the sender includes the received message's assigned id. In the unlikely event the user's mail client logs Courier's "Ok" response, the id in that response will be the id used in the log, for that message.
If you manually telnet to Courier's port 25, and manually send yourself a test message, you can take the id you receive in the final "Ok" response, and pull that message from syslog. So, if all else fails, you can simply ask the user to furnish the message id that his mail client received when the message was sent; and if the user's mail client doesn't log that, well, there's nothing you can do about that.
pgp00000.pgp
Description: PGP signature
