Re: [Mimedefang] The future of MIMEDefang
On Apr 12, 4:39pm, John Von Essen wrote: } } What will happen to www.mimedefang.org? Are you open to continue } to operate it, or transfer it to a group of volunteers who will } continue the project? This current mailing list can also be } migrated over to that domain so it doesnât die with the new } ownership. More importantly, is "MIMEDefang" trademarked? If some other person/group were to take over the open source version, would they have to change the name? } I'd hate to see MD become abandonware. Been using it since 2003. I concur, it is most likely the most flexible mail handling MILTER there is. It has been a very important part of mail handling systems that I've built over the years. It also means that I don't have to roll my own MILTERS from scratch for most things, which I have done. }-- End of excerpt from John Von Essen ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] The future of MIMEDefang
Hi, > What will happen to https://mimedefang.org/ Zix now owns that domain. You'd have to ask them what they want to do with it. > Are you open to continue to operate it, or transfer it to a group of > volunteers who will continue the project? This current mailing list > can also be migrated over to that domain so it doesn’t die with the > new ownership. I am willing to keep the site and mailing list going if nobody from Zix wants to keep it going. I did ask AppRiver what the plans were a while back, but have not had a reply. > I'd hate to see MD become abandonware… Been using it since 2003… I'd hate that also. Regards, Dianne. ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] The future of MIMEDefang
Dianne, What will happen to www.mimedefang.org? Are you open to continue to operate it, or transfer it to a group of volunteers who will continue the project? This current mailing list can also be migrated over to that domain so it doesn’t die with the new ownership. I'd hate to see MD become abandonware… Been using it since 2003… -John > On Apr 12, 2019, at 9:29 AM, Dianne Skoll wrote: > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Hi, everyone, > > As many of you probably know, I sold Roaring Penguin Software about a > year ago. The company was acquired by AppRiver, and AppRiver was > subsequently acquired by Zix. I no longer work with the company > (or indeed in the anti-spam field... I've switched over to embedded > software development.) > > As such, I don't have the time to maintain MIMEDefang. It would be a > shame for all development to stop, however, as there are still many > things that could be done to improve MIMEDefang. I'd encourage the > community to take over MIMEDefang and keep development happening. I > will of course follow developments with interest and undoubtedly voice > my opinion from time to time :) > > Regards, > > Dianne. > > -BEGIN PGP SIGNATURE- > > iQIzBAEBCAAdFiEEc45NlUBSkCwUfQeyaFpaXlEdMOIFAlywkqAACgkQaFpaXlEd > MOIJPQ/+LCY9P+S1a7QGd57d77m1q5SOJMXYxs+M5JN38a2ZOewTm3sNxuhHA9Hf > shI+yx5Mo+B39b6qZy3S4MLXmyR9ua90FdqE4REgFMEdnlZIQzi/a8YOr8RfnjCU > MjsXrCGagAg+tLmM8DyAzJRfxzFaQKnPS/XFkuhqWanbGUb/2eq4AapIgNxU5LvO > fkauKqE7EOzVXNU7vrtF+3Aindd72x0duJqbwyaMdBxsxRFB1T9mggFUFQEbIC6g > eHQ8y7Ihws4UYkiJi4dO0XhvirdOhpJbBxCga0xdjmliVomqM5DfnMukqQffLQzn > k8zVT0sh9i/dmP5xEljaw/g01vrolFB6KJtbaNEPAglMkGmopqEw3uv6ZbV/tFg/ > 5cpKe5EtcmQK1Ywjpd3wA6HeHCrgKwGqHqlnsoNSOPlhUR9LESUWbaqOjGkQHwmc > H5HS0pBS/y8wGU+FRMVegzWuubDomgB2MQMYBKHZOy3E/W3df+m9XAPHNwpVDspr > RcRTMrgpUs4rshWGQw+q2NeTvv16zM1DHT9bePSAx2zqMaIgPJOq1UpW3n4cNw3g > dZqZklRK+RR4YHgkBQ8/YuF1vv4qUM7AvgE9+2WPa0uGI5jY/2JgZTDrpqXb++Hw > 1zPZJHrYHWh7o970kYLBJDj+X3HI3eeVqZsmXbawTEDZqx32N2c= > =4y29 > -END PGP SIGNATURE- > ___ > NOTE: If there is a disclaimer or other legal boilerplate in the above > message, it is NULL AND VOID. You may ignore it. > > Visit http://www.mimedefang.org and http://www.roaringpenguin.com > MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com > http://lists.roaringpenguin.com/mailman/listinfo/mimedefang ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
[Mimedefang] The future of MIMEDefang
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hi, everyone, As many of you probably know, I sold Roaring Penguin Software about a year ago. The company was acquired by AppRiver, and AppRiver was subsequently acquired by Zix. I no longer work with the company (or indeed in the anti-spam field... I've switched over to embedded software development.) As such, I don't have the time to maintain MIMEDefang. It would be a shame for all development to stop, however, as there are still many things that could be done to improve MIMEDefang. I'd encourage the community to take over MIMEDefang and keep development happening. I will of course follow developments with interest and undoubtedly voice my opinion from time to time :) Regards, Dianne. -BEGIN PGP SIGNATURE- iQIzBAEBCAAdFiEEc45NlUBSkCwUfQeyaFpaXlEdMOIFAlywkqAACgkQaFpaXlEd MOIJPQ/+LCY9P+S1a7QGd57d77m1q5SOJMXYxs+M5JN38a2ZOewTm3sNxuhHA9Hf shI+yx5Mo+B39b6qZy3S4MLXmyR9ua90FdqE4REgFMEdnlZIQzi/a8YOr8RfnjCU MjsXrCGagAg+tLmM8DyAzJRfxzFaQKnPS/XFkuhqWanbGUb/2eq4AapIgNxU5LvO fkauKqE7EOzVXNU7vrtF+3Aindd72x0duJqbwyaMdBxsxRFB1T9mggFUFQEbIC6g eHQ8y7Ihws4UYkiJi4dO0XhvirdOhpJbBxCga0xdjmliVomqM5DfnMukqQffLQzn k8zVT0sh9i/dmP5xEljaw/g01vrolFB6KJtbaNEPAglMkGmopqEw3uv6ZbV/tFg/ 5cpKe5EtcmQK1Ywjpd3wA6HeHCrgKwGqHqlnsoNSOPlhUR9LESUWbaqOjGkQHwmc H5HS0pBS/y8wGU+FRMVegzWuubDomgB2MQMYBKHZOy3E/W3df+m9XAPHNwpVDspr RcRTMrgpUs4rshWGQw+q2NeTvv16zM1DHT9bePSAx2zqMaIgPJOq1UpW3n4cNw3g dZqZklRK+RR4YHgkBQ8/YuF1vv4qUM7AvgE9+2WPa0uGI5jY/2JgZTDrpqXb++Hw 1zPZJHrYHWh7o970kYLBJDj+X3HI3eeVqZsmXbawTEDZqx32N2c= =4y29 -END PGP SIGNATURE- ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
Re: [Mimedefang] Passing on added Header from SpamAssassin to MIMEDefang
On 12 Apr 2019, at 2:52, Benoit Panizzon wrote:
Dear List
I have started using the ASN SpamAssassin Plugin to penalize emails
originating from certain know spam operation ASN with great success
(especially for the actual sextortion email wave).
Now I reckoned it would be nice to also have the X-SPAM-ASN Header
which
is added by SpamAssassin to be passed on to MIMEDefang so it is added
to the original message, just to be able to see with one glance, from
which ASN it originated in case of spam which slips through.
I know SpamAssassin operates on a copy of the message, so it is
normally
not possible to keep headers added by SpamAssassin.
But, is there a way to still achieve this, which I am missing?
There are 2 ways:
1. Instead of using the integrated SA support in MD, run spamd and have
MD run spamc to do the scan, and replace the message entirely with what
spamc returns. This has a performance penalty, but you get any of SA's
header modifications that you want.
2. Build it yourself in mimedefang-filter, in filter_end(). This is how
I do a similar thing on my personal system:
* WARNING: This is a raw snippet that has not been cleaned
*
** up for general distribution or drop-in use
*
# NOTE: MUST be done before spam_assassin_check finishes the
object
my $SAStatus = spam_assassin_status();
# Get Relay countries and ASNs and languages
$relaycountry = $SAStatus->get_tag("RELAYCOUNTRY");
$relayasn = $SAStatus->get_tag("ASN");
$relayasncidr = $SAStatus->get_tag("ASNCIDR");
$languages= $SAStatus->get_tag("LANGUAGES");
#BEWARE: spam_assassin_check calls status->finish()
my ($hits, $req, $names, $report) = spam_assassin_check();
# Consistent with proposed patch for SA bug #6473 2018-02-04
my $relayhops = '';
my $lastcc= '';
if (length($relaycountry)) {
my @rcs = split(' ', $relaycountry);
while (my $cc = pop(@rcs)) {
if (length($lastcc)) { $relayhops = $cc . $lastcc . " " .
$relayhops; }
$lastcc = $cc;
}
$relayhops = "Trusted_" . $lastcc . " " . $relayhops;
}
my ($score);
if ($hits < 20) {
$score = "*" x int($hits);
} else {
$score = "*" x 20;
}
md_graphdefang_log('spam', $hits, $MessageID, $RelayAddr);
md_syslog('info', "SA: $hits ($score) $names");
md_syslog('info', "SOURCE: from $relayasncidr on $relayasn via
$relaycountry ($relayhops) in $languages");
# Delete any existing X-Spam-* headers
action_delete_header("X-Spam-Status");
action_delete_header("X-Spam-Score");
action_delete_header("X-Spam-Source");
action_delete_header("X-Spam-Hops");
action_add_header("X-Spam-Score", "$hits ($score) $names");
action_add_header("X-Spam-Source", "$relayasncidr on $relayasn
via $relaycountry in $languages");
action_add_header("X-Spam-Hops", "$relayhops");
Refer to the MD and/or SA docs to clarify anything in that which is
non-obvious...
--
Bill Cole
b...@scconsult.com or billc...@apache.org
(AKA @grumpybozo and many *@billmail.scconsult.com addresses)
Available For Hire: https://linkedin.com/in/billcole
___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID. You may ignore it.
Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
[Mimedefang] Passing on added Header from SpamAssassin to MIMEDefang
Dear List I have started using the ASN SpamAssassin Plugin to penalize emails originating from certain know spam operation ASN with great success (especially for the actual sextortion email wave). Now I reckoned it would be nice to also have the X-SPAM-ASN Header which is added by SpamAssassin to be passed on to MIMEDefang so it is added to the original message, just to be able to see with one glance, from which ASN it originated in case of spam which slips through. I know SpamAssassin operates on a copy of the message, so it is normally not possible to keep headers added by SpamAssassin. But, is there a way to still achieve this, which I am missing? Mit freundlichen Grüssen -Benoît Panizzon- -- I m p r o W a r e A G-Leiter Commerce Kunden __ Zurlindenstrasse 29 Tel +41 61 826 93 00 CH-4133 PrattelnFax +41 61 826 93 01 Schweiz Web http://www.imp.ch __ ___ NOTE: If there is a disclaimer or other legal boilerplate in the above message, it is NULL AND VOID. You may ignore it. Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com http://lists.roaringpenguin.com/mailman/listinfo/mimedefang
