From n.kilner at kilner-vacuum-lifting.com Wed Oct 13 14:27:11 2021 From: n.kilner at kilner-vacuum-lifting.com (Nigel Kilner) Date: Wed, 13 Oct 2021 15:27:11 +0100 Subject: MailScanner doesn't Disarm or change Subject or message body Message-ID: <7e657e22-2861-0523-d730-2428a67276e4@kilner-vacuum-lifting.com> Hello, I have MailScanner 5.3.3 with Postfix & Clamav but mailscanner does not? 'disarm' emails with web bugs or 'sign messages' or 'add signatures'. Messages do contain mailscanner header info e.g spam scores, virus scan info. mailscanner --lint shows no issues and there are no errors in logs. I have an external message rule to mark messages from outside our network. mail logs show " /Message is external, prepending warning for/ .." but the email body is not marked. I have checked mailscanner.conf for locations of rules, reports and signatures but can find no mistakes.? My config worked on previous server but after migrating and installing MS on the new server the problems started. The only issue I had with installation was with Mail::Clamav which will not build on my box ( inline-C error) however clamav works and signs message on detection. I've been going around in circles to find the cause but I am stumped. How best to troubleshoot this? Thank you Nigel Kilner -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawniverson at summitgrid.com Wed Oct 13 15:01:57 2021 From: shawniverson at summitgrid.com (Shawn Iverson) Date: Wed, 13 Oct 2021 11:01:57 -0400 Subject: MailScanner doesn't Disarm or change Subject or message body In-Reply-To: <7e657e22-2861-0523-d730-2428a67276e4@kilner-vacuum-lifting.com> References: <7e657e22-2861-0523-d730-2428a67276e4@kilner-vacuum-lifting.com> Message-ID: <5f242b63-8d63-3310-bef6-fb0d0123cf36@summitgrid.com> If the logs are indicating that something is happening with message alteration, but the message isn't getting altered, one of the first things I would check for is that the working directories for MailScanner are writable for the MailScanner user context. On 10/13/21 10:27 AM, Nigel Kilner wrote: > Hello, > > I have MailScanner 5.3.3 with Postfix & Clamav but mailscanner does > not? 'disarm' emails with web bugs or 'sign messages' or 'add signatures'. > > Messages do contain mailscanner header info e.g spam scores, virus > scan info. > > mailscanner --lint shows no issues and there are no errors in logs. > > I have an external message rule to mark messages from outside our > network. mail logs show " /Message is external, prepending warning > for/ .." but the email body is not marked. > > I have checked mailscanner.conf for locations of rules, reports and > signatures but can find no mistakes.? My config worked on previous > server but after migrating and installing MS on the new server the > problems started. The only issue I had with installation was with > Mail::Clamav which will not build on my box ( inline-C error) however > clamav works and signs message on detection. > > I've been going around in circles to find the cause but I am stumped. > How best to troubleshoot this? > > Thank you > > Nigel Kilner > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mailinglists at feedmebits.nl Sat Oct 23 17:18:48 2021 From: mailinglists at feedmebits.nl (Maarten) Date: Sat, 23 Oct 2021 19:18:48 +0200 Subject: MSMilter and spf Message-ID: It's been a a few years since msmilter was first implemented in mailscanner. I had been using the traditional since I started using mailscanner. I had some time on my hands and I thought I would try the msmilter configuration also because I haven't seen any recent issues in the list come along so I thought that is a good sign. It was easy to setup because the documentation is well done and my mail is received as expected. So first of all I would like to say thank you to those who implemented the milter option. However I am running in one small thing which isn't working correctly and that has been since I went from traditional to milter configuration. Before the switch to the milter configuration postfix would add a line like this to the headers: Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=204.92.22.85; helo=mail03.engage.redhat.com; envelope-from=noreply at engage.redhat.com; receiver= Since I made the switch to milter that is not happening anymore, any idea why that is happening? Maarten From shawniverson at summitgrid.com Sat Oct 23 17:49:25 2021 From: shawniverson at summitgrid.com (Shawn Iverson) Date: Sat, 23 Oct 2021 13:49:25 -0400 Subject: MSMilter and spf In-Reply-To: References: Message-ID: <2d38e20a-742d-76e0-17ff-449483894dca@summitgrid.com> Typically, this is implemented in postfix with something like postfix-policyd. Do you still have this or something similar? On 10/23/21 1:18 PM, Maarten via MailScanner wrote: > It's been a a few years since msmilter was first implemented in > mailscanner. I had been using the > traditional since I started using mailscanner. I had some time on my > hands and I thought I would > try the msmilter configuration also because I haven't seen any recent > issues in the list come along > so I thought that is a good sign. It was easy to setup because the > documentation is well done and > my mail is received as expected. So first of all I would like to say > thank you to those who implemented > the milter option. However I am running in one small thing which isn't > working correctly and that > has been since I went from traditional to milter configuration. > > Before the switch to the milter configuration postfix would add a line > like this to the headers: > > Received-SPF: Pass (mailfrom) identity=mailfrom; > client-ip=204.92.22.85; helo=mail03.engage.redhat.com; > envelope-from=noreply at engage.redhat.com; receiver= > > Since I made the switch to milter that is not happening anymore, any > idea why that is happening? > > Maarten > > > From mailinglists at feedmebits.nl Sat Oct 23 20:16:41 2021 From: mailinglists at feedmebits.nl (Maarten) Date: Sat, 23 Oct 2021 22:16:41 +0200 Subject: MSMilter and spf In-Reply-To: <2d38e20a-742d-76e0-17ff-449483894dca@summitgrid.com> References: <2d38e20a-742d-76e0-17ff-449483894dca@summitgrid.com> Message-ID: <622e5588-aea8-32c4-2cda-22028dc43852@feedmebits.nl> Thanks for your reply Shawn. It seems to be working now, I think I missed something. I restored my old configuration to verify it and then I ran into some other issues which didn't have anything to do with mailscanner or postfix which I fixed. After my old configuration was restored and working again, I tested it and my spf and dkim were working there. So I went? through the milter configuration? again and It seems to be working now, both my dkim and spf.? Even though I have a backup mailserver I was sweating a little because I didn't know where it went wrong since I followed the mailscanner guide. I think I may have overlooked something while doing it and reacted by changing something elsewhich caused some other issues. I'll leave it running for a day or so and see what happens. From all my testing I have done so far it's all good. See the last test mail I sent from a gmail account: Return-Path: X-Original-To: gmail at example.com Delivered-To: mailinglists at example.com Received: from magik (localhost [127.0.0.1]) ?? ?by magik.example.com (Postfix) with ESMTP id DD3AFE0ABB ?? ?for ; Sat, 23 Oct 2021 22:11:27 +0200 (CEST) DKIM-Filter: OpenDKIM Filter v2.11.0 magik.example.com DD3AFE0ABB Authentication-Results: magik.example.com; ?? ?dkim=pass (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.a=rsa-sha256 header.s=20210112 header.b=e7od2eYB X-Spam-Status: No X-FMB-MailScanner-From: example at gmail.com X-FMB-MailScanner: Found to be clean X-FMB-MailScanner-ID: D8845E0AB8.AA5CD X-FMB-MailScanner-Information: Please contact hostmaster at example.com for more information Received: from mail-ed1-f54.google.com (mail-ed1-f54.google.com [209.85.208.54]) ?? ?(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) ?? ?(no client certificate requested) ?? ?by magik (MailScanner Milter) with SMTP id D8845E0AB8 ?? ?for ; Sat, 23 Oct 2021 22:11:22 +0200 (CEST) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.208.54; helo=mail-ed1-f54.google.com; envelope-from=example at gmail.com; receiver= DKIM-Filter: OpenDKIM Filter v2.11.0 magik.example.com D8845E0AB8 Received: by mail-ed1-f54.google.com with SMTP id w15so306888edc.9 ??????? for ; Sat, 23 Oct 2021 13:11:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; ??????? d=gmail.com; s=20210112; ??????? h=mime-version:from:date:message-id:subject:to; ??????? bh=5siPEmJlMA6PG5q+Ww7Th7cXsTfPnNnJzHDNbY+kXbA=; b=e7od2eYBMzIj7F4ZGmRX3EYuVqE6zxRXaWjQEkZ9oOGViT+paDRn8YlyOh1n3i8UIA 43w4VEG8COdC44M9S2XhgowQb3RCAt8Jp7YmR9JuzExlC/1B7UDTO5smEWzyZWWkbcWE g4FXqC7kwRe/OR8AELB9ok76spHKOnhTELcYNPLeFLQiMqXXhWgp08nKPflWY6IgxQlJ p6x+OpUsTuet+6kRnG5YBLYMIcxmUBl3uj2ygqF6ygOjnvCdVqfwTzvag0lCi3Ny3See RGfc9X+kVeOPiWWUTdXfirGOa+BOM8jtHDN1y6zs1LPM6pBJd6XWn/geM6CmiY4GM+6s ???????? E8Bg== Thanks for your reply! Have a great day! On 10/23/21 19:49, Shawn Iverson via MailScanner wrote: > Typically, this is implemented in postfix with something like > postfix-policyd. Do you still have this or something similar? > > On 10/23/21 1:18 PM, Maarten via MailScanner wrote: >> It's been a a few years since msmilter was first implemented in >> mailscanner. I had been using the >> traditional since I started using mailscanner. I had some time on my >> hands and I thought I would >> try the msmilter configuration also because I haven't seen any recent >> issues in the list come along >> so I thought that is a good sign. It was easy to setup because the >> documentation is well done and >> my mail is received as expected. So first of all I would like to say >> thank you to those who implemented >> the milter option. However I am running in one small thing which >> isn't working correctly and that >> has been since I went from traditional to milter configuration. >> >> Before the switch to the milter configuration postfix would add a >> line like this to the headers: >> >> Received-SPF: Pass (mailfrom) identity=mailfrom; >> client-ip=204.92.22.85; helo=mail03.engage.redhat.com; >> envelope-from=noreply at engage.redhat.com; receiver= >> >> Since I made the switch to milter that is not happening anymore, any >> idea why that is happening? >> >> Maarten >> >> >> > > From mailinglists at feedmebits.nl Sun Oct 24 11:25:43 2021 From: mailinglists at feedmebits.nl (Maarten) Date: Sun, 24 Oct 2021 13:25:43 +0200 Subject: MSMilter and spf In-Reply-To: <622e5588-aea8-32c4-2cda-22028dc43852@feedmebits.nl> References: <2d38e20a-742d-76e0-17ff-449483894dca@summitgrid.com> <622e5588-aea8-32c4-2cda-22028dc43852@feedmebits.nl> Message-ID: Just one question which milter protocol version does msmilter need? http://www.postfix.org/postconf.5.html#milter_protocol http://www.postfix.org/MILTER_README.html Or will the default version suffice? /etc/postfix/main.cf : # Postfix ? 2.6 milter_protocol = 6 # 2.3 ? Postfix ? 2.5 milter_protocol = 2 On 10/23/21 22:16, Maarten via MailScanner wrote: > Thanks for your reply Shawn. It seems to be working now, I think I > missed something. I restored my old configuration > to verify it and then I ran into some other issues which didn't have > anything to do with mailscanner or postfix which I > fixed. After my old configuration was restored and working again, I > tested it and my spf and dkim were working there. > So I went? through the milter configuration? again and It seems to be > working now, both my dkim and spf.? Even though > I have a backup mailserver I was sweating a little because I didn't > know where it went wrong since I followed the > mailscanner guide. I think I may have overlooked something while doing > it and reacted by changing something elsewhich > caused some other issues. I'll leave it running for a day or so and > see what happens. From all my testing I have done so > far it's all good. > > See the last test mail I sent from a gmail account: > > Return-Path: > X-Original-To: gmail at example.com > Delivered-To: mailinglists at example.com > Received: from magik (localhost [127.0.0.1]) > ?? ?by magik.example.com (Postfix) with ESMTP id DD3AFE0ABB > ?? ?for ; Sat, 23 Oct 2021 22:11:27 +0200 (CEST) > DKIM-Filter: OpenDKIM Filter v2.11.0 magik.example.com DD3AFE0ABB > Authentication-Results: magik.example.com; > ?? ?dkim=pass (2048-bit key; unprotected) header.d=gmail.com > header.i=@gmail.com header.a=rsa-sha256 header.s=20210112 > header.b=e7od2eYB > X-Spam-Status: No > X-FMB-MailScanner-From: example at gmail.com > X-FMB-MailScanner: Found to be clean > X-FMB-MailScanner-ID: D8845E0AB8.AA5CD > X-FMB-MailScanner-Information: Please contact hostmaster at example.com > for more information > Received: from mail-ed1-f54.google.com (mail-ed1-f54.google.com > [209.85.208.54]) > ?? ?(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)) > ?? ?(no client certificate requested) > ?? ?by magik (MailScanner Milter) with SMTP id D8845E0AB8 > ?? ?for ; Sat, 23 Oct 2021 22:11:22 +0200 (CEST) > Received-SPF: Pass (mailfrom) identity=mailfrom; > client-ip=209.85.208.54; helo=mail-ed1-f54.google.com; > envelope-from=example at gmail.com; receiver= > DKIM-Filter: OpenDKIM Filter v2.11.0 magik.example.com D8845E0AB8 > Received: by mail-ed1-f54.google.com with SMTP id w15so306888edc.9 > ??????? for ; Sat, 23 Oct 2021 13:11:22 -0700 (PDT) > DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; > ??????? d=gmail.com; s=20210112; > ??????? h=mime-version:from:date:message-id:subject:to; > ??????? bh=5siPEmJlMA6PG5q+Ww7Th7cXsTfPnNnJzHDNbY+kXbA=; > b=e7od2eYBMzIj7F4ZGmRX3EYuVqE6zxRXaWjQEkZ9oOGViT+paDRn8YlyOh1n3i8UIA > 43w4VEG8COdC44M9S2XhgowQb3RCAt8Jp7YmR9JuzExlC/1B7UDTO5smEWzyZWWkbcWE > g4FXqC7kwRe/OR8AELB9ok76spHKOnhTELcYNPLeFLQiMqXXhWgp08nKPflWY6IgxQlJ > p6x+OpUsTuet+6kRnG5YBLYMIcxmUBl3uj2ygqF6ygOjnvCdVqfwTzvag0lCi3Ny3See > RGfc9X+kVeOPiWWUTdXfirGOa+BOM8jtHDN1y6zs1LPM6pBJd6XWn/geM6CmiY4GM+6s > ???????? E8Bg== > > > Thanks for your reply! Have a great day! > > On 10/23/21 19:49, Shawn Iverson via MailScanner wrote: >> Typically, this is implemented in postfix with something like >> postfix-policyd. Do you still have this or something similar? >> >> On 10/23/21 1:18 PM, Maarten via MailScanner wrote: >>> It's been a a few years since msmilter was first implemented in >>> mailscanner. I had been using the >>> traditional since I started using mailscanner. I had some time on my >>> hands and I thought I would >>> try the msmilter configuration also because I haven't seen any >>> recent issues in the list come along >>> so I thought that is a good sign. It was easy to setup because the >>> documentation is well done and >>> my mail is received as expected. So first of all I would like to say >>> thank you to those who implemented >>> the milter option. However I am running in one small thing which >>> isn't working correctly and that >>> has been since I went from traditional to milter configuration. >>> >>> Before the switch to the milter configuration postfix would add a >>> line like this to the headers: >>> >>> Received-SPF: Pass (mailfrom) identity=mailfrom; >>> client-ip=204.92.22.85; helo=mail03.engage.redhat.com; >>> envelope-from=noreply at engage.redhat.com; receiver= >>> >>> Since I made the switch to milter that is not happening anymore, any >>> idea why that is happening? >>> >>> Maarten >>> >>> >>> >> >> > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mailinglists at feedmebits.nl Sun Oct 24 11:27:01 2021 From: mailinglists at feedmebits.nl (Maarten) Date: Sun, 24 Oct 2021 13:27:01 +0200 Subject: MSMilter and spf In-Reply-To: References: <2d38e20a-742d-76e0-17ff-449483894dca@summitgrid.com> <622e5588-aea8-32c4-2cda-22028dc43852@feedmebits.nl> Message-ID: Mesed up with the font color: Just one question which milter protocol version does msmilter need? http://www.postfix.org/postconf.5.html#milter_protocol http://www.postfix.org/MILTER_README.html Or will the default version suffice? /etc/postfix/main.cf : # Postfix ? 2.6 milter_protocol = 6 # 2.3 ? Postfix ? 2.5 milter_protocol = 2 On 10/24/21 13:25, Maarten via MailScanner wrote: > Just one question which milter protocol version does msmilter need? > > http://www.postfix.org/postconf.5.html#milter_protocol > http://www.postfix.org/MILTER_README.html > > Or will the default version suffice? > /etc/postfix/main.cf : > # Postfix ? 2.6 > milter_protocol > = 6 > # 2.3 ? Postfix ? 2.5 > milter_protocol > = 2 -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawniverson at summitgrid.com Sun Oct 24 18:44:18 2021 From: shawniverson at summitgrid.com (Shawn Iverson) Date: Sun, 24 Oct 2021 14:44:18 -0400 Subject: MSMilter and spf In-Reply-To: References: <2d38e20a-742d-76e0-17ff-449483894dca@summitgrid.com> <622e5588-aea8-32c4-2cda-22028dc43852@feedmebits.nl> Message-ID: Default (version 6) is what it has been built and tested on. On 10/24/21 7:27 AM, Maarten via MailScanner wrote: > Mesed up with the font color: > > Just one question which milter protocol version does msmilter need? > > http://www.postfix.org/postconf.5.html#milter_protocol > http://www.postfix.org/MILTER_README.html > > Or will the default version suffice? > /etc/postfix/main.cf : > # Postfix ? 2.6 > milter_protocol > = 6 > # 2.3 ? Postfix ? 2.5 > milter_protocol > = 2 > > On 10/24/21 13:25, Maarten via MailScanner wrote: >> Just one question which milter protocol version does msmilter need? >> >> http://www.postfix.org/postconf.5.html#milter_protocol >> http://www.postfix.org/MILTER_README.html >> >> Or will the default version suffice? >> /etc/postfix/main.cf : >> # Postfix ? 2.6 >> milter_protocol >> = 6 >> # 2.3 ? Postfix ? 2.5 >> milter_protocol >> = 2 > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mailinglists at feedmebits.nl Sun Oct 24 18:57:02 2021 From: mailinglists at feedmebits.nl (Maarten) Date: Sun, 24 Oct 2021 20:57:02 +0200 Subject: MSMilter and spf In-Reply-To: References: <2d38e20a-742d-76e0-17ff-449483894dca@summitgrid.com> <622e5588-aea8-32c4-2cda-22028dc43852@feedmebits.nl> Message-ID: <48a94b66-2675-011b-6e46-a264f0076cb0@feedmebits.nl> Thanks! I was using 2 and it was working but since I found out the default version of the Postfix version I am running is 6 I switched over to 6 since MailScanner is tested with that version but both worked. I have been running the msmilter for a day now and working great! Only thing I ran into was selinux which I fixed by adding to my custom policy. Thank you so much Shawn for creating the msmilter! :) On 10/24/21 20:44, Shawn Iverson via MailScanner wrote: > > Default (version 6) is what it has been built and tested on. > > On 10/24/21 7:27 AM, Maarten via MailScanner wrote: >> Mesed up with the font color: >> >> Just one question which milter protocol version does msmilter need? >> >> http://www.postfix.org/postconf.5.html#milter_protocol >> http://www.postfix.org/MILTER_README.html >> >> Or will the default version suffice? >> /etc/postfix/main.cf : >> # Postfix ? 2.6 >> milter_protocol >> = 6 >> # 2.3 ? Postfix ? 2.5 >> milter_protocol >> = 2 >> >> On 10/24/21 13:25, Maarten via MailScanner wrote: >>> Just one question which milter protocol version does msmilter need? >>> >>> http://www.postfix.org/postconf.5.html#milter_protocol >>> http://www.postfix.org/MILTER_README.html >>> >>> Or will the default version suffice? >>> /etc/postfix/main.cf : >>> # Postfix ? 2.6 >>> milter_protocol >>> = 6 >>> # 2.3 ? Postfix ? 2.5 >>> milter_protocol >>> = 2 >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From shawniverson at summitgrid.com Sun Oct 24 19:57:53 2021 From: shawniverson at summitgrid.com (Shawn Iverson) Date: Sun, 24 Oct 2021 15:57:53 -0400 Subject: MSMilter and spf In-Reply-To: <48a94b66-2675-011b-6e46-a264f0076cb0@feedmebits.nl> References: <2d38e20a-742d-76e0-17ff-449483894dca@summitgrid.com> <622e5588-aea8-32c4-2cda-22028dc43852@feedmebits.nl> <48a94b66-2675-011b-6e46-a264f0076cb0@feedmebits.nl> Message-ID: You are welcome. I did this so that mailscanner would have a compliant way of interacting with postfix. Sadly, postfix.org, despite the enhancement, still has mailscanner discouraged. I told Weitze about the new feature, even. :( Development continues...I plan to hopefully add ithread support to the milter, which will be a more modern cpu handling compared to traditional prefork or postfork methods. On 10/24/21 2:57 PM, Maarten via MailScanner wrote: > Thanks! I was using 2 and it was working but since I found out the > default version > of the Postfix version I am running is 6 I switched over to 6 since > MailScanner is > tested with that version but both worked. I have been running the > msmilter for a > day now and working great! Only thing I ran into was selinux which I > fixed by adding to my custom policy. Thank you so much Shawn for creating > the msmilter! :) > > On 10/24/21 20:44, Shawn Iverson via MailScanner wrote: >> >> Default (version 6) is what it has been built and tested on. >> >> On 10/24/21 7:27 AM, Maarten via MailScanner wrote: >>> Mesed up with the font color: >>> >>> Just one question which milter protocol version does msmilter need? >>> >>> http://www.postfix.org/postconf.5.html#milter_protocol >>> http://www.postfix.org/MILTER_README.html >>> >>> Or will the default version suffice? >>> /etc/postfix/main.cf : >>> # Postfix ? 2.6 >>> milter_protocol >>> = 6 >>> # 2.3 ? Postfix ? 2.5 >>> milter_protocol >>> = 2 >>> >>> On 10/24/21 13:25, Maarten via MailScanner wrote: >>>> Just one question which milter protocol version does msmilter need? >>>> >>>> http://www.postfix.org/postconf.5.html#milter_protocol >>>> http://www.postfix.org/MILTER_README.html >>>> >>>> Or will the default version suffice? >>>> /etc/postfix/main.cf : >>>> # Postfix ? 2.6 >>>> milter_protocol >>>> = 6 >>>> # 2.3 ? Postfix ? 2.5 >>>> milter_protocol >>>> = 2 >>> >>> >> > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From mailinglists at feedmebits.nl Sun Oct 24 20:34:57 2021 From: mailinglists at feedmebits.nl (Maarten) Date: Sun, 24 Oct 2021 22:34:57 +0200 Subject: MSMilter and spf In-Reply-To: References: <2d38e20a-742d-76e0-17ff-449483894dca@summitgrid.com> <622e5588-aea8-32c4-2cda-22028dc43852@feedmebits.nl> <48a94b66-2675-011b-6e46-a264f0076cb0@feedmebits.nl> Message-ID: <92211f3a-0255-3370-b565-dc9e4f5265d3@feedmebits.nl> When setting up my mailserver a few years ago I did have a look at amavis-new because it is officially supported by Postfix on the Postfix add-on page. But I ended up going with Mailscanner because I found it easier to configure and I haven't regretted it since even though I have been using the traditional way since I did my first mailserver build a few years ago.? It's just nice being able to use a milter now knowing that it's an officially supported way because of it being a milter even though I never missed any mail the traditional way. I will be continuing to use the msmilter(and mailscanner) and hopefully postfix.org will come to their senses soon and change that? entry on their page because it can't be for nothing that so many people are using mailscanner :) I was even using mailscanner at my work for the mailrouters the traditional way until someone higher up decided to replace it all with Office 365 :( I will keep running it on my vps hosting my personal mail, so I am looking forward to the development of MailScanner and MSmilter! Does the Mailscanner development team need any donations, because I can donate at a later time. Just know I am representing one person and not a company :) Maarten Maarten On 10/24/21 21:57, Shawn Iverson via MailScanner wrote: > > You are welcome. I did this so that mailscanner would have a compliant > way of interacting with postfix. Sadly, postfix.org, despite the > enhancement, still has mailscanner discouraged. I told Weitze about > the new feature, even. :( > > Development continues...I plan to hopefully add ithread support to the > milter, which will be a more modern cpu handling compared to > traditional prefork or postfork methods. > > On 10/24/21 2:57 PM, Maarten via MailScanner wrote: >> Thanks! I was using 2 and it was working but since I found out the >> default version >> of the Postfix version I am running is 6 I switched over to 6 since >> MailScanner is >> tested with that version but both worked. I have been running the >> msmilter for a >> day now and working great! Only thing I ran into was selinux which I >> fixed by adding to my custom policy. Thank you so much Shawn for >> creating >> the msmilter! :) >> >> On 10/24/21 20:44, Shawn Iverson via MailScanner wrote: >>> >>> Default (version 6) is what it has been built and tested on. >>> >>> On 10/24/21 7:27 AM, Maarten via MailScanner wrote: >>>> Mesed up with the font color: >>>> >>>> Just one question which milter protocol version does msmilter need? >>>> >>>> http://www.postfix.org/postconf.5.html#milter_protocol >>>> http://www.postfix.org/MILTER_README.html >>>> >>>> Or will the default version suffice? >>>> /etc/postfix/main.cf : >>>> # Postfix ? 2.6 >>>> milter_protocol >>>> = 6 >>>> # 2.3 ? Postfix ? 2.5 >>>> milter_protocol >>>> = 2 >>>> >>>> On 10/24/21 13:25, Maarten via MailScanner wrote: >>>>> Just one question which milter protocol version does msmilter need? >>>>> >>>>> http://www.postfix.org/postconf.5.html#milter_protocol >>>>> http://www.postfix.org/MILTER_README.html >>>>> >>>>> Or will the default version suffice? >>>>> /etc/postfix/main.cf : >>>>> # Postfix ? 2.6 >>>>> milter_protocol >>>>> = 6 >>>>> # 2.3 ? Postfix ? 2.5 >>>>> milter_protocol >>>>> = 2 >>>> >>>> >>> >> >> > > -------------- next part -------------- An HTML attachment was scrubbed... URL: