[GH-ISSUE #185] Unique use case with unalias email address with to:/cc: to other email addresses #743

Closed
opened 2026-03-14 10:27:28 +03:00 by kerem · 3 comments
Owner

Originally created by @cb3inco on GitHub (Aug 13, 2021).
Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/185

I have a unique use case that I'm not sure that Anonaddy could solve. Let me explain.

Our company has a domain that we've use for internal communication only. We don't want users emailing services like gmail, yahoo, etc. Say this domain is example.com.

If we allowed users to use anonaddy with a domain of our choosing, a user could email external to our email system with send/receive using domain.net. However the problem is if a user (Sam) has an email thread going on with say bob@ gmailuser.com and now wants to add jim@ example.com, this exposes jim@ example.com to bob@ gmailuser.com. Is there anyway anonaddy could strip or replace that internal domain with a address for jim while keeping the thread intact for everyone? Ideally this would be nice at a system level rule (all example.com domains are aliased).

sam@ example.com <-> AnonAddy - samo@ domain.com <-> bob@ gmailuser.com is ok.

sam@ example.com <-> Anonaddy - samo@ domain.com <-> bob@ gmailuser.com is bad.
jim@ example.com cc: jim@ example.com <-> bob@ gmailuser.com again, is bad.

I see something in issue #131 about rules...is this something that could address this? It would be also great if jim who was also a user of anonaddy could generate a alias in his account, to use a random alias from his account on this multiple recipient email.

It's rather complicated and would love to see this, but if this is not possible, then I understand. Just thought I would ask. :)

Originally created by @cb3inco on GitHub (Aug 13, 2021). Original GitHub issue: https://github.com/anonaddy/anonaddy/issues/185 I have a unique use case that I'm not sure that Anonaddy could solve. Let me explain. Our company has a domain that we've use for internal communication only. We don't want users emailing services like gmail, yahoo, etc. Say this domain is example.com. If we allowed users to use anonaddy with a domain of our choosing, a user could email external to our email system with send/receive using domain.net. However the problem is if a user (Sam) has an email thread going on with say bob@ gmailuser.com and now wants to add jim@ example.com, this exposes jim@ example.com to bob@ gmailuser.com. Is there anyway anonaddy could strip or replace that internal domain with a address for jim while keeping the thread intact for everyone? Ideally this would be nice at a system level rule (all example.com domains are aliased). sam@ example.com <-> AnonAddy - samo@ domain.com <-> bob@ gmailuser.com is ok. sam@ example.com <-> Anonaddy - samo@ domain.com <-> bob@ gmailuser.com is bad. jim@ example.com cc: jim@ example.com <-> bob@ gmailuser.com again, is bad. I see something in issue #131 about rules...is this something that could address this? It would be also great if **jim** who was also a user of anonaddy could generate a alias in his account, to use a random alias from his account on this multiple recipient email. It's rather complicated and would love to see this, but if this is not possible, then I understand. Just thought I would ask. :)
kerem closed this issue 2026-03-14 10:27:43 +03:00
Author
Owner

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

After reading that a couple of times I'm still not 100% certain what you are asking for.

sam@ example.com <-> AnonAddy - samo@ domain.com <-> bob@ gmailuser.com is ok.
sam@ example.com <-> Anonaddy - samo@ domain.com <-> bob@ gmailuser.com is bad.

These look identical to me.

<!-- gh-comment-id:907028371 --> @willbrowningme commented on GitHub (Aug 27, 2021): After reading that a couple of times I'm still not 100% certain what you are asking for. > sam@ example.com <-> AnonAddy - samo@ domain.com <-> bob@ gmailuser.com is ok. > sam@ example.com <-> Anonaddy - samo@ domain.com <-> bob@ gmailuser.com is bad. These look identical to me.
Author
Owner

@cb3inco commented on GitHub (Aug 30, 2021):

Hi @willbrowningme - sorry for the confusion on this.

Example 1:
from: sam@ example.com <-> AnonAddy - samo@ domain.com <-> to: bob@ gmailuser.com is ok.

This is the assumed normal email flow with Anonaddy in place between one person and one recipient.

Example 2:

from: sam@ example.com <-> Anonaddy - samo@ domain.com <-> to: bob@ gmailuser.com is bad.
cc: jim@ example.com.

This is a email with a cc user on example.com - his true email address is exposed to bob, which sam's email is 'masked' by AnonAddy.

I want to know if it's possible to also mask Jim's email so that when bob@ gmailuser.com replies all, both sam and jim get the response and their emails are 'masked' through Anonaddy.

Please let me know if I can further clarify this.

<!-- gh-comment-id:907987913 --> @cb3inco commented on GitHub (Aug 30, 2021): Hi @willbrowningme - sorry for the confusion on this. Example 1: ``` from: sam@ example.com <-> AnonAddy - samo@ domain.com <-> to: bob@ gmailuser.com is ok. ``` This is the assumed normal email flow with Anonaddy in place between one person and one recipient. Example 2: ``` from: sam@ example.com <-> Anonaddy - samo@ domain.com <-> to: bob@ gmailuser.com is bad. cc: jim@ example.com. ``` This is a email with a cc user on example.com - his true email address is exposed to bob, which sam's email is 'masked' by AnonAddy. I want to know if it's possible to also mask Jim's email so that when bob@ gmailuser.com replies all, both sam and jim get the response and their emails are 'masked' through Anonaddy. Please let me know if I can further clarify this.
Author
Owner

@willbrowningme commented on GitHub (Sep 6, 2021):

This seems like a duplicate of #123. At the moment CC is not supported but I will continue to investigate ways to add support for it in the situation you describe above.

<!-- gh-comment-id:913500761 --> @willbrowningme commented on GitHub (Sep 6, 2021): This seems like a duplicate of #123. At the moment CC is not supported but I will continue to investigate ways to add support for it in the situation you describe above.
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#743
No description provided.