[GH-ISSUE #44] Failures when sending to/from custom domain name #650

Closed
opened 2026-03-14 09:56:26 +03:00 by kerem · 5 comments
Owner

Originally created by @combatant3 on GitHub (Apr 26, 2020).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/44

I believe I've enabled my domain name properly because most of the send/receive functionality is working with it. However, I discovered some edge cases where the emails don't seem to be sent/received.

Times where recipient does not get email:

  1. Sending from an AnonAddy alias to a domain linked to AnonAddy.
    Ex: To: alias1+alias2=aa-domain.com@user.anonaddy.com
    where "aa-domain.com" is a domain that's linked to someone's AnonAddy account.

  2. Sending from an AnonAddy alias to another AnonAddy alias.
    Ex: To: alias1+alias2=user.anonaddy.com@user.anonaddy.com
    *Note: alias2 also appears to not be auto-generated if it doesn't exist already. I'm not sure if this is the cause of the error but it's something I noticed.

--

Other than those two cases, the following seem to be working fine:
To: alias1+alias2=user.anonaddy.com@aa-domain.com
To: alias1+alias2=aa-domain.com@aa-domain.com
To: alias1+user=domain.com@aa-domain.com
To: alias1+user=domain.com@user.anonaddy.com
*Again, where domain.com is a general domain not linked to an AnonAddy account, and aa-domain.com is a domain linked to an AnonAddy account.

*Another note: I tested these circumstances a few different times, but only using one AnonAddy account instead of two separate accounts. So I was basically sending emails to myself, but with different aliases.

Originally created by @combatant3 on GitHub (Apr 26, 2020). Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/44 I believe I've enabled my domain name properly because most of the send/receive functionality is working with it. However, I discovered some edge cases where the emails don't seem to be sent/received. Times where recipient does not get email: 1. Sending from an AnonAddy alias to a domain linked to AnonAddy. Ex: To: alias1+alias2=aa-domain.com@user.anonaddy.com where "aa-domain.com" is a domain that's linked to someone's AnonAddy account. 2. Sending from an AnonAddy alias to another AnonAddy alias. Ex: To: alias1+alias2=user.anonaddy.com@user.anonaddy.com *Note: alias2 also appears to not be auto-generated if it doesn't exist already. I'm not sure if this is the cause of the error but it's something I noticed. -- Other than those two cases, the following seem to be working fine: To: alias1+alias2=user.anonaddy.com@aa-domain.com To: alias1+alias2=aa-domain.com@aa-domain.com To: alias1+user=domain.com@aa-domain.com To: alias1+user=domain.com@user.anonaddy.com *Again, where domain.com is a general domain not linked to an AnonAddy account, and aa-domain.com is a domain linked to an AnonAddy account. *Another note: I tested these circumstances a few different times, but only using one AnonAddy account instead of two separate accounts. So I was basically sending emails to myself, but with different aliases.
kerem closed this issue 2026-03-14 09:56:33 +03:00
Author
Owner

@xoengine commented on GitHub (Dec 24, 2020):

I believe we are experiencing the same issue. Just checking to see if anyone has had the opportunity to look into it?

<!-- gh-comment-id:750673633 --> @xoengine commented on GitHub (Dec 24, 2020): I believe we are experiencing the same issue. Just checking to see if anyone has had the opportunity to look into it?
Author
Owner

@willbrowningme commented on GitHub (Jan 8, 2021):

I will look into this again, it's tricky as I need to avoid any permanent forwarding loops from occurring.

<!-- gh-comment-id:756766957 --> @willbrowningme commented on GitHub (Jan 8, 2021): I will look into this again, it's tricky as I need to avoid any permanent forwarding loops from occurring.
Author
Owner

@xoengine commented on GitHub (Jan 8, 2021):

Thank you. If you come up with something let me know and we can try it.

<!-- gh-comment-id:756859555 --> @xoengine commented on GitHub (Jan 8, 2021): Thank you. If you come up with something let me know and we can try it.
Author
Owner

@willbrowningme commented on GitHub (Jan 20, 2021):

Please could you test this out again and let me know if it gives the expected behaviour now.

<!-- gh-comment-id:763438423 --> @willbrowningme commented on GitHub (Jan 20, 2021): Please could you test this out again and let me know if it gives the expected behaviour now.
Author
Owner

@willbrowningme commented on GitHub (Jan 27, 2021):

Closing for now.

<!-- gh-comment-id:768376775 --> @willbrowningme commented on GitHub (Jan 27, 2021): Closing for now.
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#650
No description provided.