mirror of
https://github.com/anonaddy/anonaddy.git
synced 2026-04-25 22:25:55 +03:00
[GH-ISSUE #126] Unable to add recipient with subdomain #706
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#706
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 @TomasTokaMrazek on GitHub (Feb 7, 2021).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/126
I have one domain and one subdomain. Domain DNS records (MX, DKIP, SPF) point to AnonAddy, which obviously serves as a proxy. Subdomain DNS records point to my selfhosted email server. I would like to be able to add subdomain email as a primary recipient for domain. In AnonAddy, it is currently not possible due to error "The recipient cannot use a local domain or be an alias."
I understand this limitation, it serves as a prevention to email loop, but my usecase is perfectly valid and currently works. In other words, email send to anonaddy@domain.tld goes through AnonAddy, email send to personal@mail.domain.tld goes through my email server.
Right now I am basically forced to use third-party email provider as a recipient for AnonAddy, or switch my email server to different domain. Neither solution is feasible for me, but I'll glady hear some arguments on why move email server to different domain.
I unfortunately don't have a solution from AnonAddy side. I can only think of validating MX DNS records for specified subdomain in recipient and block the request only if it points to AnonAddy email servers.
@willbrowningme commented on GitHub (Feb 8, 2021):
Hmm, thanks for bringing your scenario up. I'll have to have a think about the best way to change this to allow what you've described.
You're right that the restriction is in place as I wanted to avoid any alias -> recipient -> alias -> ... loop.
@willbrowningme commented on GitHub (Feb 19, 2021):
I've just pushed an update that fixes this.
Please try to add your subdomain again and let me know if you are still having issues.
@TomasTokaMrazek commented on GitHub (Feb 21, 2021):
Thank you, I tested it today, works as expected.