Thanks for the explanation, Sam. The scenario I'm most interested in is when a user has setup some email forwarding, and then complains that either messages don't appear to be forwarded, or a particular message never arrived. The forwarding is done via maildrop and the .mailfilter file. With that, I wonder if it is at all possible to have access to this server-generated ID from within maildrop?
It would be very nice if the .mailfilter rules could have access to this ID, just as it has access to certain variables like "FROM" and thus allow for accurate tracking of specific individual messages. Please, please, please? :-)) On Tue, 5 Aug 2003, Sam Varshavchik wrote: > Ricardo Kleemann writes: > > > > > 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. > > ------------------------------------------------------- This SF.Net email sponsored by: Free pre-built ASP.NET sites including Data Reports, E-commerce, Portals, and Forums are available now. Download today and enter to win an XBOX or Visual Studio .NET. http://aspnet.click-url.com/go/psa00100003ave/direct;at.aspnet_072303_01/01 _______________________________________________ courier-users mailing list [EMAIL PROTECTED] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-users
