This is a discussion on changed port, no delivery ??? within the alt.comp.mail.exim forums, part of the Mail Servers and Related category; I changed /etc/services/ to run tcp and udp SMTP connections on port 125. I ran ASSP (Anti Spam Server) ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
I changed /etc/services/ to run tcp and udp SMTP connections on port 125.
I ran ASSP (Anti Spam Server) on port 25, and it relays good messages to Exim on port 127.0.0.1:125 Incoming mail works great, but OUTGOING MAIL FAILS WITH "Connection Refused (111)". I believe that Exim is attempting to send outgoing mail on port 125!!! anybody know how, why and what i have to do to fix this? --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.747 / Virus Database: 499 - Release Date: 9/1/2004 |
|
|||
|
Hello Chris,
Chris Fortune schrieb/wrote: > I changed /etc/services/ to run tcp and udp SMTP connections on port 125. > I ran ASSP (Anti Spam Server) on port 25, and it relays good messages to > Exim on port 127.0.0.1:125 How do the corresponding lines of /etc/services look like in detail? > Incoming mail works great, but OUTGOING MAIL FAILS WITH "Connection Refused > (111)". > > I believe that Exim is attempting to send outgoing mail on port 125!!! That has probably been caused by changing smtp 25/tcp to smtp 125/tcp I would recommend you to use the following combination instead: smtp 25/tcp smtp-exim 125/tcp When you add the line daemon_smtp_port = smtp-exim to your exim.conf, exim will listen on port 125 for incoming mail, but won't get confused when contacting other servers' SMTP (!) port. Regards, Christian -- Christian Schmidt | Germany | ChriSchmiLi@gmx.de PGP Key ID: 0x28266F2C |
|
|||
|
Hello,
Thanks Christian! This fix looked very promising, I changed exim.conf and /etc/services as recommended, but it failed. The error message is below. Is there some collision with cpanel's config? "/usr/sbin/exim -tls-on-connect -bd -oX 465" ? "Christian Schmidt" <ChriSchmiLi@gmx.de> wrote in message news:slrnck0d8o.b2n.ChriSchmiLi@server.linau.de... > Hello Chris, > > Chris Fortune schrieb/wrote: > > > I changed /etc/services/ to run tcp and udp SMTP connections on port 125. > > I ran ASSP (Anti Spam Server) on port 25, and it relays good messages to > > Exim on port 127.0.0.1:125 > > How do the corresponding lines of /etc/services look like in detail? > smtp 25/tcp mail #smtp-exim 125/tcp mail smtp 25/udp mail > > Incoming mail works great, but OUTGOING MAIL FAILS WITH "Connection Refused > > (111)". I believe that Exim is attempting to send outgoing mail on port 125!!! > > That has probably been caused by changing > "smtp 25/tcp" to "smtp 125/tcp" > Correct > I would recommend you to use the following combination instead: > smtp 25/tcp > smtp-exim 125/tcp > > When you add the line > daemon_smtp_port = smtp-exim > to your exim.conf, exim will listen on port 125 for incoming mail, but > won't get confused when contacting other servers' SMTP (!) port. > Error Message: Attempting to restart exim Waiting for exim to restart.... . . . . . . . . . . finished. exim statusmailnull 22628 0.0 0.1 5480 912 ? S Jul01 0:02 /usr/bin/perl /usr/local/cpanel/bin/eximstats mailnull 27970 0.0 0.0 0 0 ? Z Jul14 0:00 [exim ] mailnull 15021 0.0 0.3 6084 1780 ? S 20:55 0:00 /usr/sbin/exim -bd -q60m mailnull 15028 0.0 0.3 6052 1760 ? S 20:55 0:00 /usr/sbin/exim -tls-on-connect -bd -oX 465 root 15128 0.1 0.2 5772 1496 ? S 20:55 0:00 antirelayd root 15143 5.1 4.0 24532 20520 ? S 20:55 0:00 /usr/bin/spamd -d Sep 11 20:55:02 fortune01 exim: exim shutdown succeeded Sep 11 20:55:02 fortune01 exim: antirelayd shutdown succeeded Sep 11 20:55:02 fortune01 exim: spamd shutdown failed Sep 11 20:55:02 fortune01 exim: exim startup succeeded Sep 11 20:55:02 fortune01 exim: exim startup succeeded Sep 11 20:55:03 fortune01 exim: antirelayd startup succeeded exim has failed, please contact the sysadmin. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.747 / Virus Database: 499 - Release Date: 9/1/2004 |
|
|||
|
Hello Chris,
Chris Fortune schrieb/wrote: > Thanks Christian! This fix looked very promising, I changed exim.conf and > /etc/services as recommended, but it failed. The error message is below. > Is there some collision with cpanel's config? > "/usr/sbin/exim -tls-on-connect -bd -oX 465" ? IS that the command you start exim with? [..] >> I would recommend you to use the following combination instead: >> smtp 25/tcp >> smtp-exim 125/tcp >> >> When you add the line >> daemon_smtp_port = smtp-exim >> to your exim.conf, exim will listen on port 125 for incoming mail, but >> won't get confused when contacting other servers' SMTP (!) port. >> > > Error Message: > > Attempting to restart exim > Waiting for exim to restart.... . . . . . . . . . . finished. Well - that looks good IMO. > Sep 11 20:55:02 fortune01 exim: exim shutdown succeeded Sep 11 20:55:02 > fortune01 exim: antirelayd shutdown succeeded Sep 11 20:55:02 fortune01 > exim: spamd shutdown failed Sep 11 20:55:02 fortune01 exim: exim startup > succeeded Sep 11 20:55:02 fortune01 exim: exim startup succeeded Sep 11 > 20:55:03 fortune01 exim: antirelayd startup succeeded exim has failed, > please contact the sysadmin. As I don't know anything about "antirelayd" and in which way it interacts with exim, I can't give you any advice - sorry. Maybe you'll take another look at the antirelayd docs... Regards, Christian -- Christian Schmidt | Germany | ChriSchmiLi@gmx.de PGP Key ID: 0x28266F2C |
|
|||
|
> > "/usr/sbin/exim -tls-on-connect -bd -oX 465" ?
> > IS that the command you start exim with? > Yes, that is what cpanel uses. > > Attempting to restart exim > > Waiting for exim to restart.... . . . . . . . . . . finished. > > Well - that looks good IMO. > I thought so too, but no exim process :( > > 20:55:03 fortune01 exim: antirelayd startup succeeded exim has failed, > > please contact the sysadmin. > > As I don't know anything about "antirelayd" and in which way it > interacts with exim, I can't give you any advice - sorry. > > Maybe you'll take another look at the antirelayd docs... > There are NO antirelayd docs. Check out Google - nothing. # description: antirelayd is a daemon that checked /var/log/maillog for # logins and keeps track of vaild ones for use with smtp relaying. # --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.747 / Virus Database: 499 - Release Date: 9/2/2004 |
|
|||
|
Hello Chris,
Chris Fortune schrieb/wrote: >> > "/usr/sbin/exim -tls-on-connect -bd -oX 465" ? >> >> IS that the command you start exim with? >> > Yes, that is what cpanel uses. OK, it starts an exim daemon listening on port 465. AFAIK, this port is reserved for ssl-encrypted SMTP... > >> > Attempting to restart exim >> > Waiting for exim to restart.... . . . . . . . . . . finished. >> >> Well - that looks good IMO. >> > I thought so too, but no exim process :( > > >> > 20:55:03 fortune01 exim: antirelayd startup succeeded exim has failed, >> > please contact the sysadmin. >> >> As I don't know anything about "antirelayd" and in which way it >> interacts with exim, I can't give you any advice - sorry. >> >> Maybe you'll take another look at the antirelayd docs... >> > > There are NO antirelayd docs. Check out Google - nothing. > > # description: antirelayd is a daemon that checked /var/log/maillog for > # logins and keeps track of vaild ones for use with smtp > relaying. > # Ah, I see. It's just a mechanism for controlling who may use your server as a relay for outgoing mail, isn't it? As exim and especially exim4 provides powerful means of controlling who may relay and who may not, I would recommend you to just use these means and to stop using antirelayd... Keep it simple. ;-) Regards, Christian -- Christian Schmidt | Germany | ChriSchmiLi@gmx.de PGP Key ID: 0x28266F2C |
|
|||
|
> > # description: antirelayd is a daemon that checked /var/log/maillog for > > # logins and keeps track of vaild ones for use with smtp > > relaying. > > # > > Ah, I see. It's just a mechanism for controlling who may use your > server as a relay for outgoing mail, isn't it? > As exim and especially exim4 provides powerful means of controlling > who may relay and who may not, I would recommend you to just use these > means and to stop using antirelayd... > Keep it simple. ;-) > It worked! I commented out antirelayd in the /etc/rc.d/init.d/exim file and restarted exim on an unused unusual port ... voila, beautiful. ASSP is now running on port 25 and accepting mail from the Internet, then relaying it to Exim for delivery. Indeed it was antirelayd that was messing things up and killing Exim on any port but 25 and 465. I have no idea why, but since the relayhosts file seems to be working, then I see no need of it anyways. I'll read more in the Exim docs about relaying. Now, a new problem. The ASSP daemon will not accept outgoing mail on port 25. It accepts outgoing mail from any other port that I choose, but it is then an open relay!! This is similar to the previous problem i had with Exim, it would not accept outgoing mail on port 25 either, only as TLS on port 465, however this is now broken because I just installed a new SSL cert!!! Unfortunately, ASSP will not broker a TLS authentication... :( It can support POPb4SMTP. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.762 / Virus Database: 510 - Release Date: 9/13/2004 |
|
|||
|
Hello Chris,
Chris Fortune schrieb/wrote: > Now, a new problem. The ASSP daemon will not accept outgoing mail on port > 25. What is "ASSP"? > It accepts outgoing mail from any other port that I choose, but it is > then an open relay!! This is similar to the previous problem i had with > Exim, it would not accept outgoing mail on port 25 either, only as TLS on > port 465, however this is now broken because I just installed a new SSL > cert!!! Unfortunately, ASSP will not broker a TLS authentication... >:( It can support POPb4SMTP. Configuring exim for SMTP Auth is noct that difficult... ;-) Regards, Christian -- Christian Schmidt | Germany | ChriSchmiLi@gmx.de PGP Key ID: 0x28266F2C |
|
|||
|
> > Now, a new problem. The ASSP daemon will not accept outgoing mail on
port > > 25. It accepts outgoing mail from any other port that I choose ... > > What is "ASSP"? > http://assp.sourceforge.net/ "a transparent SMTP filtering proxy, written in perl" > > , but it is > > then an open relay!! After further tests, not true. > > This is similar to the previous problem i had with > > Exim, it would not accept outgoing mail on port 25 either, only as TLS on > > port 465, however this is now broken because I just installed a new SSL > > cert!!! Unfortunately, ASSP will not broker a TLS authentication... > >:( It can support POPb4SMTP. > > Configuring exim for SMTP Auth is not that difficult... ;-) > Hmmm. Yes, thank you. Right now I fixed the problem by running assp on an unused port and using plain text user/pass. I will persist. Your help has been very appreciated. --- Outgoing mail is certified Virus Free. Checked by AVG anti-virus system (http://www.grisoft.com). Version: 6.0.762 / Virus Database: 510 - Release Date: 9/13/2004 |
![]() |
| Thread Tools | |
| Display Modes | |
|
|