Resending because I didn't get an echo - not sure if it made it to the 
list...

Tracy wrote:
> Soenke Ruempler wrote:
>> Hi Tracy,
>>
>> On 27.10.2006 14:00, Tracy wrote:
>>
>>> I'm running XMail 1.20 (I know, not the current version) on Windows 
>>> 2000 Server (SP4). I have two filters that run (one from pre-data - 
>>> spam check, one from post-data - virus scan).
>>>
>>> For the last week, I've been noticing that mail delivery is running 
>>> about 4 - 6 hours later than mail receipt. For example, I received 
>>> about 5 minutes ago (7:50am) a posting from this mailing list with a 
>>> time stamp of 3:09am - but checking the SMTP log for XMail shows that 
>>> it was received by SMTP at 3:09:16 this morning. So, it sat in the 
>>> processing queue somewhere for over 4.5 hours before being delivered 
>>> to my mailbox.
>>>
>>> I have verified that if I stop XMail, then restart it, all the 
>>> waiting mail suddenly gets delivered - but new items coming in still 
>>> hang up in the queue.
>>>
>>> Any ideas on where to look for what might be causing this? I've 
>>> checked to make sure that both the pre and post data filters are not 
>>> hanging up anywhere - there aren't any copies of them still hanging 
>>> around in the process list. And I've tried restarting the machine 
>>> (same effect as restarting XMail - queued mail gets delivered, new 
>>> arriving mail sticks in the queue).
>>
>> I remember exactly such behavior some time ago. There is some evil
>> message in the que that seems to stop SMAIL threads. I didn't find any
>> real solution but I somehow catched the evil thing.
>>
>> You can try the following:
>>
>> 1) Start XMail in debug mode and look when SMAIL stops processing the
>> que. Maybe the last entry is the message.
>> 2) Check all messages in the que (it shoud be the message in the rsnd/
>> folder) - one of them is evil.
>>
>> If you catch the message it'd be great if you can investigate it for
>> some abnormal characters / sizes / etc. - I guess there's maybe some bug
>> in the software that has not been found & fixed - OR: some filter
>> screwed up a spool file and X(S)Mail doesn't like it anymore...
>>
>> I hope these tipps will help you. I'd appreciate some feedback. Thanks.
>>
> 
> 
> Well, it was definitely a corrupt message of some kind in the outbound 
> queue. Once I got about 200 of the waiting messages out of the queue, 
> local mail delivery started flowing again.
> 
> It looked like it might have been more than one message - what it really 
> looked like was that all the smail threads were getting tied up trying 
> to deliver mail that would go for one reason or another. Stopping the 
> debug session and restarting it several times (with retry set to 4 
> instead of default) cleared a bunch of it out and now things are going.
> 
> I don't know what it was about the messages in particular - it could 
> have been a number of nasty things, since all of the messages in 
> question were spam reports and included the original spams.
> 
> But for what it's worth, that's what I found out. Hope it strikes a 
> chord with someone, and maybe turns up further answers.
> 

-
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]

Reply via email to