mirror of
https://github.com/anonaddy/anonaddy.git
synced 2026-04-25 22:25:55 +03:00
[GH-ISSUE #611] Reply not work for outlook.de #441
Labels
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/anonaddy#441
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @philippzett on GitHub (Mar 6, 2024).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/611
Attempted Reply/Send Failed
An attempt to send or reply from your alias example@anonaddy.me was just made from example@outlook.de which failed because it didn't pass authentication checks and could be spoofed.
In order to send or reply from an alias there must be a valid DMARC policy present for outlook.de and your message must be permitted by that DMARC policy.
The attempt was trying to send the message to the following destination: example@gmail.com
These are the authentication results for the message:
mail2.anonaddy.me; dkim=none; spf=pass (mail2.anonaddy.me: domain of example@outlook.de designates 40.92.91.12 as permitted sender) smtp.mailfrom=example@outlook.de; dmarc=none; arc=pass ("microsoft.com:s=arcselector9901:i=1")
If this attempt was made by yourself, then you need to inspect the authentication results above and make sure your recipient's domain (outlook.de) has the correct DNS records in place; SPF, DKIM and DMARC.
If this attempt was not made by you, then someone else may be attempting to send a message from your alias. Make sure you have a suitable DMARC policy in place (with p=quarantine or p=reject) along with SPF and DKIM records to protect your recipient's email address from being spoofed.
@Raighar commented on GitHub (May 7, 2025):
Any info on this? I am facing the same problem.
@willbrowningme commented on GitHub (May 16, 2025):
Please send me an email and I can exclude your recipient (real email) from this requirement, but this is done at your own risk.
@KMikeeU commented on GitHub (Jan 23, 2026):
Hey, I'm having this issue on my self-hosted instance. I intercepted the email inside the docker container and the DKIM signature seems to be valid, but it's still refused. Should I open a separate issue for this, and is this even the right repo, considering the above issue is about the hosted service? @willbrowningme Thanks!