On Wed, 2 Feb 2005, Manuel Martin wrote: > Suspend outgoing messages. > If I have to take Exchange offline (or for other reasons) I'd like to be = > able > to suspend the Xmail SMTP-Queues, so that messages can still be received = > and > are copied to the spool directories, but not sent until the queue is > unsuspended. I think that would qualify for a new pair of commands.
Just set a long retry policy and take the Exchange server offline. > Log failed delivery attempts > SMAIL-Logs don't show failed delivery attempts I think. They should IMO, = > and > they should also show which error occured and wether it was a local = > error (or > transport) or the remote server coughed, and if yes, which code and = > message > the remote server returned. > Otherwise one has to fiddle through the spool additionally to the > SMAIL-Logs... Did you take a look at the files inside the slog directories inside the spool? > "pseudo log" of commands for Xmail-Postmaster > A cool thing would be if the bounce message (for the postmaster) would = > have a > short transcription of the last SMTP-dialog, which includes also if an > "retries exceeded" happens; as we all know some servers just don't know = > the > difference between "temporary" and "permanent", and give permanently > temporary errors :-).=20 > Something like > > .... > > MAIL FROM:<bla> > < 200 OK > > RCPT TO:<ble> > < 200 OK > > DATA > > [Sending data] > < 451 Uh, somethings wrong here > > (Yes, it's just an not 100% correct example) Usually SMTP messages, have all the necessary information to understand where the transaction broke. This is why there is some text after the status code ;) - Davide - To unsubscribe from this list: send the line "unsubscribe xmail" in the body of a message to [EMAIL PROTECTED] For general help: send the line "help" in the body of a message to [EMAIL PROTECTED]
