Prev: Cannot backup Exchange VSS Error
Next: EXPROFRE errors
From: da crusher on 2 Oct 2008 11:23
Hi Rich,

I am having the same problem. Can you please elaborate on the article you
referenced? I am confused as the article states that the symptoms are that
users are receiving spam even though they shouldn't be... That is not the
issue that is mentioned at the beginning of the string.. I'm sure I'm
missing something..

Thanks in advance!!!!

"Rich Matheisen [MVP]" wrote:

> On Wed, 23 Jul 2008 14:31:26 -0500, "Matt" <mm(a)bb.com> wrote:
>
> [ snip ]
>
> >This is a delivery status notification, automatically generated by MTA
> >im2.namehub.com on Tue, 22 Jul 2008 22:41:58 -0700
> >Regarding recipient(s) : leeann(a)canadaygroup.com
> >Delivery status : Failed. Message could not be delivered to domain
> ><canadaygroup.com> .Error while sending data.
> >MTA Response :550
> >The original message headers are included as attachment.
> >
> >________________________________________
> >
> >Reporting-MTA: dns; im2.namehub.com
> >
> >Final-Recipient: rfc822;leeann(a)canadaygroup.com
> >Diagnostic-Code: smtp; 550 5.7.1 Sender ID (PRA) Not Permitted
> >Remote-MTA: dns; 64.70.67.183
> >Action: failed
> >Status: 5.0.0
> >
> >
> >Thoughts??
>
> Your SPF data uses ip4 with CIDR notation. Exchange 2003 SP3 doesn't
> like that. The error is at the receiving server, not yours.
>
> They need to install http://support.microsoft.com/kb/951639.
>
> Oh . . . so do you if you don't want to be refusing legitimate email.
> ---
> Rich Matheisen
> MCSE+I, Exchange MVP
>
 | 
Pages: 1
Prev: Cannot backup Exchange VSS Error
Next: EXPROFRE errors