Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: Robert Harlow on September 14, 2003, 08:49:22 PM

Title: QMHANDLER deleted 2 spams - now 2 permanent retries in qmail
Post by: Robert Harlow on September 14, 2003, 08:49:22 PM
Sirs

qmhandler showed me two stuck messages in the remote queue. They were plainly rubbish. Elected to delete both. Now the qmail/current log has a pair of permanent retries...
@400000003f6476300b29ac74 warning: trouble opening remote/19/1661539; will try again later
@400000003f6476730b29db54 warning: trouble opening remote/20/1661655; will try again later
...and, yes, they DO try later:-|

Did qmhandler (somehow) incorrectly delete these two spams? The permanent retries only occurred AFTER the delete functionality. Perhaps it would've been better to have just left the 2 spams quietly in the queue;~/ If qmhandler can't delete these things properly why does it offer to so do!?

best wishes, Robert
Title: Re: QMHANDLER deleted 2 spams - now 2 permanent retries in q
Post by: Jens Kruuse on September 15, 2003, 01:46:36 AM
I've had that problem a few times myself. I solved it by going to the console as root and issuing two commands:

service qmaild restart
service smtpfront-qmail restart

See if that works for you. Some of the tech-wizards may have better solutions. ;-)

Cheers,
Jens
Title: Re: QMHANDLER deleted 2 spams - now 2 permanent retries in q
Post by: Robert Harlow on September 15, 2003, 01:55:06 AM
Since the reboot (and a whole lot of other stuff I expect) that particular pair of *will try again later* error lines have not returned. That's good but I rather think that next time I take up qmhandler's offer to *delete* an offensive email the same repetitions will occur. Thank you Jens I will certainly boilerplate those two commands for that probable eventuality:-)

best wishes, Robert
Title: Re: QMHANDLER deleted 2 spams - now 2 permanent retries in q
Post by: Robert Harlow on September 19, 2003, 06:55:31 PM
(follow up)

Jens made a small typo, my boilerplate now reads:-

service qmail restart
service smtpfront-qmail restart

Found this out when I tried the commands on another *stuck/strange* email issue that was affecting the frontend (Forté Agent/Windows) but it didn't resolve it;~/

best wishes, Robert