Byteplant Forum

Home » CleanMail Support » CleanMail Server Talk » connection closed by server
connection closed by server [message #1018] Tue, 25 January 2005 11:03
teddy_ih
Messages: 4
Registered: January 2005
Junior Member
Hello,
I'm currently testing No Spam Today! SMTP Proxy to limit spam on our mail server. We're using Visnetic Mail Server and your program apparently integrates very well with it. Only one thing, after letting run NoSpam for awhile I always get "Connection Closed by Server on the logs" and well no email gets through of course.

Can anything be done to avoid this? Does it have anything to do with the system load (maybe the system load reaches its maximum and the whole thing crashes??)

thank you in advance
t.

Re: connection closed by server [message #1019 is a reply to message #1018] Tue, 25 January 2005 15:50 Go to previous message
support
Messages: 918
Registered: April 2004
Senior Member
> I'm currently testing No Spam Today! SMTP Proxy to limit spam
> on our mail server. We're using Visnetic Mail Server and your
> program apparently integrates very well with it. Only one
> thing, after letting run NoSpam for awhile I always get
> "Connection Closed by Server on the logs" and well no email
> gets through of course.
>
> Can anything be done to avoid this? Does it have anything to
> do with the system load (maybe the system load reaches its
> maximum and the whole thing crashes??)

Hard to tell what might be going wrong. It could be a load problem, but this depends a lot on your hardware and the number of mails processed.

Reconfigure NoSpamToday! to enable detailed logging (File -> Global Settings), this way the log might show something (like the time it takes to filter the mail, how many mails are being processed etc.).

Once you see these connection closed messages, please send us a mail (nstsupport@byteplant.com), with the relevant parts of the log file (nospamtoday.log), and your configuration file (nospamtoday.cf).



Customer Support
Byteplant GmbH
Re: connection closed by server [message #1020 is a reply to message #1018] Mon, 31 January 2005 10:13 Go to previous message
teddy_ih
Messages: 4
Registered: January 2005
Junior Member
thanks in advance for your help,

I did what you told me and got the following log:

Jan 31, 2005, 03:23:25 Session 0: Connection from 220.78.83.115 accepted on 80.78.66.203:25
Jan 31, 2005, 03:23:25 Session 0: 421 4.0.0 Tarpitting active for [192.168.1.52]
Jan 31, 2005, 03:23:25 Session 0: Connection closed by server
Jan 31, 2005, 03:23:25 Session 0: Connection from 220.78.83.115 closed
Jan 31, 2005, 03:25:59 Session 0: Connection from 64.12.136.13 accepted on 80.78.66.203:25
Jan 31, 2005, 03:25:59 Session 0: 421 4.0.0 Tarpitting active for [192.168.1.52]
Jan 31, 2005, 03:25:59 Session 0: Connection closed by server
Jan 31, 2005, 03:25:59 Session 0: Connection from 64.12.136.13 closed
Jan 31, 2005, 03:26:47 Session 0: Connection from 206.81.120.47 accepted on 80.78.66.203:25
Jan 31, 2005, 03:26:47 Session 0: 421 4.0.0 Tarpitting active for [192.168.1.52]
Jan 31, 2005, 03:26:47 Session 0: Connection closed by server
Jan 31, 2005, 03:26:47 Session 0: Connection from 206.81.120.47 closed
Jan 31, 2005, 03:27:47 Session 0: Connection from 206.81.120.50 accepted on 80.78.66.203:25
Jan 31, 2005, 03:27:47 Session 0: 421 4.0.0 Tarpitting active for [192.168.1.52]
Jan 31, 2005, 03:27:47 Session 0: Connection closed by server


Does this mean that i have to disable tarpiting on my mailserver???

Re: connection closed by server [message #1021 is a reply to message #1020] Tue, 01 February 2005 11:52 Go to previous message
support
Messages: 918
Registered: April 2004
Senior Member
Your server counts the number of failed recipient addresses or similar, and associates them with the IP address of the MTA connected in, which is always the same: NoSpamToday! at [192.168.1.52].

Maybe you can use other tar-pitting settings for your server. It is a common configuration that the sending MTA's IP address is no longer visible to a mail server (because of proxys or firewalls), so I'm sure there is a setting that takes this into account. Tar-pitting could look at the server name given in the HELO command instead of the IP address.

If you can't find a tar-pitting setting that works, you need to turn it off.



Customer Support
Byteplant GmbH
Previous Topic: "HTML and text parts are different" - indicates spam?
Next Topic: Whitelist
Goto Forum:
  


Current Time: Sun Sep 25 15:59:24 CEST 2016