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 Murray