Re: sendmail problems
- From: Duane Winner <dwinner@xxxxxxxxxxx>
- Date: Thu, 18 Oct 2007 15:09:28 -0400
Derek Ragona wrote:
At 01:27 PM 10/18/2007, Duane Winner wrote:Can't find much wrong with DNS:
Derek Ragona wrote:
At 06:15 PM 10/17/2007, Duane Winner wrote:connection to
Derek Ragona wrote:
At 04:07 PM 10/17/2007, Duane Winner wrote:
Hello,
I need help to resolve a problem with my sendmail server.
In my /var/log/maillog, I've been seeing:
sm-mta[1753]: l9H4EoAn001753: outbound-mail-10.bluehost.com
[69.89.17.210] did not issue MAIL/EXPN/VRFY/ETRN during
but thenwrongIPv4
I use this server to manage mailman lists, so I knew something was
when I started notice that my own list posts (using a bluehost.com
account) were not showing up.
So I looked in the logs and noticed the above.
At first I thought it might be bluehost.com acting up again,
[64.233.166.176]tried to send mail from a gmail.com account. Same thing:
sm-mta[1785]: l9H4OdFq001785: py-out-1112.google.com
which ifdid not issue MAIL/EXPN/VRFY/ETRN during connection to IPv4
It accepts fine from my company's external email server (different
domain, different network), and also accepts from my att.net email
account, and many others who post to my lists.
I'm not sure where to even begin looking. Any help appreciated!
-DW
Are you running only IPv4? or are you running IPv6? Or both?
IPv4 only. When I restart sendmail, I get the following output,
ProtocolI'm interpreting correctly, means that sendmail isn't going to try to
use IPv6 when it's running:
Oct 17 19:13:23 mymailserver sm-mta[33703]: starting daemon (8.13.6):
SMTP+queueing@00:30:00
Oct 17 19:13:23 mymailserver sm-mta[33703]: NOQUEUE: SYSERR(root):
opendaemonsocket: daemon IPv6: can't create server SMTP socket:
not supported
Oct 17 19:13:23 mymailserver sm-mta[33703]: NOQUEUE: SYSERR(root):
opendaemonsocket: daemon IPv6: optional socket disabled
Oct 17 19:13:23 mymailserver sm-msp-queue[33707]: starting daemon
(8.13.6): queueing@00:30:00
It looks like you are trying to run sendmail on IPv6. You can turn on
or off support for IPv6 in the DaemonPortOptions in your *.cf files in
/etc/mail. I would check those and also check your IP stack
configuration doing:
ifconfig -a
Still broken; I disabled IPv6 in my cf's, and sendmail doesn't even try
to listen on IPv6 now when I restart it.
I don't think it did anyway before, it was just trying to but I don't
have IPv6 in my stack since I disable it in the kernel config, so it
just ignored ipv6 after startup.
I think something else is going on. The weird thing is that it's just
certain mail hosts that it's rejecting.
Check the DNS forward and reverse of the rejected hosts. It may be a
DNS issue.
-Derek
FYI: I had dnsbl enabled (which worked fine for the past couple years on
this server), but disabled that too, and still no luck.
dig -x 69.89.18.10
; <<>> DiG 9.3.2 <<>> -x 69.89.18.10
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 48077
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 2
;; QUESTION SECTION:
;10.18.89.69.in-addr.arpa. IN PTR
;; ANSWER SECTION:
10.18.89.69.in-addr.arpa. 86279 IN PTR
outbound-mail-41.bluehost.com.
;; AUTHORITY SECTION:
18.89.69.in-addr.arpa. 86279 IN NS ns3.bluehost.com.
18.89.69.in-addr.arpa. 86279 IN NS ns1.bluehost.com.
18.89.69.in-addr.arpa. 86279 IN NS ns2.bluehost.com.
;; ADDITIONAL SECTION:
ns1.bluehost.com. 171739 IN A 74.220.195.31
ns2.bluehost.com. 171739 IN A 69.89.16.4
;; Query time: 0 msec
;; SERVER: 10.20.237.8#53(10.20.237.8)
;; WHEN: Thu Oct 18 15:05:42 2007
;; MSG SIZE rcvd: 171
dig -x 64.233.166.177
; <<>> DiG 9.3.2 <<>> -x 64.233.166.177
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30043
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 4, ADDITIONAL: 4
;; QUESTION SECTION:
;177.166.233.64.in-addr.arpa. IN PTR
;; ANSWER SECTION:
177.166.233.64.in-addr.arpa. 85685 IN PTR py-out-1112.google.com.
;; AUTHORITY SECTION:
166.233.64.in-addr.arpa. 85304 IN NS ns1.google.com.
166.233.64.in-addr.arpa. 85304 IN NS ns2.google.com.
166.233.64.in-addr.arpa. 85304 IN NS ns3.google.com.
166.233.64.in-addr.arpa. 85304 IN NS ns4.google.com.
;; ADDITIONAL SECTION:
ns1.google.com. 171704 IN A 216.239.32.10
ns2.google.com. 171704 IN A 216.239.34.10
ns3.google.com. 171704 IN A 216.239.36.10
ns4.google.com. 171704 IN A 216.239.38.10
;; Query time: 0 msec
;; SERVER: 10.20.237.8#53(10.20.237.8)
;; WHEN: Thu Oct 18 15:07:09 2007
;; MSG SIZE rcvd: 217
--
This message has been scanned for viruses and
dangerous content by *MailScanner* <http://www.mailscanner.info/>, and is
believed to be clean.
MailScanner thanks transtec Computers <http://www.transtec.co.uk/> for
their support.
_______________________________________________
freebsd-questions@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "freebsd-questions-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: sendmail problems
- From: Derek Ragona
- Re: sendmail problems
- References:
- sendmail problems
- From: Duane Winner
- Re: sendmail problems
- From: Derek Ragona
- Re: sendmail problems
- From: Duane Winner
- Re: sendmail problems
- From: Derek Ragona
- Re: sendmail problems
- From: Duane Winner
- Re: sendmail problems
- From: Derek Ragona
- sendmail problems
- Prev by Date: Re: Why 7.0 is so late ?
- Next by Date: Re: Calling syscalls through int 0x80 documentation?
- Previous by thread: Re: sendmail problems
- Next by thread: Re: sendmail problems
- Index(es):
Relevant Pages
|
