mirror of
https://github.com/modoboa/modoboa.git
synced 2026-04-25 00:46:03 +03:00
[GH-ISSUE #3587] ARC verification and signing for automated senders #1797
Labels
No labels
bug
bug
dependencies
design
documentation
duplicate
enhancement
enhancement
enhancement
feedback-needed
help-needed
help-needed
installer
invalid
looking-for-sponsors
modoboa-contacts
new-ui
new-ui
pr
pull-request
pyconfr
python
question
security
stale
webmail
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/modoboa-modoboa#1797
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 @almereyda on GitHub (Feb 19, 2024).
Original GitHub issue: https://github.com/modoboa/modoboa/issues/3587
Now that Modoboa has the send-only flag for email accounts, we have a facility to identify automated senders. This is useful for providing ARC signing to those identities, which are used by systems that do not bring their own ARC signing facility. This is needed to deliver messages from automated senders into Google (and possibly others).
Rspamd has a module for verification and generation of ARC signatures.
–
Therefore it appears useful to add support for the requirement that
@stale[bot] commented on GitHub (Dec 18, 2025):
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
@almereyda commented on GitHub (Dec 20, 2025):
This is still very useful for medium- to large-volume senders who use Modoboa with send-only accounts as transactional email service.
@tonioo commented on GitHub (Jan 6, 2026):
@almereyda How would you integrate that into Modoboa?
@almereyda commented on GitHub (Jan 7, 2026):
In our setup Mailman 3 handles its ARC headers. Modoboa could add its own on top of the chain, like Google do when those are present. (I need to find an example.) Mailman 3 is also a Django application, which could maybe help to inspect their implementation or even plain reuse/copy some modules.
This will also be useful to add ARC headers to transactional messages sent from clients that do not add their own, indicating themselves as automated senders.
We will maybe want to make this mandatory and implicit when activating "send-only" (transactional) mail accounts.
@kryskool commented on GitHub (Jan 8, 2026):
After check Mailman source code, they use the library authheaders
to process an ARC signing
@FlorianLaunay commented on GitHub (Jan 22, 2026):
I guess it would be better to rely on OpenARC or Rspamd ARC module like modoboa already handles DKIM signing natively with OpenDKIM or Rspamd with its
modoboa.rspamdplugin.@almereyda commented on GitHub (Jan 23, 2026):
Given usage of rspamd is considered the canonical implementation path for advanced Modoboa use cases, that sounds like a suitable implementation path for decoupling this from core.