Relay access denied


#1

Hello,

I work with VeriSign and we’re doing some Q&A with a new product of ours that deals with anti-spam. I’m using my domain for testing and changed the MX record to mail.emailsecurity.verisign.com and I set the inbound SMTP server info on VeriSign’s end to mail.alaive.com. When I
try to send an email to allen@alaive.com, it bounces immediately. Here is the header info:

Final-Recipient: rfc822; allen@alaive.com
Action: failed
Status: 5.0.0
Diagnostic-Code: X-Postfix; host mail.alaive.com[66.33.217.4] said: 554
allen@alaive.com: Relay access denied (in reply to RCPT TO command)

Can you tell me what’s going on here and on which end it is failing?

Thank you.

-Allen


#2

Once you change the MX record, our mail servers aren’t configured to accept the mail locally anymore.

What you need to do in this case is leave the mail service active, and then have support manually set it so that our MX isn’t generated but so that the mail service is still active… then they can add the necessary MX record by hand. There’s currently no way to do what you want to do here directly from the panel. If you put in a support request with Attn to Ralph, he should be able to get you setup.

Also, you can’t count on being able to send back to the host for “mail.example.com”. You’d want to configure it to send to one or both MXs (on our side) for the domain - mx1.postal.mail.dreamhost.com and mx2.postal.mail.dreamhost.com in this case. Even this is not guaranteed to work forever - it probably will, but we don’t officially “support” configurations like this.