Spam Filter ISP Support Forum

  New Posts New Posts RSS Feed - Unable to forward to Mail Enable Server
  FAQ FAQ  Forum Search   Register Register  Login Login

Unable to forward to Mail Enable Server

 Post Reply Post Reply
Author
ykaraman View Drop Down
Newbie
Newbie


Joined: 15 March 2007
Location: United States
Status: Offline
Points: 5
Post Options Post Options   Thanks (0) Thanks(0)   Quote ykaraman Quote  Post ReplyReply Direct Link To This Post Topic: Unable to forward to Mail Enable Server
    Posted: 15 March 2007 at 4:14pm

I installed Spam Filter ISP trial version on my server. I set it up for single server and single IP operation. SF is using port 25 while my MailEnable is using port 26. I am running into issues when mail clears SF and while it is forwarded to ME. I am getting the following message:

Socket Error # 10061 -- Connection refused. - Forwarding to:50.123.132.15- message queued mail@isp.net

My ME server displays the following message in its SMTP inbound test diagnosis results:

220 my_mailserver.mydomain.com Welcome to SpamFilterISP SMTP Server v3.1.3.599 - Unlicensed Evaluation Copy 

When I setup SF I specified my fully qualified domain name for the e-mail server. Please note the domain name in the above message (my_mailserver.mydomain.com).

YK
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: 15 March 2007 at 4:39pm
ykaraman,

The error:

Socket Error # 10061 -- Connection refused. - Forwarding to:123.123.123.123  - message queued mail@isp.net

indicates that your mail server (MailEnable) is rejecting the connection from SpamFilter, when SpamFilter attempts to forward it emails. As MailEnable is simply rejecting the connection, you'll need to look at MailEnable's logs to see why it's not accepting them.
 
The 2nd issue with the banner is rather unusual. The welcome banner:
220 my_mailserver.mydomain.com Welcome to SpamFilterISP SMTP Server v3.1.3.599 - Unlicensed Evaluation Copy
is sent by SpamFilter when anyone connects to port 25. The "my_mailserver.mydomain.com" is customized by entering a valid value in the "Settings - Configuration" tab, under the "FQDN" box. Please ensure you click on the "Save SMTP Settings" button to activate that setting.
The "" part can be customized under the "Customized Items" tab, in the "Welcome Banner welcome text".

Roberto Franceschetti

LogSat Software

Spam Filter ISP
Back to Top
ykaraman View Drop Down
Newbie
Newbie


Joined: 15 March 2007
Location: United States
Status: Offline
Points: 5
Post Options Post Options   Thanks (0) Thanks(0)   Quote ykaraman Quote  Post ReplyReply Direct Link To This Post Posted: 16 March 2007 at 9:18am

After installing the new version there have been some improvements but I still can't forward mail to MailEnable. I still get the following message:

Warning - This IP Address appears to be running an SMTP Server other than MailEnable or the welcome message has been changed.

SFISP's header appears to be:

220 mydomain.com Welcome to SpamFilterISP SMTP Server v3.1.3.599 - Unlicensed Evaluation Copy

where mydomain.com represent's our domain name in the actual output.

I don't think I will get a response from ME on this. Any help from your side will help me move ahead with your product.

Regards,

Yavuz

YK
Back to Top
ykaraman View Drop Down
Newbie
Newbie


Joined: 15 March 2007
Location: United States
Status: Offline
Points: 5
Post Options Post Options   Thanks (0) Thanks(0)   Quote ykaraman Quote  Post ReplyReply Direct Link To This Post Posted: 16 March 2007 at 12:13pm

I found a solution to the SFISP -- MailEnable issue. I set this up on a single server with one domain. I was using the same IP for SFISP and ME but using different SMTP ports for each (26 for ME). I have two public IP addresses on the server. When I dedicated an IP address to SFISP and ME and used SMTP port 25 for both (SFISP and forwarding address for ME) it worked fine.

I am guessing most installations with multiple server, domains, or IPs wouldn't have experienced this.

Regards,

Yavuz

YK
Back to Top
 Post Reply Post Reply
  Share Topic   

Forum Jump Forum Permissions View Drop Down



This page was generated in 0.062 seconds.