sorry about this. I guess it has nothing to do with mx records. It is the remote server telling me their server is not able to accept mail.
On Sun, Oct 13, 2013 at 12:04 AM, Roman Gelfand <rgelfa...@gmail.com> wrote: > but I am geting the following message > > said: 451 Temporary local problem - please try later (in reply to > RCPT TO command)) > > it is stuck forever in a queue until it fails. Is there a setting I > need to set so it should be accepted. > > On Sat, Oct 12, 2013 at 11:35 PM, Noel Jones <njo...@megan.vbhcs.org> wrote: >> On 10/12/2013 10:19 PM, Roman Gelfand wrote: >>> Looking through the logs, I have noticed an attempt to send out mail >>> which temporary local fails. I did a dig mx and noticed there is no >>> mx record. I then tried to connect to the email address domain >>> portion of the name. Sure enough, I was able to connect. >>> >>> Is this legitimate configuration of mail server? >> >> MX records are not required. If there is no MX record, use the >> domain A record. This is required RFC behavior. >> >> >>> >>> Is there a way to configure postfix saying that if there is no mx >>> record attempt to connect to connect using domain portion? >> >> Yes, this is the required behavior. This is not configurable. >> >>> What is >>> the exposure? >> >> Apparently postfix is working properly. >> >> Note that historically, lack of an MX record is not a suitable spam >> indicator. Spammers easily set up MX records, along with SPF, DKIM, >> etc. using automated tools. There are better ways to catch spam. >> >> There is no "exposure". The presence of lack of an MX record neither >> adds nor detracts from the reputation of a client. >> >> >> >> >> -- Noel Jones
