RE: Email issues, relay failure, perhaps Jails is causing it.
Hello Can anybody assist me with pfctl on freebsd? I have pfctl running as adaptive. It is blocking some smtp mail. I am uncertain about flushing the states or machining some of the TIMEWAITING constraints go away. Which is really blocking my email. Can anyone assist? Thanks -Original Message- From: Bernt Hansson [mailto:b...@bananmonarki.se] Sent: Sunday, February 26, 2012 2:20 AM To: Bender, Chris Cc: freebsd-questions@freebsd.org Subject: Re: Email issues, relay failure, perhaps Jails is causing it. 2012-02-26 00:54, Bender, Chris skrev: Hi Brent Yes the system we are calling X, is jailed by another system. Here is the jailer system: zs1# netstat -aptcp | grep smtp tcp4 0 0 tools2.smtp10.156.31.20.45081 SYN_RCVD tcp4 0 0 tools2.smtp*.* LISTEN tcp4 0 0 rt3.smtp *.* LISTEN tcp4 0 0 npims.smtp *.* LISTEN tcp4 0 0 wiki.smtp *.* LISTEN tcp4 0 0 localhost.smtp *.* LISTEN Here is about jails; http://www.uk.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html Have you tried to telnet into the other jailed hostnames and ip-addresses, like telnet rt3.* 25 What does it say? Can you connect? There seems to be either a jail problem or a routing problem You can look at your routing table with netstat -r ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Email issues, relay failure, perhaps Jails is causing it.
Does anybody have an idea on how to clear the bruteforCE TABLE ON PFCTL ? An adaptive fw or pftcl device is blocking some of my email? Thanks -Original Message- From: Bernt Hansson [mailto:b...@bananmonarki.se] Sent: Sunday, February 26, 2012 2:20 AM To: Bender, Chris Cc: freebsd-questions@freebsd.org Subject: Re: Email issues, relay failure, perhaps Jails is causing it. 2012-02-26 00:54, Bender, Chris skrev: Hi Brent Yes the system we are calling X, is jailed by another system. Here is the jailer system: zs1# netstat -aptcp | grep smtp tcp4 0 0 tools2.smtp10.156.31.20.45081 SYN_RCVD tcp4 0 0 tools2.smtp*.* LISTEN tcp4 0 0 rt3.smtp *.* LISTEN tcp4 0 0 npims.smtp *.* LISTEN tcp4 0 0 wiki.smtp *.* LISTEN tcp4 0 0 localhost.smtp *.* LISTEN Here is about jails; http://www.uk.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html Have you tried to telnet into the other jailed hostnames and ip-addresses, like telnet rt3.* 25 What does it say? Can you connect? There seems to be either a jail problem or a routing problem You can look at your routing table with netstat -r ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Email issues, relay failure
On 2/25/12 1:39 PM, Bender, Chris wrote: Thanks. There aren't any firewalls between the devices but they are far apart. On 2/27/12 11:12 AM, Bender, Chris wrote: Can anybody assist me with pfctl on freebsd? I have pfctl running as adaptive. It is blocking some smtp mail. ! BTW, pfctl is the program for controlling the firewall. The actual firewall is generally referred to as pf. So if you just turn PF off for a bit, does e-mail suddenly flow? -- --Jon Radel j...@radel.com
RE: Email issues, relay failure
Yes after a few minutes the email in question begins to flow. AT some point in the past some of the postfix boxes behind the firewall Where turned off. This caused the fw, I believe to think it was being Attacked because it had nowhere to push the smtp traffic. I believe that is why on several IPs I see TIME_WAITING for the connections. I was thinking about just reloading the pf.conf but I have never worked with pf so I am worried other things might break. My thought was by doing that the Adaptive part of the pfctl would be restarted? Does that make sense would reloading the rules wash the adaptive behavior away or Would all that still be in some sort of bruteforce file to protect the firewall? Thanks -Original Message- From: Jon Radel [mailto:j...@radel.com] Sent: Monday, February 27, 2012 11:39 AM To: Bender, Chris; freebsd-questions@freebsd.org Subject: Re: Email issues, relay failure On 2/25/12 1:39 PM, Bender, Chris wrote: Thanks. There aren't any firewalls between the devices but they are far apart. On 2/27/12 11:12 AM, Bender, Chris wrote: Can anybody assist me with pfctl on freebsd? I have pfctl running as adaptive. It is blocking some smtp mail. ! BTW, pfctl is the program for controlling the firewall. The actual firewall is generally referred to as pf. So if you just turn PF off for a bit, does e-mail suddenly flow? -- --Jon Radel j...@radel.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Email issues, relay failure
On 2/27/12 11:45 AM, Bender, Chris wrote: I was thinking about just reloading the pf.conf but I have never worked with pf so I am worried other things might break. My thought was by doing that the Adaptive part of the pfctl would be restarted? Any pf.conf file I've ever seen does something sensible after reload. I suspect one could write something perverse that blows up on restart, but that would making rebooting the machine problematic Does that make sense would reloading the rules wash the adaptive behavior away or Would all that still be in some sort of bruteforce file to protect the firewall? pf can load data from files when it starts or just manage things in a fashion that is transient upon restart. Hard to say what's happening in your case w/o a clue as to what's in pf.conf. I'd suggest that you at the very least whitelist internal SMTP speakers that you expect to get e-mail from on a regular basis, even if you do throttling of SMTP connections in general. Much less messy -- --Jon Radel j...@radel.com
RE: Email issues, relay failure
How would I whitelist SMTP speakers? I am thinking it would be ok to reload the rules, would that clear the issue with SMTP users for now? Whats the harm? Thanks -Original Message- From: Jon Radel [mailto:j...@radel.com] Sent: Monday, February 27, 2012 11:58 AM To: Bender, Chris Cc: freebsd-questions@freebsd.org Subject: Re: Email issues, relay failure On 2/27/12 11:45 AM, Bender, Chris wrote: I was thinking about just reloading the pf.conf but I have never worked with pf so I am worried other things might break. My thought was by doing that the Adaptive part of the pfctl would be restarted? Any pf.conf file I've ever seen does something sensible after reload. I suspect one could write something perverse that blows up on restart, but that would making rebooting the machine problematic Does that make sense would reloading the rules wash the adaptive behavior away or Would all that still be in some sort of bruteforce file to protect the firewall? pf can load data from files when it starts or just manage things in a fashion that is transient upon restart. Hard to say what's happening in your case w/o a clue as to what's in pf.conf. I'd suggest that you at the very least whitelist internal SMTP speakers that you expect to get e-mail from on a regular basis, even if you do throttling of SMTP connections in general. Much less messy -- --Jon Radel j...@radel.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Email issues, relay failure
On 2/27/12 12:00 PM, Bender, Chris wrote: How would I whitelist SMTP speakers? You're invited to read the documentation. The Book of PF: A No-Nonsense Guide to the OpenBSD Firewall, 2nd ed., is also rather informative, although one has to keep in mind that the version of PF in FreeBSD lags that in OpenBSD. I am thinking it would be ok to reload the rules, would that clear the issue with SMTP users for now? Whats the harm? The universe might grind to a halt. This would upset a great many people. This outcome, however, is exceedingly unlikely. Again, with no clue as to what's in pf.conf, I could offer only the vaguest guesses based in part on my judged competence of the author of your pf.conf. Since your pf.conf appears to have possibly destroyed your e-mail infrastructure, the preliminary assessment is a bit shaky. -- --Jon Radel j...@radel.com
RE: Email issues, relay failure
Hi Joe
So from the rules below, I can see my network to and from in tables
tbl.r38.s to tbl.r37.s.
However when pfctl is enabled that traffic fails with
# tcpdump -ni bge0 host 10.156.81.10 and port 25
tcpdump: listening on bge0, link-type EN10MB
14:26:50.220591 10.156.81.10.60809 172.19.4.41.25: S
3154136673:3154136673(0) win 64240 mss
1260,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop
(DF) [tos 0xb8]
14:26:50.244314 10.156.81.10.60809 172.19.4.41.25: R
3154136674:3154136735(61) ack 1245040067 win 0 (DF) [tos 0xb8]
14:27:11.233494 10.156.81.10.60809 172.19.4.41.25: S
3154136673:3154136673(0) win 64240 mss
1260,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop,nop
(DF) [tos 0xb8]
14:27:11.245057 10.156.81.10.60809 172.19.4.41.25: R 0:61(61) ack 1
win 0 (DF) [tos 0xb8]
SO from traffic aboveon the inbound interface I can see this failed.
OUCH. But I don't know what rule is killing it.
Here is table
table tbl.r37.s { 10.200.82.16 , 10.200.104.15 , 172.19.4.41 ,
198.211.94.23 }
table tbl.r38.s { 10.13.0.0/21 , 10.13.224.0/21 , 10.13.226.0/23 ,
10.150.0.0/16 , 10.156.0.0/16 , 10.158.0.0/16 , 10.166.0.0/16 ,
10.196.0.0/16 , 10.198.0
.0/16 , 10.200.104.0/24 , 172.16.0.0/16 , 172.19.4.0/24 , 172.19.11.0/24
, 172.19.20.0/24 , 172.19.50.0/24 , 172.19.51.0/24 , 172.19.52.0/24 ,
172.19.53.0/24
, 172.19.100.0/29 , 172.19.231.0/24 , 172.19.232.0/24 , 172.31.0.0/16 }
Rest of pf.conf since you asked which I have removed confidential info
The key is what is blocking SMTP. I am not sure yet?
Thanks
#
# Prolog script
#
set loginterface bge0
set state-defaults pflow
nat-anchor ftp-proxy/*
rdr-anchor ftp-proxy/*
nat-anchor relayd/*
rdr-anchor relayd/*
anchor relayd/*
anchor ftp-proxy/*
#
# End of prolog script
#
set skip on bridge10
set skip on tun579
set skip on tun138
set skip on tun148
set skip on tun10
set skip on bridge138
set skip on bridge148
#
# Scrub rules
#
match in all scrub (no-df )
match out all scrub (random-id max-mss 1460)
# Tables: (26)
table BlackList persist file /home/admin/BlackList.txt
table BlackList-Internet persist file
/home/admin/BlackList-internet.txt
# Rule 0 (global)
# BlackList Rule
block in log quick inet from BlackList to any no state label
RULE 0 -- DROP
block out log quick inet from BlackList to any no state label
RULE 0 -- DROP
#
# Rule 1 (global)
# BlackList Rule
block in log quick inet from any to BlackList no state label
RULE 1 -- DROP
block out log quick inet from any to BlackList no state label
RULE 1 -- DROP
#
# Rule 2 (global)
# BlackList Servers going to Internet
block in log quick inet from BlackList-Internet to 127.0.0.1 no
state label RULE 2 -- DROP
block out log quick inet from BlackList-Internet to 127.0.0.1 no
state label RULE 2 -- DROP
#
# Rule 3 (bge1)
# BlackList Servers going to Internet
block out log quick on bge1 inet from BlackList-Internet to any no
state label RULE 3 -- DROP
#
# Rule 4 (bge1)
# BlackList Internet Ports
block out log quick on bge1 inet proto tcp from any to any port {
25, 465 } no state label RULE 4 -- DROP
#
# Rule 5 (global)
BLOCKED FOR CONFIIDENTIALITY
# Rule 6 (bge1,bge0)
# FTP Proxy Loopback Pule
pass in log quick on { bge0 bge1 } inet proto tcp from any to
127.0.0.1 port 8021 flags any modulate state ( pflow ) label RULE 6 --
ACCEPT
#
# Rule 7 (bge0,vlan579)
pass in log quick on { bge0 vlan579 } inet proto tcp from tbl.r2
to 127.0.0.1 port 2021 flags any modulate state ( pflow ) label RULE 7
-- ACCEPT
#
# Rule 8 (bge0,vlan579)
pass in log quick on { bge0 vlan579 } inet proto tcp from tbl.r2
to 127.0.0.1 port 3128 flags any modulate state ( pflow ) label RULE 8
-- ACCEPT
#
# Rule 9 (global)
pass in log quick inet from any to any tagged FTPPROXY keep state
( pflow ) label RULE 9 -- ACCEPT
pass out log quick inet from any to any tagged FTPPROXY keep state
( pflow ) label RULE 9 -- ACCEPT
#
# Rule 10 (bge1)
# Allow ESP, AH, IKE and NAT-T for IPSEC
#
# Rule 11 (bge1)
# BLOCKED FOR CONFIDENTIALITY
#
# Rule 12 (bge1)
# PPTP Traffic
BLOCKED FOR CONFIDENTIALITY
#
# Rule 13 (bge1)
# PPTP Traffic BLOCKED FOR CONFIDENTIALITY#
# Rule 14 (bge1)
# PPTP Traffic
pass out log quick on bge1 inet proto 47 from 172.19.231.128/27 to
any label RULE 14 -- ACCEPT
#
# Rule 15 (global)
Blocked for confidentiality
#
# Rule 16 (bge0)
pass in log quick on bge0 inet proto tcp from tbl.r16.s to
172.19.231.149 port 1723 flags any modulate state label RULE 16 --
ACCEPT
pass in log quick on bge0 inet proto 47 from tbl.r16.s to
172.19.231.149 label RULE 16 -- ACCEPT
#
# Rule 17 (global)
pass in log quick inet from tbl.r17.s to 10.10.11.0/24 label
RULE 17 -- ACCEPT
pass out log quick inet from tbl.r17.s to 10.10.11.0/24 label
RULE 17 -- ACCEPT
#
# Rule 18 (global)
pass in log quick inet proto udp from 172.19.231.128/27 to
212.9.21.214 port { 500, 4500 } label RULE 18 --
Re: Email issues, relay failure, perhaps Jails is causing it.
--As of February 26, 2012 8:20:14 AM +0100, Bernt Hansson is alleged to have said: http://www.uk.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html Have you tried to telnet into the other jailed hostnames and ip-addresses, like telnet rt3.* 25 What does it say? Can you connect? There seems to be either a jail problem or a routing problem You can look at your routing table with netstat -r --As for the rest, it is mine. This is my strong suspicion as well. To separate out what the problem is: 'su' to root in the jailed system. Shut down postfix. (`postfix stop`, or `/etc/rc.d/postfix stop`) Then run `nc -l 25`. This will echo anything that comes in on port 25 direct to your terminal. Then try telneting to it. If it works, the problem is postfix. If it doesn't, restart postfix and ignore it: It's not the problem. Daniel T. Staal --- This email copyright the author. Unless otherwise noted, you are expressly allowed to retransmit, quote, or otherwise use the contents for non-commercial purposes. This copyright will expire 5 years after the author's death, or in 30 years, whichever is longer, unless such a period is in excess of local copyright law. --- ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Email issues, relay failure
On 24/02/2012 21:52, Bender, Chris wrote: Hi, I am responsible for a system I know little about. Sendmail all of a sudden stopped working...the sendmial is supposed to send to another machine. Check /var/log/maillog on both boxes, you should see a log message on the origin machine and the onward machine of the form (I've replaced actual names with CAPS) Feb 25 10:37:32 SERVER1 sm-mta[74139]: q1OIevSE033413-*MSGID*: to=i...@domain.com, delay=15:56:34, xdelay=00:01:15, mailer=esmtp, pri=2919788, relay=SOME.RELAY. [X.X.86.167], dsn=4.0.0, stat=Deferred: Operation timed out with [SERVER] What does the Stat say on the first box, if its anything other than Sent Ok, then it'll say why. ( deferred, refused etc). Check the logs on the 2nd server for the same message. Post extracts from both boxes if you need further help good luck Paul. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Email issues, relay failure
Hi Paul, What is happening is mail is coming from machine A--à sent to a middle machine X which I think is acting as a delivery machine(as I see postfix as a processes) which iisn't the recipient of the mail just Deliverer. It is also a jails machine. Anyway the logs on system A say the following when sending a mail to me through X. Feb 25 13:04:17 ccl_imagpsm sendmail[25091]: q1OFs7e0007106: to=chris.ben...@cell.com, ctladdr=build@ccl_imagpsm.wms.cell.com (500/500), delay=21:10:07, xdelay=00:00:00, mailer=relay, pri=4080533, relay=tools2.wms.cell.com., dsn=4.0.0, stat=Deferred: Connection timed out with tools2.wms.cell.com. I did a tcp dump on system X and I did see packets coming in and out from X on port 25 but nothing came in on the maillog. I then sent the same email I attempted on system A but from system X. That worked and here is the log. Feb 25 13:33:44 tools2 postfix/pickup[20706]: F0986628D: uid=0 from=root Feb 25 13:33:44 tools2 postfix/cleanup[21660]: F0986628D: message-id=20120225133344.f09866...@tools2.wms.cell.com Feb 25 13:33:44 tools2 postfix/qmgr[20707]: F0986628D: from=r...@tools2.wms.cell.com, size=441, nrcpt=1 (queue active) Feb 25 13:33:45 tools2 postfix/smtp[21675]: F0986628D: to=chris.ben...@cell.com, relay=wmsexg01.corp.cell.com[10.200.104.15]:25, delay=0.16, delays=0.03/0.01/0.01/0.11, dsn=2.0.0, status=sent (250 2.0.0 Ok: queued as DC069B18973) Feb 25 13:33:45 tools2 postfix/qmgr[20707]: F0986628D: removed I am loosing much info as many machines are attempting to deliver email. Not sure what to do need a mentor on this. Please help Thanks From: Paul Macdonald [mailto:p...@ifdnrg.com] Sent: Saturday, February 25, 2012 5:42 AM To: Bender, Chris Cc: freebsd-questions@freebsd.org Subject: Re: Email issues, relay failure On 24/02/2012 21:52, Bender, Chris wrote: Hi, I am responsible for a system I know little about. Sendmail all of a sudden stopped working...the sendmial is supposed to send to another machine. Check /var/log/maillog on both boxes, you should see a log message on the origin machine and the onward machine of the form (I've replaced actual names with CAPS) Feb 25 10:37:32 SERVER1 sm-mta[74139]: q1OIevSE033413-MSGID: to=i...@domain.com mailto:i...@domain.com , delay=15:56:34, xdelay=00:01:15, mailer=esmtp, pri=2919788, relay=SOME.RELAY. [X.X.86.167], dsn=4.0.0, stat=Deferred: Operation timed out with [SERVER] What does the Stat say on the first box, if its anything other than Sent Ok, then it'll say why. ( deferred, refused etc). Check the logs on the 2nd server for the same message. Post extracts from both boxes if you need further help good luck Paul. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org mailto:freebsd-questions-unsubscr...@freebsd.org ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Email issues, relay failure
On 25/02/2012 13:41, Bender, Chris wrote: Hi Paul, What is happening is mail is coming from machine A--àsent to a middle machine*X* which I think is acting as a delivery machine(as I see postfix as a processes) which iisn't the recipient of the mail just Deliverer. It is also a jails machine. Anyway the logs on system A say the following when sending a mail to me through X. Feb 25 13:04:17 ccl_imagpsm sendmail[25091]: q1OFs7e0007106: to=chris.ben...@cell.com, ctladdr=build@ccl_imagpsm.wms.cell.com (500/500), delay=21:10:07, xdelay=00:00:00, mailer=relay, pri=4080533, relay=tools2.wms.cell.com., dsn=4.0.0, stat=Deferred: Connection timed out with tools2.wms.cell.com. I did a tcp dump on system X and I did see packets coming in and out from X on port 25 but nothing came in on the maillog. Ok, i don't know Postfix so someone else might have to pick up here. It sounds like there might be a local mailer (submission queue) running on X, but not SMTP. The message from A was that it couldn't connect to X. (Deferred: Connection timed out with tools2.wms.cell.com) what do you get if you try telnetting from A to X telnet tools2.wms.cell.com 25 (if you get a connection, good, try following these instructions to send a mail manually via telnet) http://www.yuki-onna.co.uk/email/smtp.html If not, have you tried restarting postfix on X? Paul. *From:*Paul Macdonald [mailto:p...@ifdnrg.com] *Sent:* Saturday, February 25, 2012 5:42 AM *To:* Bender, Chris *Cc:* freebsd-questions@freebsd.org *Subject:* Re: Email issues, relay failure On 24/02/2012 21:52, Bender, Chris wrote: Hi, I am responsible for a system I know little about. Sendmail all of a sudden stopped working...the sendmial is supposed to send to another machine. Check /var/log/maillog on both boxes, you should see a log message on the origin machine and the onward machine of the form (I've replaced actual names with CAPS) Feb 25 10:37:32 SERVER1 sm-mta[74139]: q1OIevSE033413-*MSGID*: to=i...@domain.com mailto:i...@domain.com, delay=15:56:34, xdelay=00:01:15, mailer=esmtp, pri=2919788, relay=SOME.RELAY. [X.X.86.167], dsn=4.0.0, stat=Deferred: Operation timed out with [SERVER] What does the Stat say on the first box, if its anything other than Sent Ok, then it'll say why. ( deferred, refused etc). Check the logs on the 2nd server for the same message. Post extracts from both boxes if you need further help good luck Paul. ___ freebsd-questions@freebsd.org mailto:freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org mailto:freebsd-questions-unsubscr...@freebsd.org -- - Paul Macdonald IFDNRG Ltd Web and video hosting - t: 0131 5548070 m: 07970339546PLEASE NOTE NEW MOBILE e: p...@ifdnrg.com w: http://www.ifdnrg.com - IFDNRG 40 Maritime Street Edinburgh EH6 6SA - ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Email issues, relay failure
Hi Paul I restarted postfix several times on system X. I even restarted the entire system. The DNS isn't an issue I tried the IP address. I was wondering if there was certificate or Some password issue, is that possible? Something isn't connecting between the two. On telnet w IP it says unable to connect. I know nothing about postfix either. It is weird that I can email from X though. I tried postfix status from MAN and postfix flush but that didn't reveal much. Its weird that the delivery on A says deferred connection timed out but on tcpdump I see the port 25 Traffic seemingly working on system X. Thanks, any postfix/mail braniacs out there? Regards From: Paul Macdonald [mailto:p...@ifdnrg.com] Sent: Saturday, February 25, 2012 9:47 AM To: Bender, Chris Subject: Re: Email issues, relay failure i just tried a dns lookup on tools2.wms.cell.com and got nothing so it looks like you're dns entries are on a local network. If you try telnettting to the IP of X on port 25, you can rule out a DNS issue. Paul. On 25/02/2012 14:35, Bender, Chris wrote: Hi Paul Interesting I hadn't thought if that. Telnetting to port 25 has no results whatsoever. Does it matter that machine X doesn't support telnet though. It only allows SSH. telnet: connect to address 0.0.4.41: Connection refused telnet: Unable to connect to remote host: Connection refused thanks From: Paul Macdonald [mailto:p...@ifdnrg.com] Sent: Saturday, February 25, 2012 9:12 AM To: Bender, Chris Cc: freebsd-questions@freebsd.org Subject: Re: Email issues, relay failure On 25/02/2012 13:41, Bender, Chris wrote: Hi Paul, What is happening is mail is coming from machine A--à sent to a middle machine X which I think is acting as a delivery machine(as I see postfix as a processes) which iisn't the recipient of the mail just Deliverer. It is also a jails machine. Anyway the logs on system A say the following when sending a mail to me through X. Feb 25 13:04:17 ccl_imagpsm sendmail[25091]: q1OFs7e0007106: to=chris.ben...@cell.com mailto:chris.ben...@cell.com , ctladdr=build@ccl_imagpsm.wms.cell.com mailto:build@ccl_imagpsm.wms.cell.com (500/500), delay=21:10:07, xdelay=00:00:00, mailer=relay, pri=4080533, relay=tools2.wms.cell.com., dsn=4.0.0, stat=Deferred: Connection timed out with tools2.wms.cell.com. I did a tcp dump on system X and I did see packets coming in and out from X on port 25 but nothing came in on the maillog. Ok, i don't know Postfix so someone else might have to pick up here. It sounds like there might be a local mailer (submission queue) running on X, but not SMTP. The message from A was that it couldn't connect to X. (Deferred: Connection timed out with tools2.wms.cell.com) what do you get if you try telnetting from A to X telnet tools2.wms.cell.com 25 (if you get a connection, good, try following these instructions to send a mail manually via telnet) http://www.yuki-onna.co.uk/email/smtp.html If not, have you tried restarting postfix on X? Paul. From: Paul Macdonald [mailto:p...@ifdnrg.com] Sent: Saturday, February 25, 2012 5:42 AM To: Bender, Chris Cc: freebsd-questions@freebsd.org Subject: Re: Email issues, relay failure On 24/02/2012 21:52, Bender, Chris wrote: Hi, I am responsible for a system I know little about. Sendmail all of a sudden stopped working...the sendmial is supposed to send to another machine. Check /var/log/maillog on both boxes, you should see a log message on the origin machine and the onward machine of the form (I've replaced actual names with CAPS) Feb 25 10:37:32 SERVER1 sm-mta[74139]: q1OIevSE033413-MSGID: to=i...@domain.com mailto:i...@domain.com , delay=15:56:34, xdelay=00:01:15, mailer=esmtp, pri=2919788, relay=SOME.RELAY. [X.X.86.167], dsn=4.0.0, stat=Deferred: Operation timed out with [SERVER] What does the Stat say on the first box, if its anything other than Sent Ok, then it'll say why. ( deferred, refused etc). Check the logs on the 2nd server for the same message. Post extracts from both boxes if you need further help good luck Paul. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org mailto:freebsd-questions-unsubscr...@freebsd.org -- - Paul Macdonald IFDNRG Ltd Web and video hosting - t: 0131 5548070 m: 07970339546 PLEASE NOTE NEW MOBILE e: p...@ifdnrg.com w: http://www.ifdnrg.com - IFDNRG 40 Maritime Street Edinburgh EH6 6SA - -- - Paul Macdonald IFDNRG Ltd Web and video hosting - t: 0131 5548070 m: 07970339546 PLEASE NOTE NEW MOBILE e: p...@ifdnrg.com w: http://www.ifdnrg.com - IFDNRG
Re: Email issues, relay failure
On Sat, 25 Feb 2012 10:26:38 -0500 Bender, Chris articulated: any postfix/mail braniacs out there? If you are having a problem with Postfix, the absolute best place to get help with your problem is the Postfix forum. TO REPORT A PROBLEM see http://www.postfix.org/DEBUG_README.html#mail quote Output from postconf -n. Please do not send your main.cf file, or 500+ lines of postconf output. Better, provide output from the postfinger tool. This can be found at http://ftp.wl0.org/SOURCES/postfinger. /quote Depending on your version of Postfix, postconf -Mf postconf -nf will output all the information required. Just copy it and submit it the Postfix forum. -- Jerry ♔ Disclaimer: off-list followups get on-list replies or get ignored. Please do not ignore the Reply-To header. __ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Email issues, relay failure
Hi Jon Thanks. There aren't any firewalls between the devices but they are far apart. I can telnet from x to a and I can ssh from a to x. I think you are right in focusing on the connection time out from A to X , i looked on X for a service that isnt running Which makes this fail but I am not sure Which services. I see postfix and sendmail running and I have restarted them. I never see mail delivery from A in mailog on X Thanks On Feb 25, 2012, at 1:03 PM, Jon Radel j...@radel.com wrote: On 2/25/12 10:26 AM, Bender, Chris wrote: On telnet w IP it says unable to connect. ... Its weird that the delivery on A says deferred connection timed out but on tcpdump I see the port 25 If you can't establish a TCP connection from A to your relay server on port 25, I'd expect all of the above. If you can't establish a TCP connection to port 25 at all from A, I'd stop focusing on the details of the e-mail server on the relay machine (as they're likely to be beside the point) and start focusing on what is blocking the traffic from A. Have you audited all the firewalls involved? To be really focused, if you see traffic (both ways) at the relay server when A tries to talk to port 25, but A is convinced that no TCP connection is established, either you're stomping on things at the relay server (do your attempts to telnet to port 25 fail immediately or just sit there for a good long time and then fail?), the reply packets from relay to A are getting mis-routed, or A is ignoring the packets coming in from the relay. Can you ping from the relay to A? There's a distinct difference between failure to establish a TCP connection (look to the network stuff) and the e-mail server giving you an error response rejecting your attempt to transfer mail or just quietly loosing the mail (look to the e-mail servers). -- --Jon Radel j...@radel.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Email issues, relay failure
On 2/25/12 10:26 AM, Bender, Chris wrote: On telnet w IP it says unable to connect. ... Its weird that the delivery on A says deferred connection timed out but on tcpdump I see the port 25 If you can't establish a TCP connection from A to your relay server on port 25, I'd expect all of the above. If you can't establish a TCP connection to port 25 at all from A, I'd stop focusing on the details of the e-mail server on the relay machine (as they're likely to be beside the point) and start focusing on what is blocking the traffic from A. Have you audited all the firewalls involved? To be really focused, if you see traffic (both ways) at the relay server when A tries to talk to port 25, but A is convinced that no TCP connection is established, either you're stomping on things at the relay server (do your attempts to telnet to port 25 fail immediately or just sit there for a good long time and then fail?), the reply packets from relay to A are getting mis-routed, or A is ignoring the packets coming in from the relay. Can you ping from the relay to A? There's a distinct difference between failure to establish a TCP connection (look to the network stuff) and the e-mail server giving you an error response rejecting your attempt to transfer mail or just quietly loosing the mail (look to the e-mail servers). -- --Jon Radel j...@radel.com
Re: Email issues, relay failure
Jon Radel wrote: On 2/25/12 10:26 AM, Bender, Chris wrote: On telnet w IP it says unable to connect. ... Its weird that the delivery on A says deferred connection timed out but on tcpdump I see the port 25 If you can't establish a TCP connection from A to your relay server on port 25, I'd expect all of the above. If you can't establish a TCP connection to port 25 at all from A, I'd stop focusing on the details of the e-mail server on the relay machine (as they're likely to be beside the point) and start focusing on what is blocking the traffic from A. Have you audited all the firewalls involved? To be really focused, if you see traffic (both ways) at the relay server when A tries to talk to port 25, but A is convinced that no TCP connection is established, either you're stomping on things at the relay server (do your attempts to telnet to port 25 fail immediately or just sit there for a good long time and then fail?), the reply packets from relay to A are getting mis-routed, or A is ignoring the packets coming in from the relay. Can you ping from the relay to A? There's a distinct difference between failure to establish a TCP connection (look to the network stuff) and the e-mail server giving you an error response rejecting your attempt to transfer mail or just quietly loosing the mail (look to the e-mail servers). It can also depend on a difference between residential vs business account at the ISP between them. If it was working fine and absolutely nothing was changed at either end, one posibility is an ISP implemented a policy of forcing mail submission to port 587, and whatever blocking they then started on port 25 is what broke the connection. -Mike ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Email issues, relay failure
2012-02-25 19:39, Bender, Chris skrev: There aren't any firewalls between the devices but they are far apart. I can telnet from x to a and I can ssh from a to x. Have you tried the correct IP from A to X? Try dig -x X-IP and dig X-hostname. Can you ping X from A? Try telnet to X from A with the hostname of X. Have X changed IP-address? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Email issues, relay failure
NP on all counts. Names and IPs are same results using both digson A and resolving. In fact both are identical results on A and B. I can easily ssh user@X-Username From a too. The issue doesn't appear be at getting to X the issues is something to do with the service on X. I amnot sure if postfix has certs, or password. I don't see anything on the maillog of X when the email from A Is sent to it. Maillog on A says connection timed out. Thanks Regards -Original Message- From: Bernt Hansson [mailto:b...@bananmonarki.se] Sent: Saturday, February 25, 2012 4:25 PM To: Bender, Chris Cc: Jon Radel; freebsd-questions@freebsd.org Subject: Re: Email issues, relay failure 2012-02-25 19:39, Bender, Chris skrev: There aren't any firewalls between the devices but they are far apart. I can telnet from x to a and I can ssh from a to x. Have you tried the correct IP from A to X? Try dig -x X-IP and dig X-hostname. Can you ping X from A? Try telnet to X from A with the hostname of X. Have X changed IP-address? ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Email issues, relay failure
2012-02-25 22:44, Bender, Chris skrev: NP on all counts. Names and IPs are same results using both digson A and resolving. In fact both are identical results on A and B. I can easily ssh user@X-Username From a too. The issue doesn't appear be at getting to X the issues is something to do with the service on X. I amnot sure if postfix has certs, or password. I don't see anything on the maillog of X when the email from A Is sent to it. Maillog on A says connection timed out. What is the output on X for ps ax|grep libexec/postfix/smtpd ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Email issues, relay failure
tools2# ps ax|grep libexec/postfix/smtpdps ax|grep libexec/postfix/smtpd tools2# ps ax|grep libexec/postfix/smtpd 53297 20 R+J0:00.00 grep libexec/postfix/smtpd tools2# ps -af | grep smtp 53300 20 R+J0:00.00 grep smtp tools2# ps -af | grep postfix 53305 20 R+J0:00.00 grep postfix tools2# ps -ax| more PID TT STAT TIME COMMAND 20417 ?? SsJ0:00.09 /usr/sbin/syslogd -ss 20482 ?? SsJ0:00.45 /usr/local/libexec/vsftpd 20603 ?? IsJ0:00.00 /usr/local/sbin/squid -D 20610 ?? SJ 0:01.97 (squid) -D (squid) 20699 ?? SsJ0:00.26 /usr/local/libexec/postfix/master I don't see sendmail or smtp -Original Message- From: Bernt Hansson [mailto:b...@bananmonarki.se] Sent: Saturday, February 25, 2012 4:53 PM To: Bender, Chris Cc: Jon Radel; freebsd-questions@freebsd.org Subject: Re: Email issues, relay failure 2012-02-25 22:44, Bender, Chris skrev: NP on all counts. Names and IPs are same results using both digson A and resolving. In fact both are identical results on A and B. I can easily ssh user@X-Username From a too. The issue doesn't appear be at getting to X the issues is something to do with the service on X. I amnot sure if postfix has certs, or password. I don't see anything on the maillog of X when the email from A Is sent to it. Maillog on A says connection timed out. What is the output on X for ps ax|grep libexec/postfix/smtpd ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Email issues, relay failure
2012-02-25 22:52, Bernt Hansson skrev: 2012-02-25 22:44, Bender, Chris skrev: NP on all counts. Names and IPs are same results using both digson A and resolving. In fact both are identical results on A and B. I can easily ssh user@X-Username From a too. The issue doesn't appear be at getting to X the issues is something to do with the service on X. I amnot sure if postfix has certs, or password. I don't see anything on the maillog of X when the email from A Is sent to it. Maillog on A says connection timed out. What is the output on X for ps ax|grep libexec/postfix/smtpd Also try, on X, netstat -aptcp | grep smtp. It should be something along the line of; tcp40 0 *.smtp*.*LISTEN Is the postfix machine running freebsd? Found this on postfix.org http://www.postfix.org/smtpd.8.html As of Postfix version 2.3, the SMTP server refuses to receive mail from the network when it runs with non $mail_owner privileges $mail_owner = http://www.postfix.org/postconf.5.html#mail_owner ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Email issues, relay failure
Hi Brent, Thanks for that, I am still digesting it. tools2# uname -a FreeBSD tools2 8.2-RELEASE-p2 FreeBSD 8.2-RELEASE-p2 # So I put a 0 in the first two octets of the ip address below, but that IP address is A. I am not sure what that means. I was horsing around and tried to start sendmail On X then I tried to send an email from A. I have no idea what all that means. Here is netstat results: netstat: kvm not available: /dev/mem: No such file or directory tcp4 0 0 tools2.smtp0.0.81.10.33679 SYN_RCVD tcp4 0 0 tools2.smtp*.*LISTEN What is non $mail_owner privileges or how to determine that? tools2# postconf -d | grep mail_version mail_version = 2.7.0 milter_macro_v = $mail_name $mail_version I am still not sure about the non mail owner issue yet, but I would think because this has run in the past that it wouldn't have changed. And how do I run smtp as a non mail user when I am root? Hopfully we are getting somewhere. Thanks -Original Message- From: Bernt Hansson [mailto:b...@bananmonarki.se] Sent: Saturday, February 25, 2012 5:09 PM To: Bender, Chris Cc: freebsd-questions@freebsd.org; Jon Radel Subject: Re: Email issues, relay failure 2012-02-25 22:52, Bernt Hansson skrev: 2012-02-25 22:44, Bender, Chris skrev: NP on all counts. Names and IPs are same results using both digson A and resolving. In fact both are identical results on A and B. I can easily ssh user@X-Username From a too. The issue doesn't appear be at getting to X the issues is something to do with the service on X. I amnot sure if postfix has certs, or password. I don't see anything on the maillog of X when the email from A Is sent to it. Maillog on A says connection timed out. What is the output on X for ps ax|grep libexec/postfix/smtpd Also try, on X, netstat -aptcp | grep smtp. It should be something along the line of; tcp40 0 *.smtp*.*LISTEN Is the postfix machine running freebsd? Found this on postfix.org http://www.postfix.org/smtpd.8.html As of Postfix version 2.3, the SMTP server refuses to receive mail from the network when it runs with non $mail_owner privileges $mail_owner = http://www.postfix.org/postconf.5.html#mail_owner ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Email issues, relay failure
2012-02-25 23:29, Bender, Chris skrev: Hi Brent, Thanks for that, I am still digesting it. tools2# uname -a FreeBSD tools2 8.2-RELEASE-p2 FreeBSD 8.2-RELEASE-p2 # So I put a 0 in the first two octets of the ip address below, but that IP address is A. I am not sure what that means. I was horsing around and tried to start sendmail On X then I tried to send an email from A. I have no idea what all that means. Here is netstat results: netstat: kvm not available: /dev/mem: No such file or directory tcp4 0 0 tools2.smtp0.0.81.10.33679 SYN_RCVD tcp4 0 0 tools2.smtp*.*LISTEN Ok. I'm stabbing in the dark here, but didn't you say that X was a jail system? Is every postfix process in a jail? I have never used a jailed system. So my WILD guess it's a something with jail, or jail setup. What is non $mail_owner privileges or how to determine that? tools2# postconf -d | grep mail_version mail_version = 2.7.0 milter_macro_v = $mail_name $mail_version I am still not sure about the non mail owner issue yet, but I would think because this has run in the past that it wouldn't have changed. And how do I run smtp as a non mail user when I am root? Hopfully we are getting somewhere. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
RE: Email issues, relay failure, perhaps Jails is causing it.
Hi Brent Yes the system we are calling X, is jailed by another system. Here is the jailer system: zs1# netstat -aptcp | grep smtp tcp4 0 0 tools2.smtp10.156.31.20.45081 SYN_RCVD tcp4 0 0 tools2.smtp*.*LISTEN tcp4 0 0 rt3.smtp *.*LISTEN tcp4 0 0 npims.smtp *.*LISTEN tcp4 0 0 wiki.smtp *.*LISTEN tcp4 0 0 localhost.smtp *.*LISTEN I see smtp running on several systems it has jailed including system X. I see above a smtp conversation between system X and 10.156.31.20. But that is never delivered from what I have seen. I am not sure about the queues Or how to see in postfix what exactly is happening? I think a lot of this stopped working after we rebooted the jailer system. Jails really should have no affect on This it is a virtual machine essentially, at least that is my thoughts. What happen to your thought that snmp needs to run as a non mailer system? Thanks regards -Original Message- From: Bernt Hansson [mailto:b...@bananmonarki.se] Sent: Saturday, February 25, 2012 6:11 PM To: Bender, Chris Cc: freebsd-questions@freebsd.org; Jon Radel Subject: Re: Email issues, relay failure 2012-02-25 23:29, Bender, Chris skrev: Hi Brent, Thanks for that, I am still digesting it. tools2# uname -a FreeBSD tools2 8.2-RELEASE-p2 FreeBSD 8.2-RELEASE-p2 # So I put a 0 in the first two octets of the ip address below, but that IP address is A. I am not sure what that means. I was horsing around and tried to start sendmail On X then I tried to send an email from A. I have no idea what all that means. Here is netstat results: netstat: kvm not available: /dev/mem: No such file or directory tcp4 0 0 tools2.smtp0.0.81.10.33679 SYN_RCVD tcp4 0 0 tools2.smtp*.* LISTEN Ok. I'm stabbing in the dark here, but didn't you say that X was a jail system? Is every postfix process in a jail? I have never used a jailed system. So my WILD guess it's a something with jail, or jail setup. What is non $mail_owner privileges or how to determine that? tools2# postconf -d | grep mail_version mail_version = 2.7.0 milter_macro_v = $mail_name $mail_version I am still not sure about the non mail owner issue yet, but I would think because this has run in the past that it wouldn't have changed. And how do I run smtp as a non mail user when I am root? Hopfully we are getting somewhere. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Email issues, relay failure, perhaps Jails is causing it.
2012-02-26 00:54, Bender, Chris skrev: Hi Brent Yes the system we are calling X, is jailed by another system. Here is the jailer system: zs1# netstat -aptcp | grep smtp tcp4 0 0 tools2.smtp10.156.31.20.45081 SYN_RCVD tcp4 0 0 tools2.smtp*.*LISTEN tcp4 0 0 rt3.smtp *.*LISTEN tcp4 0 0 npims.smtp *.*LISTEN tcp4 0 0 wiki.smtp *.*LISTEN tcp4 0 0 localhost.smtp *.*LISTEN Here is about jails; http://www.uk.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html Have you tried to telnet into the other jailed hostnames and ip-addresses, like telnet rt3.* 25 What does it say? Can you connect? There seems to be either a jail problem or a routing problem You can look at your routing table with netstat -r ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Email issues, relay failure
Hi, I am responsible for a system I know little about. Sendmail all of a sudden stopped working...the sendmial is supposed to send to another machine. The senmail locally looks to deliver email to a que and the que looks to forward to another machine. However this looks to break.Can somebody help me diagnose and repair. It may be the remote machine never gets the email and thusly never delivers the email. Here is local machine response to my sending the following command echo test email from ccl `date` | mailx -s test email from ccl `date` c...@cell.com The que message show the following.. Running /var/spool/mqueue/q1OKcmpH017170 (sequence 1 of 20) c...@cell.com... Connecting to tools.wms.cellularatsea.com. via relay... c...@cell.com... Deferred: Connection timed out with tools.wms.cell.com. I can ping this machine via ping tools Is there supposed to be some type of handler on tools to accept messages. How would I know if it were postfix or sendmail? Is this possible to be on remote machine. CB Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Email issues, relay failure
On 02/24/2012 13:52, Bender, Chris wrote: Hi, I am responsible for a system I know little about. Sendmail all of a sudden stopped working...the sendmial is supposed to send to another machine. The senmail locally looks to deliver email to a que and the que looks to forward to another machine. However this looks to break.Can somebody help me diagnose and repair. It may be the remote machine never gets the email and thusly never delivers the email. Here is local machine response to my sending the following command echo test email from ccl `date` | mailx -s test email from ccl `date` c...@cell.com The que message show the following.. Running /var/spool/mqueue/q1OKcmpH017170 (sequence 1 of 20) c...@cell.com... Connecting to tools.wms.cellularatsea.com. via relay... c...@cell.com... Deferred: Connection timed out with tools.wms.cell.com. I can ping this machine via ping tools Is there supposed to be some type of handler on tools to accept messages. How would I know if it were postfix or sendmail? Is this possible to be on remote machine. CB Thanks ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org telnet remote_machine 25 does it connect to a mailer daemon? -- Dave Robison Sales Solution Architect II FIS Banking Solutions 510/621-2089 (w) 530/518-5194 (c) 510/621-2020 (f) da...@vicor.com david.robi...@fisglobal.com _ The information contained in this message is proprietary and/or confidential. If you are not the intended recipient, please: (i) delete the message and all copies; (ii) do not disclose, distribute or use the message in any manner; and (iii) notify the sender immediately. In addition, please be aware that any message addressed to our domain is subject to archiving and review by persons other than the intended recipient. Thank you. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
Re: Email issues, relay failure
On Fri, 24 Feb 2012, Robison, Dave wrote: On 02/24/2012 13:52, Bender, Chris wrote: Sendmail all of a sudden stopped working...the sendmial is supposed to send to another machine. ...snip... echo test email from ccl `date` | mailx -s test email from ccl `date` c...@cell.com The que message show the following.. Running /var/spool/mqueue/q1OKcmpH017170 (sequence 1 of 20) c...@cell.com... Connecting to tools.wms.cellularatsea.com. via relay... c...@cell.com... Deferred: Connection timed out with tools.wms.cell.com. I can ping this machine via ping tools Is there supposed to be some type of handler on tools to accept messages. How would I know if it were postfix or sendmail? telnet remote_machine 25 does it connect to a mailer daemon? How you would know: You should see something like this: $ telnet remote_machine 25 Trying 192.168.1.1... Connected to remote_machine.mydomain.com Escape character is '^]'. 220 remote_machine.mydomain.com ESMTP Sendmail 8.14.3/8.14.3; Fri, 24 Feb 2012 19:44:05 -0500 (EST) Note the 'Sendmail'. I don't have a postfix server handy, but presumably it would not emit the S word. -- Chris Hill ch...@monochrome.org ** [ Busy Expunging / ] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
