Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for forwarding via SMTP (with SRS due SPF) #6

Closed
hz61p1 opened this issue Mar 21, 2020 · 4 comments
Closed

Add support for forwarding via SMTP (with SRS due SPF) #6

hz61p1 opened this issue Mar 21, 2020 · 4 comments
Assignees
Labels

Comments

@hz61p1
Copy link

hz61p1 commented Mar 21, 2020

No description provided.

@albertito
Copy link
Owner

Hi!

Can you elaborate on this?

chasquid already supports forwarding with SRS. If you alias to a non-local domain, then SMTP forwarding with SRS will be used.

@hz61p1
Copy link
Author

hz61p1 commented Mar 21, 2020

Thanks for the details. The documentation does not explicitly indicate which mechanism is used for this.

@albertito
Copy link
Owner

I see! I can fix that, thanks for pointing it out.

I'll leave this open to track the documentation improvement.

@albertito albertito assigned albertito and unassigned hz61p1 Mar 21, 2020
albertito added a commit that referenced this issue Mar 21, 2020
When an alias has a remote destination, chasquid uses sender rewriting
(also known as SRS [1]) to forward the email without risking being in
violation of SPF policies.

See https://en.wikipedia.org/wiki/Sender_Rewriting_Scheme for more
details.

This, however, wasn't documented anywhere, as noted in
#6.

This patch adds a paragraph to the alias documentation explaining this
behaviour.
@albertito
Copy link
Owner

Commit 65afb02 adds a paragraph about this in the aliases documentation.

Thanks for the report, and please let me know if you have any suggestion or comment to improve it!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants