On Saturday, January 15, 2005 2:53 PM [GMT+1=CET], Eric Garnice <[EMAIL PROTECTED]> wrote:
> One of our offices has an Exchange server that's almost finished > committing suicide (what else is new). To help the old bear along, I > installed XMail on a file server in that office and routed all > outbound mail from Exchange through XMail thereby keeping the > Exchange outbound queues clean of spam NDRs. > > The odd thing is that XMail refuses to deliver. The messages are are > the spool, but no slog files are created and the messages just sit > there. I can find the proper mx in the dnscache directory for some > test messages I have sent, so DNS is ok. Making it stranger is if I > restart XMail (1.21 on Win2K Server) all messages are delivered > immediately. I currently have XMail on a 5 minute restart batch and > it's working, but if I don't restart the messages just build up in > the spool. My only command-line options are for logging. I've > deployed XMail in some odd fashion like this dozens of times, but > this time I'm stumped. > > Any ideas? Eric, i had something very similar like that some time ago. It was one message in the que that got the SMAIL threads to completely stop working. You'll have to search for it, after each restart, check which message is still in the que (mess directories) and doesn't get delivered - so you can find it. After quarantaining your mailserver then should run without any problems. Check the devil message for suspicious content (or zip it and send it to Davide) - I think maybe somewhere in XMail there is a sleeping dog that gots triggered in some really rarely situations. Good luck! ;-) - 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]
