[GH-ISSUE #3587] ARC verification and signing for automated senders #1797

Open
opened 2026-02-27 11:19:11 +03:00 by kerem · 7 comments
Owner

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

  • the Modoboa rspamd plugin has support for configuring verification and generation of ARC signatures.
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). * [Email sender guidelines - Google Workspace Admin Help](https://support.google.com/a/answer/81126) Rspamd has a module for verification and generation of ARC signatures. * [ARC module](https://rspamd.com/doc/modules/arc.html) – Therefore it appears useful to add support for the requirement that - [ ] the Modoboa rspamd plugin has support for configuring verification and generation of ARC signatures.
Author
Owner

@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.

<!-- gh-comment-id:3667645059 --> @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.
Author
Owner

@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.

<!-- gh-comment-id:3677790802 --> @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.
Author
Owner

@tonioo commented on GitHub (Jan 6, 2026):

@almereyda How would you integrate that into Modoboa?

<!-- gh-comment-id:3714571730 --> @tonioo commented on GitHub (Jan 6, 2026): @almereyda How would you integrate that into Modoboa?
Author
Owner

@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.

<!-- gh-comment-id:3718834808 --> @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.
Author
Owner

@kryskool commented on GitHub (Jan 8, 2026):

After check Mailman source code, they use the library authheaders
to process an ARC signing

<!-- gh-comment-id:3725454847 --> @kryskool commented on GitHub (Jan 8, 2026): After check Mailman source code, they use the library [authheaders](https://github.com/ValiMail/authentication-headers) to process an ARC signing
Author
Owner

@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.rspamd plugin.

<!-- gh-comment-id:3784453553 --> @FlorianLaunay commented on GitHub (Jan 22, 2026): I guess it would be better to rely on [OpenARC](https://github.com/trusteddomainproject/OpenARC) or [Rspamd ARC module](https://docs.rspamd.com/modules/arc/) like modoboa already handles DKIM signing natively with OpenDKIM or Rspamd with its `modoboa.rspamd` plugin.
Author
Owner

@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.

<!-- gh-comment-id:3790076454 --> @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.
Sign in to join this conversation.
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/modoboa-modoboa#1797
No description provided.