Maybe a reverse DNS issue? Just a guess.....
Michael Shook Technical Analyst Saddle Creek Corporation 723 Joe Tamplin Industrial Blvd Macon GA 31217 478 742 8740 ext. 105 (work) 478 256 9318 (mobile) 478 742 7917 (fax) [EMAIL PROTECTED] http://www.saddlecrk.com >>> [EMAIL PROTECTED] 02/23/04 03:24PM >>> Interesting. When I have all ports open, I get a 220 return right away. When only 25 is open, I get a 220 return after exactly 30 seconds every time. I tried telnetting to other mail servers with ports other than 25 closed and they connect right away. So its obvious now this isn't a problem with SA. I just wish I knew why my mail server takes 30 seconds. It's Qmail and I haven't found anything showing that it needs some other port before opening a connection. Thanks for your help. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Sunday, February 22, 2004 11:20 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] SMTP alerts failing when closing ports other than 25 For SMTP we only use 25 and 53 (for the DNS resolution). Try: telnet <hostname> 25 and do you get a return (220...) and how long does it take to get that return? Dirk. _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fernando Scalini Sent: Sunday, February 22, 2004 11:23 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] SMTP alerts failing when closing ports other than 25 Thanks. SA version 4.1.1567 With full logging, I get the following when using an external SMTP server Sunday, February 22, 2004 1:41:33 PM Sending email message (This is a test message sent by Servers Alive) Sunday, February 22, 2004 1:41:49 PM SMTP Error : T: 16Pfalse Sunday, February 22, 2004 1:41:49 PM SMTP Error : stopped sending mail Sunday, February 22, 2004 1:41:49 PM SMTP Error : And I get the following with "Send Direct" Sunday, February 22, 2004 2:04:50 PM Sending email message (This is a test message sent by Servers Alive) Sunday, February 22, 2004 2:05:06 PM SMTP Error : stopped sending mail Sunday, February 22, 2004 2:05:06 PM SMTP Error : SA is running on the web server that has most of the ports closed. It is the same server where other components can send email without problems (using same SMTP server as SA). DNS port is open (as is 25, 80, 443, 1433) but I am also using a numeric IP to point to the SMTP server when using "normal" send. It works fine when all ports are open, so I think the main question is what other ports besides SMTP and DNS is SA trying to use (if it's an SA problem to begin with). -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Sunday, February 22, 2004 12:58 AM To: [EMAIL PROTECTED] Subject: RE: [SA-list] SMTP alerts failing when closing ports other than 25 What version of SA? And are you using full logging? If so then there should be a line before that saying when the mailsending started. Also from the mail it's not very clear what you're exactly doing. Are you using the direct send or the "normal" send? On what system did you close all the ports? On the system running SA or on the system running the SMTP server? If the system running SA, then you could also have a problem with the direct send that it also needs access to a DNS server in order to resolve the SMTP server it should be using? Dirk. _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fernando Scalini Sent: Sunday, February 22, 2004 9:29 AM To: [EMAIL PROTECTED] Subject: RE: [SA-list] SMTP alerts failing when closing ports other than 25 Saturday, February 21, 2004 5:36:08 PM SMTP Error : stopped sending mail Saturday, February 21, 2004 5:36:08 PM SMTP Error : -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dirk Bulinckx Sent: Saturday, February 21, 2004 11:45 PM To: [EMAIL PROTECTED] Subject: RE: [SA-list] SMTP alerts failing when closing ports other than 25 Looks like SA is able to connect to the port but is not receiving the correct return from the server. Leaving the timestamps from the logging could confirm this. Dirk. _____ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Fernando Scalini Sent: Sunday, February 22, 2004 3:08 AM To: [EMAIL PROTECTED] Subject: [SA-list] SMTP alerts failing when closing ports other than 25 Using IPsec, I close down all non-essential ports on this web server. I leave port 25 open so asp scripts can send out email and they work fine. However, SA can't send unless I open up all ports. This happens whether I use "Send Direct", an external SMTP server, or the IIS SMTP server on the same box as SA. Does SA require more than just TCP Port 25? What has me stumped is that asp scripts can send email out just fine even though SA can't. Log has two lines for each failure. Second one has nothing after "SMTP Error :" SMTP Error : stopped sending mail SMTP Error : I checked the box for "Don't ping the SMTP servers...". SA version is 4.1.1567. W2KAS SP4 I checked archives and google and can't find a solution to this problem. Thanks! To unsubscribe from a list, send a mail message to [EMAIL PROTECTED] With the following in the body of the message: unsubscribe SAlive
