[GH-ISSUE #305] Send From feature using mailer@ instead of alias #821

Closed
opened 2026-03-14 10:45:13 +03:00 by kerem · 2 comments
Owner

Originally created by @ThHareau on GitHub (Jun 20, 2022).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/305

Hey,

I'm trying to use the send from feature, however this is not working as expected.

I've sent the email using the following recipient: "alias+myemail=maindomain.tld@domain.tld".

When I connect to "myemail@maindomain.tld", I do receive the email, however it is not sent from "alias@domain.tld" but instead from "My Email mailer@anonaddy.me". When I look in the headers, I see the following:

From: My Name <mailer@anonaddy.me>
Reply-To: My Name <alias@domain.tld>

I noticed something odd in the send headers; I don't know if it is relevant:

To: alias+myemail=maindomain.tld@domain.tld <alias+myemail=maindomain.tld@domain.tld>

If needed I can provide more information, but I'd rather not publish personal information here if possible.

Originally created by @ThHareau on GitHub (Jun 20, 2022). Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/305 Hey, I'm trying to use the send from feature, however this is not working as expected. I've sent the email using the following recipient: "alias+myemail=maindomain.tld@domain.tld". When I connect to "myemail@maindomain.tld", I do receive the email, however it is not sent from "alias@domain.tld" but instead from "My Email <mailer@anonaddy.me>". When I look in the headers, I see the following: ``` From: My Name <mailer@anonaddy.me> Reply-To: My Name <alias@domain.tld> ``` I noticed something odd in the send headers; I don't know if it is relevant: ``` To: alias+myemail=maindomain.tld@domain.tld <alias+myemail=maindomain.tld@domain.tld> ``` If needed I can provide more information, but I'd rather not publish personal information here if possible.
kerem closed this issue 2026-03-14 10:45:19 +03:00
Author
Owner

@willbrowningme commented on GitHub (Jun 21, 2022):

It sounds to me like your custom domain has not been verified for sending which is why the messages have to be sent from "mailer@anonaddy.me" instead of your domain's aliases (otherwise they would fail SPF, DKIM, DMARC checks and be rejected).

Please go to the domains page and make sure you see a green check in the "Verified Records" column, if not then click "Recheck" and add the correct ones. If you are still having issues then please send me an email.

<!-- gh-comment-id:1161273071 --> @willbrowningme commented on GitHub (Jun 21, 2022): It sounds to me like your custom domain has not been verified for sending which is why the messages have to be sent from "mailer@anonaddy.me" instead of your domain's aliases (otherwise they would fail SPF, DKIM, DMARC checks and be rejected). Please go to the domains page and make sure you see a green check in the "Verified Records" column, if not then click "Recheck" and add the correct ones. If you are still having issues then please [send me an email](https://anonaddy.com/contact/).
Author
Owner

@ThHareau commented on GitHub (Aug 2, 2022):

You are correct, I had to click on recheck and it is now working as expected. Thanks a lot

<!-- gh-comment-id:1202404742 --> @ThHareau commented on GitHub (Aug 2, 2022): You are correct, I had to click on recheck and it is now working as expected. Thanks a lot
Sign in to join this conversation.
No labels
bug
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/anonaddy#821
No description provided.