Messages piling up in queue, not being delivered
Printed From: LogSat Software
Category: Spam Filter ISP
Forum Name: Spam Filter ISP Support
Forum Description: General support for Spam Filter ISP
URL: https://www.logsat.com/spamfilter/forums/forum_posts.asp?TID=6705
Printed Date: 05 February 2025 at 11:51am
Topic: Messages piling up in queue, not being delivered
Posted By: gillonba
Subject: Messages piling up in queue, not being delivered
Date Posted: 06 July 2009 at 12:46pm
|
We have two spam filter servers that have been running pretty well for about a year now. But last Wednesday, messages started piling up in the queue directory of server 1. Restarting the service would cause some of them to be sent, but most of them would not be sent. This caused MAJOR problems, as our clients were not receiving mail. Server 2 was working just fine, so we decided to shut the service down on 1 and run on just server 2 until we figured out what is wrong. Now, I have just started seeing the same thing happening on server 2. Messages are queuing up and not being sent. I have installed the update (v. 4.1.2.812) on server 1 and restarted it, but it still does not seem to be sending. Have you seen this before? Is there a way to force the messages through? I do not see any indication in the logs that the message is actually being sent or not. Any advice would be appreciated because we are dead in the water until this is resolved!
|
Replies:
Posted By: gillonba
Date Posted: 06 July 2009 at 12:57pm
Update: I am seeing messages like this:
07/06/09 12:50:36:647 -- (2728) Read Timeout - forwarding to:<url1> - message queued - mailadmin@accentconsulting.com
07/06/09 12:50:37:584 -- (2844) Read Timeout - forwarding to:<url2> - will try forwarding to mail.remingtonseeds.com
07/06/09 12:50:38:365 -- (3280) Read Timeout - forwarding to:<IP1> - message queued - b-i0tay.1tnaqr@pinosal.com
07/06/09 12:50:39:021 -- (3368) Read Timeout - forwarding to:<url2> - will try forwarding to <url2.2>
07/06/09 12:50:39:224 -- (2992) Read Timeout - forwarding to:<url2> - will try forwarding to <url2.2>
07/06/09 12:50:39:224 -- (2920) Read Timeout - forwarding to:<url2> - will try forwarding to <url2.2>
07/06/09 12:50:39:224 -- (1288) Read Timeout - forwarding to:<url2> - will try forwarding to <url2.2>
07/06/09 12:50:39:224 -- (3216) Read Timeout - forwarding to:<url2> - will try forwarding to <url2.2>
07/06/09 12:50:39:271 -- (2232) Read Timeout - forwarding to:<IP1> - message queued - redraw@wendigo.biz
So it looks like it can't talk to the remote servers. As you can see in that snippet, there are multiple different servers affected. Pinging the given names returns the correct IP address and indicates that we CAN reach those servers. Also, the issue affects messages to multiple different servers, so the problem is unlikely to be on their end
|
Posted By: LogSat
Date Posted: 06 July 2009 at 1:30pm
gillonba,
Can you please zip and email us directly at support at logsat.com your SpamFilter's activity file for today? Please also include the contents of the \SpamFilter\queue and the \SpamFilter\temp directory.
If the file is larger than 8MB I'll send you a PM with the login access for our FTP site.
In the meantime, can you please try, from command line on the server running SpamFilter, running the following command:
C:\>telnet smtp-in.remingtonseeds.com 25
and see if you receive a response?
The "ReadTimeout" error usually means that SpamFilter is unable to make a successful connection to the remote server. As in this case there are issues with multiple servers, can you also please ensure there are no firewall issues (either local to the server or with your external firewall)?
-------------
Roberto Franceschetti
http://www.logsat.com" rel="nofollow - LogSat Software
http://www.logsat.com/sfi-spam-filter.asp" rel="nofollow - Spam Filter ISP
|
Posted By: gillonba
Date Posted: 07 July 2009 at 9:35am
|
Thank you for your help! The telnet suggestion put us on the right track. It turns out that our ISP noticed an increase in SMTP traffic and blocked port 25 without telling us. The issue is now resolved
|
|