-
-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unable to reply back to forwarded email #169
Comments
The problem might be that you are not running Rspamd, as it is Rspamd that adds the Without that header you will get the message as above, since your recipient must explicitly pass DMARC checks in order to be able to send/reply from aliases. Please try adding Rspamd and see if that resolves it. |
I do have Rspamd enabled and running but I'm also getting the same (bounce) mail and not able to reply. |
Oh wow. That look me days trying to get that working. And in the end it was a completely unrelated setting. |
Btw, permanent link to the code line you mentioned is: You can easily press Y on a code page to get a link including the commit hash, and as such always pointing to the relevant section, even years later. |
Hello, running Anonaddy 0.13.5 armv7 alpine docker image using docker-compose. dkim configured. Not running rspamd or GPG. Other than my custom domain name, pretty much every other environment variable is default. Emails forward properly, but replies fail with below anonaddy generated email error (from gmail in this instance). Have tried multiple different email providers.
An attempt to send or reply from your alias [] was just made from [] which failed because it didn't pass authentication checks and could be a spoofed.
In order to send or reply from an alias there must be a valid DMARC policy present for gmail.com and your message must be permitted by that DMARC policy.
The attempt was trying to send the message to the following destination: []
If this attempt was made by yourself, then you need to make sure your recipient's domain (gmail.com) 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.
The text was updated successfully, but these errors were encountered: