rspamd
Rapid spam filtering system. (by rspamd)
postsrsd
Postfix Sender Rewriting Scheme daemon (by roehling)
Our great sponsors
| rspamd | postsrsd | |
|---|---|---|
| 1 | 3 | |
| 1,934 | 315 | |
| 1.5% | - | |
| 9.8 | 7.8 | |
| 3 days ago | 6 days ago | |
| C | C | |
| GNU General Public License v3.0 or later | GNU General Public License v3.0 only |
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rspamd
Posts with mentions or reviews of rspamd.
We have used some of these posts to build our list of alternatives
and similar projects.
-
Self hosters using RSpamd, this may be of interest to you
TL;DR: https://github.com/rspamd/rspamd/issues/4080
postsrsd
Posts with mentions or reviews of postsrsd.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-03-29.
-
Return path empty, therefore, dynamic SPF lookups based on client HELO domain?
So you're saying that the alias should work just fine? Have you checked this and this? Together with this solution? It seems it is a problem that can happen with SPF enabled. I can also reproduce the issue as I mention in the Stack Exchange post.
There are 2 suggestions in that Stack Exchange topic. One is to use BCC maps, that seems odd to me as a fix. Is that a valid approach? The other one is to use https://github.com/roehling/postsrsd, which may seem more valid. But is an extra milter really needed? Isn't this something Postfix can handle itself? I'm fishing for some more detailed advice and to validate the already given suggestions.
-
Postfix: How to set envelope-from when forwarding mail?
I use PostSRSd. This implements Sender Rewriting Scheme. The envelope-FROM is rewritten to an address on your own domain — so recipients will look at your SPF record, not the original sender's record. Bounces back to that address are forwarded back to the original sender. The address includes a cryptographically-generated tag to prevent this send-bounces-back channel from being an open relay.
What are some alternatives?
When comparing rspamd and postsrsd you can also consider the following projects:
premake-core - Premake
postforward - Postfix SRS forwarding agent
Weechat - The extensible chat client.
Exim - Exim Mail Transport Agent - source, testsuite and documentation
cyrus-sasl-xoauth2 - XOAUTH2 mechanism plugin for cyrus-sasl
vis - A vi-like editor based on Plan 9's structural regular expressions
Mailspring - :love_letter: A beautiful, fast and fully open source mail client for Mac, Windows and Linux.
Sylpheed - A mirror of the official sylpheed svn repository located at svn://sylpheed.sraoss.jp/sylpheed. The mirror does not include the branches.
neomutt - ✉️ Teaching an Old Dog New Tricks -- IRC: #neomutt on irc.libera.chat
xmake - 🔥 A cross-platform build utility based on Lua