Tina,
this is an MTA (mail transfer agent) level failure, (typically people
use mail user agents like eudora/thunderbird/outlook/mutt/pine or one of
the many webmail processes to generate their mail, and these MUAs
deliver to an MTA at the user's ISP).
It looks like the comporium.net mail exchanger server (MX) is
misconfigured, unwell, a bit draconian about who can send mail to it, or
it's DNS servers may be slow. The HELO (or extended hello: EHLO) is the
second part of the mail transfer conversation, and the 'client' MTA is
expecting a '250' welcome-type response from the comporium 'server'. It
appears this is not happening within a reasonable amount of time. It is
fairly common for MTAs to check the domain name offered in the HELO
against the internet address (helping to make a decision about how
SPAMmy the message is) before responding, but if the domain lookup takes
too long an MTA can give up.
The 451 is a 'temporary local processing failure' and the reporting MTA
(google?) will keep trying up until the mail timeout. This timeout is
often 4 days by default - which is why I think it's imprudent to try to
do urgent business by e-mail, but many of my my clients disagree and
then whine bitterly *via e-mail* when their e-mail is broken for reasons
outside of their (and our) control :).
I'd imagine you need to seek the support of your ISP helpdesk at this
point.
davidt
On Fri, May 02, 2014 at 08:07:52PM -0400, Tina Manley wrote:
All of my mail is resulting in this message:
"This is automatically generated Delivery Status Notification
THIS IS A WARNING MESSAGE ONLY.
YOU DO NOT NEED TO RESEND YOUR MESSAGE.
Delivery to the following recipient has been delayed:
images@xxxxxxxxxxxxx
Message will be retried for 2 more day(s)
Technical details of temporary failure:
Google tried to deliver your message, but it was rejected by the server for
the recipient domain comporium.net by d51502b.ess.barracudanetworks.com.
[64.235.150.197].
The error that the other server returned was:
451 No response to HELO/EHLO"