: Why is an email failing RFC2822 specifications? I am sending an email to a maximum of 14 gmail users. They are part of a small group of paid subscribers. In a send to all 14 1 or 2 are

@Margaret670

I sent an email from the standard web interface and then worked out it was the form. Looking in the code there were 2 lines causing errors


$headers .= "To: $nameto " . $newLine;

$headers .= "From: $namefrom " . $newLine;


As these were being added to the header they were being duplicated and gmail did not like it.

Vote Up Vote Down

@Gloria169

You're most likely not authorized to send e-mail from that system for the domain you're trying to use in the 'From' address per SPF. The webserver should use the domain's authorized mail server as a smart relay.

A lot of systems don't give useful error messages when they think you're a spammer, as it just tells the spammer what they need to fix to get their e-mails through.

There's a chance that the emails that look like they're going through are really being delivered to the recipients' spam folders, and the random fails are to give you a warning so in case it's something done in error you have a warning to correct the problem.

(and this would likely have been better to ask at Server Fault, being an SMTP question; I haven't had to administer an SMTP server in 9 years, so I know of SPF, but I've never had to deal with the issue that it causes)

Vote Up Vote Down

@Kevin317

Everything I've seen about this error code says it indicates the receiving mail box was unavailable at the time. There could be many reasons for this from their server being down, to the mailbox being full/non-existent, to more esoteric things. Do you get the message more often for any particular recipients, and have you asked them if they've had downtime, etc?

EDIT
Getting 550 5.7.1 apparently means that the message was rejected, due to the "submitter" (presumably your PHP script) not being authorized to send on behalf of the domain involved. There are no easy permalinks, but do an in-page search for "5.7.1" in RFC 4405 and RFC 4408. Another article I found says the message can indicate you being on a blacklist. While that's obviously not true since the messages do sometimes go through, it does suggest again that you're triggering some checking/spam mechanism, which would be consistent with the authorization concept in the RFCs. That should give you a bit more to work with for hunting this down.

But it seems like it might be time for you to go through support channels for the script you're using, unless it's some standard tool. I've never encountered that before.

Vote Up Vote Down