Re: postfix and DNs server
Am 28.05.2012 13:57, schrieb Amira Othman: I am using postfix 2.8.4 on centos 5.8 and recently I installed bind9 on the same server to have my own DNS server. I didn't change MX record of mail server as I am still testing configuration and newbie but I noticed that outgoing mails stopped being delivered and I don't know why as I don't change anything in postfix or MX records what may cause that? * you do not provide any informations * our crystal ball does not work however, if your OUTGOING mail stopped it sounds like /etc/resolv.conf points to your local nameserver which does not work signature.asc Description: OpenPGP digital signature
Re: postfix and DNs server
Amira Othman: Hi all I am using postfix 2.8.4 on centos 5.8 and recently I installed bind9 on the same server to have my own DNS server. I didn't change MX record of mail server as I am still testing configuration and newbie but I noticed that outgoing mails stopped being delivered and I don't know why as I don't change anything in postfix or MX records what may cause that? Postfix logs all attempts to send or receive mail, whether or not these attempts are successful. I suggest you look there first. Wietse
RE: postfix and DNs server
Amira Othman: Hi all I am using postfix 2.8.4 on centos 5.8 and recently I installed bind9 on the same server to have my own DNS server. I didn't change MX record of mail server as I am still testing configuration and newbie but I noticed that outgoing mails stopped being delivered and I don't know why as I don't change anything in postfix or MX records what may cause that? Postfix logs all attempts to send or receive mail, whether or not these attempts are successful. I suggest you look there first. Wietse This is log error from=a.oth...@cairosource.com, size=11908, nrcpt=1 (queue active) May 28 10:20:28 cairosource postfix/smtp[32092]: AC8596E684AB: to=test_ca...@yahoo.com, relay=mx01.hmc1.comcast.net[76.96.53.13]:25, delay=2.1, delays=1.9/0.02/0.24/0, dsn=4.0.0, status=deferred (host mx01.hmc1.comcast.net[76.96.53.13] refused to talk to me: 554 imta01.westchester.pa.hmc1.comcast.net bizsmtp x.x.x.x Comcast requires that all mail servers must have a PTR record with a valid Reverse DNS entry. Currently your mail server does not fill that requirement. For more information, refer to:http://worknetkc.st.comcastsupport.com/sdccommon/asp/defcontent_view.asp? ssfromlink=truesprt_cid=bb859780-1131-4fbf-b307-4798d1e628f0) My resolve.conf contains just nameserver 127.0.0.1 and I didn't setup reverse DNS yet. But MX record of this domain is not on my DNS it's another DNS server.
Re: postfix and DNs server
Am 28.05.2012 14:22, schrieb Amira Othman: from=a.oth...@cairosource.com, size=11908, nrcpt=1 (queue active) May 28 10:20:28 cairosource postfix/smtp[32092]: AC8596E684AB: to=test_ca...@yahoo.com, relay=mx01.hmc1.comcast.net[76.96.53.13]:25, delay=2.1, delays=1.9/0.02/0.24/0, dsn=4.0.0, status=deferred (host mx01.hmc1.comcast.net[76.96.53.13] refused to talk to me: 554 imta01.westchester.pa.hmc1.comcast.net bizsmtp x.x.x.x Comcast requires that all mail servers must have a PTR record with a valid Reverse DNS entry. Currently your mail server does not fill that requirement. did you read the message? your outgoing server seems not to have a proper PTR it would be really helpful if you provide informations * what is your domain * what public IP has your outgoing MTA My resolve.conf contains just nameserver 127.0.0.1 this is bad in context recently I installed bind9 on the same server! why do you use a TESTING nameservr for your MTA? and I didn't setup reverse DNS yet if your MTA has no reverse DNS outside you can not expect that someone accepts mail from you But MX record of this domain is not on my DNS it's another DNS server MX rceord has really NOTHING to do with outgoing mail! signature.asc Description: OpenPGP digital signature
Re: postfix and DNs server
Amira Othman: Comcast requires that all mail servers must have a PTR record with a valid Reverse DNS entry. Currently your mail server does not fill that requirement. For more information, refer to: http://worknetkc.st.comcastsupport.com/sdccommon/asp/defcontent_view.asp? ssfromlink=truesprt_cid=bb859780-1131-4fbf-b307-4798d1e628f0) You need to set up a PTR record for your server's IP address, an A record that resolves the name in the PTR record to your server's IP address, and perhaps Postfix needs to be configured to send EHLO with the name in the PTR record. All this has nothing to do with the MX record. Wietse
