team/site
team
/
site
7
17
Fork 56
Code Issues 2 Pull Requests 1 Releases Wiki Activity

Implement SRS to improve deliverability of forwarded messages #138

New Issue
Open
opened 2024-04-14 10:13:41 +00:00 by alexlehm · 0 comments
alexlehm commented 2024-04-14 10:13:41 +00:00
Copy Link

I'd like to propose an addition, however I am not sure if it is worth the effort since it applies only to very few users of the site.

The email forwarding function using the .forward file currently simply forwards the emails keeping the MAIL FROM header without change which means that some sites that enforce SPF very strictly will bounce emails that are forwarded from domains that have SPF -all and some spam filters will reject or defer forwarded emails when they do not fit the DKIM signature and SPF, since the MAIL FROM address does not match the tilde domains and the SPF does not match either.

The common solution for this is to rewrite the MAIL FROM value to a forwarding address that uses a encoded address and then a subdomain like srs.example.com that is forwarded the other way when bounce emails are received for a short while (like 10 days or so)

I currently have no actual use-case to use the feature, so I am not really testing it, but it looks like the mails from one or two users get caught

I'd like to propose an addition, however I am not sure if it is worth the effort since it applies only to very few users of the site. The email forwarding function using the .forward file currently simply forwards the emails keeping the MAIL FROM header without change which means that some sites that enforce SPF very strictly will bounce emails that are forwarded from domains that have SPF -all and some spam filters will reject or defer forwarded emails when they do not fit the DKIM signature and SPF, since the MAIL FROM address does not match the tilde domains and the SPF does not match either. The common solution for this is to rewrite the MAIL FROM value to a forwarding address that uses a encoded address and then a subdomain like srs.example.com that is forwarded the other way when bounce emails are received for a short while (like 10 days or so) I currently have no actual use-case to use the feature, so I am not really testing it, but it looks like the mails from one or two users get caught
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
master
Labels
Clear labels
No items
No Label
Milestone
Clear milestone
No items
No Milestone
Assignees
Clear assignees
No Assignees
1 Participants
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: team/site#138
No description provided.
Delete Branch "%!s(<nil>)"

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?