Spam Filter ISP Support Forum

  New Posts New Posts RSS Feed - messages with attachments not being delivered
  FAQ FAQ  Forum Search   Register Register  Login Login

messages with attachments not being delivered

 Post Reply Post Reply
Author
gillonba View Drop Down
Newbie
Newbie


Joined: 30 April 2008
Status: Offline
Points: 33
Post Options Post Options   Thanks (0) Thanks(0)   Quote gillonba Quote  Post ReplyReply Direct Link To This Post Topic: messages with attachments not being delivered
    Posted: 12 July 2011 at 10:56am
We are running two spam filter servers, and one of them seems to have trouble delivering messages with attachments.  Instead, I am seeing this in the logs:

07/12/11 10:39:01:321 -- (5064) Socket Error # 10054 -- Connection reset by peer. - forwarding to:<server> - message queued - <address>
07/12/11 10:39:01:400 -- (5204) Socket Error # 10053 -- Software caused connection abort. - forwarding to:<server> - message queued - <address>
07/12/11 10:39:01:540 -- (6104) Socket Error # 10053 -- Software caused connection abort. - forwarding to:<server> - message queued - <address>
07/12/11 10:39:01:618 -- (4556) Socket Error # 10054 -- Connection reset by peer. - forwarding to:<server> - message queued - <address>
07/12/11 10:39:01:681 -- (5676) Socket Error # 10053 -- Software caused connection abort. - forwarding to:<server> - message queued - <address>
07/12/11 10:39:01:915 -- (6120) Socket Error # 10053 -- Software caused connection abort. - forwarding to:<server> - message queued - <address>
07/12/11 10:39:02:212 -- (1120) Socket Error # 10053 -- Software caused connection abort. - forwarding to:<server> - message queued - <address>
07/12/11 10:39:03:118 -- (5120) Socket Error # 10054 -- Connection reset by peer. - forwarding to:<server> - message queued - <address>
07/12/11 10:39:03:634 -- (3692) Socket Error # 10053 -- Software caused connection abort. - forwarding to:<server> - message queued - <address>
07/12/11 10:39:04:025 -- (6060) Socket Error # 10054 -- Connection reset by peer. - forwarding to:<server> - message queued - <address>
07/12/11 10:39:04:446 -- (5220) Socket Error # 10053 -- Software caused connection abort. - forwarding to:<server> - message queued - <address>
07/12/11 10:39:05:103 -- (5880) Socket Error # 10053 -- Software caused connection abort. - forwarding to:<server> - message queued - <address>
07/12/11 10:39:05:212 -- (6036) Socket Error # 10054 -- Connection reset by peer. - forwarding to:<server> - message queued - <address>
07/12/11 10:39:10:368 -- (3872) Socket Error # 10053 -- Software caused connection abort. - forwarding to:<server> - message queued - <address>
07/12/11 10:39:12:446 -- (3380) Socket Error # 10053 -- Software caused connection abort. - forwarding to:<server> - message queued - <address>
07/12/11 10:39:17:634 -- (4796) Socket Error # 10054 -- Connection reset by peer. - forwarding to:<server> - message queued - <address>

I suspect the issue is bandwidth.  This particular server is on a connection that is limited to 768kb upload, and the messages range from 5 to 25 MB in size.  There is nothing I can do about the bandwidth.  Is there a setting somewhere to increase the time it will spend trying to deliver the messages?  Or maybe reduce the number it tries to send at once?  I am on Spam Filter v.4.2.4.844
Back to Top
LogSat View Drop Down
Admin Group
Admin Group
Avatar

Joined: 25 January 2005
Location: United States
Status: Offline
Points: 4068
Post Options Post Options   Thanks (0) Thanks(0)   Quote LogSat Quote  Post ReplyReply Direct Link To This Post Posted: 12 July 2011 at 7:44pm
gillonba,

With such a small section of the logfile we're unable to see the timestamp of when SpamFilter has initiated the outbound connection - all that is visible are the socket errors. The time interval that elapses from when the delivery is attempted to when the connection is dropped often can provide some clues as to the possible causes. If for example the time interval is pretty consistent (1 minute, 5 minutes, 10, 20) that could indicate fixed timeout on firewalls (yours or the recipient's), or disconnects caused by other antivirus/antispam software that could be examining the messages.

On SpamFilter's side, you can try increasing this parameter in the SpamFilter.ini file:

;Timeout when delivering emails to the destination SMTP server (in seconds)

ReadTimeoutOutgoing=60


SpamFilter has a user-configurable limit for the amount of incoming SMTP connections. The limit for outbound connections is hardcoded to be equal to one fourth that threshold. If for example you set your maximum inbound Max SMTP connections to 100, SpamFilter will, as a consequence, have a limit of 25 outbound connections.

Roberto Franceschetti

LogSat Software

Spam Filter ISP
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down



This page was generated in 0.078 seconds.