You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It would be great if i can send mails from different alias-adresses.
As next it would be famouse if there is a alias-detection ;)
Generaly i use a catch-all configuration and use different mail-adresses for the most cases.
So if i reply it would realy helpful to write back over a alias.
Use case: mail alias for a specific supplier. Ex.: [email protected] is to deal with all my interactions with that supplier. It is an alias of [email protected]. This works fine for receiving email. But if we need to interact with them (ex.: a support ticket by email): our replies from [email protected] are not recognized. I typically create different accounts to avoid this issue. And Cypht's unified inbox is very handy to aggregate all these accounts. However, it's annoying to be forced to create accounts to deal with an external party that doesn't have proper web-based ticket system.
So @cptsanifair: I support this feature request :-)
So would this be for the "from" or "reply-to"?
What needs to happen for mail servers to accept a different "from" than currently logged in user?
In Migadu: "This is what the Migadu Wildcard Sending option is for. It grants specific mailboxes the super powers to impersonate any address on the same domain. The user however still has to authenticate with the SMTP using the mailbox credentials. Mailbox identities do not inherit this right." https://migadu.com/guides/wildcard/
🚀 Feature
It would be great if i can send mails from different alias-adresses.
As next it would be famouse if there is a alias-detection ;)
Generaly i use a catch-all configuration and use different mail-adresses for the most cases.
So if i reply it would realy helpful to write back over a alias.
As ex:
Incoming:
from [email protected]
to [email protected]
If i answer i want to write from: [email protected] to [email protected].
The text was updated successfully, but these errors were encountered: