¿ªÔÆÌåÓý

550 Rejected by header based Anti-Spoofing policy


 

Hello

I have a member who have/had some e-mail problems that I'm still in the process of sorting out.

The member is currently subscribed with two e-mail addresses, say, user@... and user@.... When I visit the message history of both these accounts, I see a bounce notice (although oddly I don't see this bounce mentioned in the group's history):

For account user@...:

Recent Bounces
When Message Reason
Mar 28 [message title] 550 Rejected by header based Anti-Spoofing policy: user@... - [6lDVz9szPvqv-XYAnfANkQ.za31]

For account user@...:

Recent Bounces
When Message Reason
Mar 28 [message title] 550 Rejected by header based Anti-Spoofing policy: user@... - [Md2vVsKuMW6C1h0uPf43KA.za82]

What I find odd is that both bounce messages refer to user@.... In other words, a message that was sent to user@... triggered a bounce message that mentions user@.... (The code at the end of the message is also different, I assume it's a reference number.)

Can anyone shed some light on this?

(This member was subscribed to the Yahoogroup using both e-mail addresses, with one of them set to no-mail, and this had something to do with forwarding of mails within their company, so that the user thinks he's using e-mail address X whereas in fact his e-mails' headers say he's using e-mail address Y, or something like that.)

Thanks
Samuel


 

Samuel,


When I visit the message history
of both these accounts, I see a bounce notice (although oddly I don't
see this bounce mentioned in the group's history):

Group's history? If you mean the group's Activity Log, that records delivery failures To the group, whereas the member's Email Delivery History records delivery failures From the group.


When? ? Message Reason
Mar 28? [message title] 550 Rejected by header based Anti-Spoofing
policy: user@... -



The cited help page has information about a bypass policy that the member can set to avoid this bounce message. He/she will need to know Groups.io's sending IP address: 66.175.222.12
The other approach would be for the member to contact support and nominate his/her account as one that needs From address munging in the manner being done for users with email hosted on Microsoft (Outlook 365 or Exchange) servers.


What I find odd is that both bounce messages refer to user@....

From what you say later I'm going to guess that those both refer to the same account at that organization. Why there are two domains for it I don't know.
Sounds like one or the other of his two subscriptions should be set to No Email here as well. It would probably have been better if one had been made an Alias address of the other, but it may be too confusing to try to unwind that now.

Shal


--
Help: /static/help
More Help: /g/GroupManagersForum/wiki
Even More Help: Search button at the top of Messages list


 

On 2019/03/29 05:02 PM, Shal Farley wrote:

Samuel wrote:
When? ? Message Reason
Mar 28? [message title] 550 Rejected by header based Anti-Spoofing
policy: user@... <mailto:user@...> -
What I find odd is that both bounce messages refer to
user@... <mailto:user@...>.
From what you say later I'm going to guess that those both refer to the same account at that organization. Why there are two domains for it I don't know.
Oh, I'm aware that this sort of thing happens when a company's name changes, or if the company merges with another one, so that both entities continue to exist separately but they are also somehow one company, and allow users to retain their old addresses somehow.

Anyway, the way that this bounce message is displayed by Groups.io makes it appear as if it was the first message in the thread that bounced. The subject line is not preceded by "Re:", so I assumed that the message that bounced was the first message. But there is a link to the message, and now I clicked the link, and discovered that the message that bounced was the user's own message. In other words, she received all the other messages, but her own one bounced at her side. This explains why the e-mail addresses are the same: because she sent only one message, from user@..., and that message then bounced on her side twice.

If I understand correctly, then, we would be able to avoid these bounce messages by simply setting her account not to send her a copy of her own mails. Is there such a setting (i.e.: do not send me my own mails)?

I'm not sure if these bounces are dangerous in the long run.

Thanks
Samuel


 

Samuel M,

If I understand correctly, then, we would be able to avoid these
bounce messages by simply setting her account not to send her a copy
of her own mails. Is there such a setting (i.e.: do not send me my
own mails)?
No.

Since it is only her own posts going back to her that are bouncing it sounds like what she needs is the Gmail-style From re-writing.

That's not something that there is a user control for, Mark is trying to handle it on a domain-wide basis so that all users of such a domain get the benefit once the domain is identified.

I think that still leaves her with two options.

1) Go through her email service's procedure to set a "bypass" for that spoof blocking. That has the advantage that she'll receive her own messages with her email address intact in the From field (but that's a rather slim advantage).

2) Contact [email protected] and ask to have her accounts handled in the fashion of Gmail users: re-write the From field for one's own messages only. This has the minor disadvantage that she would see her own messages as being From: user@... but would have the likely advantage of benefiting every user of domain1 and domain2. It is also simpler for her to achieve (one email message versus whatever rigamarole).

I'm not sure if these bounces are dangerous in the long run.
Not really dangerous, but they may be inconvenient. Particularly if they are keeping her account in Bouncing status: that would block her from participation in the group until she un-bounces each time.

Shal


--
Help: /static/help
More Help: /g/GroupManagersForum/wiki
Even More Help: Search button at the top of Messages list