Re: [Mimedefang] action_drop_with_warning with recipient depending message

You have to understand that MIMEDefang is operating on one message. It may have multiple recipients, but anything you do happens to that message. If you want different per-recipient behavior for the same message, somewhere along the line you need to resend the message. You can do this up-front

[Mimedefang] action_drop_with_warning with recipient depending message

Hi, depending on the recipient I'd like to drop with different warning messages using action_drop_with_warning e.g. when a virus is found. As I understand action_drop_with_warning, it drops with the same message at one go for each recipient in case of multiple recipients, so calling

Re: [Mimedefang] resending mails from quarantine, modify Message-ID or use Resent-Headers?

On Wed, Jan 4, 2017 at 2:25 PM, Marcus Schopen wrote: > I will set a new Message-ID too then. Do remove the old Message-ID > header or do you change it to X-Orig-Message-ID to keep it? > > And do you set Resent-Date, Resent-From, Resent-To, Resent-Message-ID > headers too? My

Re: [Mimedefang] resending mails from quarantine, modify Message-ID or use Resent-Headers?

Am Dienstag, den 03.01.2017, 19:58 +0100 schrieb Peter Bonivart: > On Tue, Jan 3, 2017 at 7:19 PM, Marcus Schopen wrote: > > Hi, > > > > I'm playing around with resending quarantined emails, if the user wants > > them to be delivered and check locally. I set Resent-Headers in

Re: [Mimedefang] resending mails from quarantine, modify Message-ID or use Resent-Headers?

On Tue, Jan 3, 2017 at 7:19 PM, Marcus Schopen wrote: > Hi, > > I'm playing around with resending quarantined emails, if the user wants > them to be delivered and check locally. I set Resent-Headers in those > resent messages, so that cyrus delivers and doesn't drop them as >

[Mimedefang] resending mails from quarantine, modify Message-ID or use Resent-Headers?

Hi, I'm playing around with resending quarantined emails, if the user wants them to be delivered and check locally. I set Resent-Headers in those resent messages, so that cyrus delivers and doesn't drop them as duplicates. Some users users pop their mailboxes with exchange or popcon. Any

Re: [Mimedefang] calling external shell script without waiting for its end

Hi Dianne, Thanks for your time. Am Montag, den 02.01.2017, 15:45 -0500 schrieb Dianne Skoll: > On Mon, 02 Jan 2017 19:26:44 +0100 > Marcus Schopen wrote: > > > When calling an external bash script in filter_end like > > > system("/usr/local/bin/skript.sh $QueueID >

Re: [Mimedefang] calling external shell script without waiting for its end

On Mon, 02 Jan 2017 19:26:44 +0100 Marcus Schopen wrote: > When calling an external bash script in filter_end like > system("/usr/local/bin/skript.sh $QueueID > /dev/null &"); I hope you trust the contents of $QueueID implicitly... The MIMEDefang working directory gets

[Mimedefang] calling external shell script without waiting for its end

Hi, happy new year to all! :) When calling an external bash script in filter_end like system("/usr/local/bin/skript.sh $QueueID > /dev/null &"); I get the following error from time to time (mostly on receiving many simultaneously mails): Jan 2 18:38:13 serv mimedefang-multiplexor[7447]:

Re: [Mimedefang] Block internal messages

On 12/26/2016 9:38 PM, Richard Laager wrote: On 12/26/2016 03:35 PM, Marcelo Machado wrote: I am new to Mimedefang and I would like to know if it is possible to block internal messages, (from my domain to my domain) if the number of recipients is greater than 10. Anything is possible if you

Re: [Mimedefang] Block internal messages

On 12/26/2016 03:35 PM, Marcelo Machado wrote: > I am new to Mimedefang and I would like to know if it is possible to > block internal messages, (from my domain to my domain) if the number > of recipients is greater than 10. Anything is possible if you write the custom Perl code required. What

[Mimedefang] Block internal messages

Hi everyone. I am new to Mimedefang and I would like to know if it is possible to block internal messages, (from my domain to my domain) if the number of recipients is greater than 10. Marcelo Gomes ___ NOTE: If there is a disclaimer or other legal

Re: [Mimedefang] add_header all RelaysUntrusted _RELAYSUNTRUSTED_

You call SpamAssassin like this in your filter: ($hits, $threshold, $names, $report) = spam_assassin_check(); The "names" variable lists all of the rules in SA which were triggered, so you can apply some logic based on this: if ( $names =~ /RELAYSUNTRUSTED/ ) { # add header to

Re: [Mimedefang] add_header all RelaysUntrusted _RELAYSUNTRUSTED_

Hi Dianne, thanks for your time. Am Mittwoch, den 14.12.2016, 09:42 -0500 schrieb Dianne Skoll: > On Wed, 14 Dec 2016 12:54:38 +0100 > Marcus Schopen wrote: > > > > I'd like to set a "add_header all RelaysUntrusted > > > _RELAYSUNTRUSTED_" to my headers, to see in case of

Re: [Mimedefang] add_header all RelaysUntrusted _RELAYSUNTRUSTED_

On Wed, 14 Dec 2016 12:54:38 +0100 Marcus Schopen wrote: > > I'd like to set a "add_header all RelaysUntrusted > > _RELAYSUNTRUSTED_" to my headers, to see in case of IPs in > > trusted_networks on which IPs dnsrbl and dnswl checks run on. But > > putting this to

Re: [Mimedefang] add_header all RelaysUntrusted _RELAYSUNTRUSTED_

Am Montag, den 12.12.2016, 23:30 +0100 schrieb Marcus Schopen: > Hi, > > I'd like to set a "add_header all RelaysUntrusted _RELAYSUNTRUSTED_" to > my headers, to see in case of IPs in trusted_networks on which IPs > dnsrbl and dnswl checks run on. But putting this to sa-mimedefang.cf has > no

Re: [Mimedefang] add_header all RelaysUntrusted _RELAYSUNTRUSTED_

On 12/12/2016 5:57 PM, Marcus Schopen wrote: Hmmm ... I did a reread and after your email a stop/start, but the header doesn't come up. I always forget that we have SA glued into MD in an odd way. If you are using something like the default example windows filter, you have a call in your

Re: [Mimedefang] add_header all RelaysUntrusted _RELAYSUNTRUSTED_

Am Montag, den 12.12.2016, 17:46 -0500 schrieb Kevin A. McGrail: > On 12/12/2016 5:30 PM, Marcus Schopen wrote: > > I'd like to set a "add_header all RelaysUntrusted _RELAYSUNTRUSTED_" to > > my headers, to see in case of IPs in trusted_networks on which IPs > > dnsrbl and dnswl checks run on. But

Re: [Mimedefang] add_header all RelaysUntrusted _RELAYSUNTRUSTED_

On 12/12/2016 5:30 PM, Marcus Schopen wrote: I'd like to set a "add_header all RelaysUntrusted _RELAYSUNTRUSTED_" to my headers, to see in case of IPs in trusted_networks on which IPs dnsrbl and dnswl checks run on. But putting this to sa-mimedefang.cf has no effect. My first thought is if you

Re: [Mimedefang] DZIP Extension

On Mon, 12 Dec 2016 12:38:06 -0500 "Kevin A. McGrail" wrote: > Seeing some fake invoice/in the wild garbage with .dzip extension > getting through today. > If you are doing some extension blocking, etc. might want to take a > look. Yes, we're seeing those too... they're

[Mimedefang] DZIP Extension

Seeing some fake invoice/in the wild garbage with .dzip extension getting through today. If you are doing some extension blocking, etc. might want to take a look. Regards, KAM ___ NOTE: If there is a disclaimer or other legal boilerplate in the above

Re: [Mimedefang] Sender Address Verification

On 11/23/2016 12:22 PM, Richard Laager wrote: > On 11/22/2016 12:55 PM, Bill Cole wrote: >> the SAV rule was never decisive in a correct SA 'spam' determination > > Thanks for sharing. This is good information. > > I've made a note to re-evaluate my SAV rules after the holiday. I have > some

Re: [Mimedefang] Mimedefang-Problem

Hi Sauraj > I have been using mimedefang for long time with sendmail as the MTA > but when I try to change the MTA to postfix and use mimedefang it > seems to be not working. Could you please help me with this. We use MIMEDefang with Postfix. Could you please be a bit more specific about the

Re: [Mimedefang] Mimedefang-Problem

Hi Sauraj, Am Mittwoch, den 07.12.2016, 16:38 +0545 schrieb sauraj: > Dear all, > > I have been using mimedefang for long time with sendmail as the MTA but when > I try to change the MTA to postfix and use mimedefang it seems to be not > working. Could you please help me with this. Hmmm, hard

[Mimedefang] Mimedefang-Problem

Dear all, I have been using mimedefang for long time with sendmail as the MTA but when I try to change the MTA to postfix and use mimedefang it seems to be not working. Could you please help me with this. Thanks, Sauraj ___ NOTE: If there is a

Re: [Mimedefang] Connecting Clamd via inet socket?

Benoit Panizzon wrote: > Hi all > > Does anyone know, if it's possible to use > > ClamdSock = "host:port"; > > in MIMEDefang? > > I found very old posts stating, that clamd can only scan local files, > thus has to be called on the machine the file resides. > > Is still this the case, or can

Re: [Mimedefang] Connecting Clamd via inet socket?

Hi all Thank you for the comments. I wrote that email a bit in a hurry, because we have an 'old' installation which uses MIMEDefang where we cannot update clamd (and the OS base) anymore. Clamd keeps crashing with new definition files. So as a quick fix I got clamd on our new filter installation

Re: [Mimedefang] Connecting Clamd via inet socket?

On Dec 2, 1:22pm, "Bill Cole" wrote: } On 2 Dec 2016, at 12:01, Dianne Skoll wrote: } > On Fri, 2 Dec 2016 16:57:32 +0100 } > Benoit Panizzon wrote: } > } >> Does anyone know, if it's possible to use } >> ClamdSock = "host:port"; } >> in MIMEDefang? } > } > No; the

Re: [Mimedefang] Connecting Clamd via inet socket?

That's the great thing about mimedefang. Very little you can't add. I've got some clamp code that streams to another host. Don't remember how I did it. Can you implement code if I dig it up? Regards, KAM On December 2, 2016 12:01:59 PM EST, Dianne Skoll wrote: >On

Re: [Mimedefang] Connecting Clamd via inet socket?

Hi all > Better just to modify the Perl wrappers to use IO::Socket::INET and > use the stream-scanning clamd protocol. We extended the ClamAV::Client (CPAN) also handle zINSTREAM protocol, it has worked fine for some years now. example "code" send("zINSTREAM\0") while (read block

Re: [Mimedefang] Connecting Clamd via inet socket?

On 2 Dec 2016, at 12:28, Marcus Schopen wrote: Hi Benoît, Am Freitag, den 02.12.2016, 16:57 +0100 schrieb Benoit Panizzon: Hi all Does anyone know, if it's possible to use ClamdSock = "host:port"; in MIMEDefang? I found very old posts stating, that clamd can only scan local files, thus

Re: [Mimedefang] Connecting Clamd via inet socket?

On Fri, 02 Dec 2016 13:22:09 -0500 "Bill Cole" wrote: > socat UNIX-LISTEN:/var/run/fakeclamd.sock,mode=777,fork > TCP:: That won't work because the MIMEDefang code uses SCAN, which gets passed a local filename. Better just to modify the Perl wrappers to

Re: [Mimedefang] Connecting Clamd via inet socket?

On 2 Dec 2016, at 12:01, Dianne Skoll wrote: On Fri, 2 Dec 2016 16:57:32 +0100 Benoit Panizzon wrote: Does anyone know, if it's possible to use ClamdSock = "host:port"; in MIMEDefang? No; the built-in code uses IO::Socket::UNIX and can only scan local files. You

Re: [Mimedefang] Connecting Clamd via inet socket?

Hi Benoît, Am Freitag, den 02.12.2016, 16:57 +0100 schrieb Benoit Panizzon: > Hi all > > Does anyone know, if it's possible to use > > ClamdSock = "host:port"; > > in MIMEDefang? > > I found very old posts stating, that clamd can only scan local files, > thus has to be called on the machine

Re: [Mimedefang] Connecting Clamd via inet socket?

On Fri, 2 Dec 2016 16:57:32 +0100 Benoit Panizzon wrote: > Does anyone know, if it's possible to use > ClamdSock = "host:port"; > in MIMEDefang? No; the built-in code uses IO::Socket::UNIX and can only scan local files. You need to write your own wrapper code if you

[Mimedefang] Connecting Clamd via inet socket?

Hi all Does anyone know, if it's possible to use ClamdSock = "host:port"; in MIMEDefang? I found very old posts stating, that clamd can only scan local files, thus has to be called on the machine the file resides. Is still this the case, or can the content to be scanned streamed via inet

Re: [Mimedefang] Sender Address Verification

On 11/22/2016 12:55 PM, Bill Cole wrote: > the SAV rule was never decisive in a correct SA 'spam' determination Thanks for sharing. This is good information. I've made a note to re-evaluate my SAV rules after the holiday. I have some test harnesses to determine whether an individual rule "made a

Re: [Mimedefang] Sender Address Verification

On 19 Nov 2016, at 7:01, Simon Standley wrote: Guys, In conversations on this list in days gone by, I seem to recall sender address verification via the likes of smf-sav milter, or through mimedefang, was considered evil heresy, likely to get you blacklisted. Yes. For good reason. If you

Re: [Mimedefang] Sender Address Verification

We have been doing sender address verification for years. Looking through the code... We use custom MIMEDefang code around DNS::Resolver and md_check_against_smtp_server(). We wrap the md check in a block and use alarm() to timeout, as MD's timeout doesn't always work (e.g. if the server is

Re: [Mimedefang] newbie prerequisite install questions

> On 21 Nov 2016, at 13:04, Michael Fox wrote: [details clipped] > Yes. *ALL* of those are Distribution names, which is why they don't use > the :: module delimiter. You should be able to get them all using CPAN. Thanks Bill. That's exactly what I needed. Michael

[Mimedefang] Sender Address Verification

Guys, In conversations on this list in days gone by, I seem to recall sender address verification via the likes of smf-sav milter, or through mimedefang, was considered evil heresy, likely to get you blacklisted. Recently though, I've seen an increasing number of recipients do this kind of

Re: [Mimedefang] newbie prerequisite install questions

On 21 Nov 2016, at 13:04, Michael Fox wrote: Thanks Mickey. That doesn't appear to be a "module", but rather an archive of multiple modules, right? (I'm new to CPAN, too). MailTools is a Distribution: a collection of related modules maintained as one project because they are

Re: [Mimedefang] newbie prerequisite install questions

Thanks Mickey. That doesn't appear to be a "module", but rather an archive of multiple modules, right? (I'm new to CPAN, too). So, is the instruction to download, unpack and install this archive, using sudo? And, for my other question, should I install the other modules listed on the Download

Re: [Mimedefang] newbie prerequisite install questions

On Nov 21, 2016, at 9:16 AM, Michael Fox wrote: > Then “MailTools-1” links to http://search.cpan.org/search?q=MailTools, which > has 28 pages of modules, none of which seem to be named “MailTools” or > “Mail::Tools”. I just don’t know what I’m supposed to do there. Please >

[Mimedefang] newbie prerequisite install questions

I’m new to MIMEdefang and could use some more specific instructions on installation.  Sorry for the many nit questions.  But I want to start off right and I’m just not finding clear installation instructions. I read http://www.mimedefang.org/static/mimedefang-lisa04.pdf, slide 30, and it says

Re: [Mimedefang] Multiple MIMEDefang instances (was Re: strip down mimedefang-filter to sub filter_recipient for md_check_against_smtp_server checks)

Hi Dianne, Am Dienstag, den 11.10.2016, 13:10 -0400 schrieb Dianne Skoll: > On Tue, 11 Oct 2016 18:07:42 +0200 > Marcus Schopen wrote: > > > I run milter-greylist and I don't want to run messages into > > greylisting before I checked if recipients are valid (fills up > >

Re: [Mimedefang] Multiple MIMEDefang instances (was Re: strip down mimedefang-filter to sub filter_recipient for md_check_against_smtp_server checks)

On Tue, 11 Oct 2016 18:07:42 +0200 Marcus Schopen wrote: > I run milter-greylist and I don't want to run messages into > greylisting before I checked if recipients are valid (fills up > greylisting database with non existing recipients). You can do greylisting from within

Re: [Mimedefang] Multiple MIMEDefang instances (was Re: strip down mimedefang-filter to sub filter_recipient for md_check_against_smtp_server checks)

Hi Dianne, Am Dienstag, den 11.10.2016, 10:50 -0400 schrieb Dianne Skoll: > Hi, > > While in principle, you can run multiple MIMEDefang instances, I really > don't see the point. MIMEDefang lets you write your policy in Perl, > so I cannot see a use case that requires more than one instance of

[Mimedefang] Multiple MIMEDefang instances (was Re: strip down mimedefang-filter to sub filter_recipient for md_check_against_smtp_server checks)

Hi, While in principle, you can run multiple MIMEDefang instances, I really don't see the point. MIMEDefang lets you write your policy in Perl, so I cannot see a use case that requires more than one instance of MIMEDefang. Regards, Dianne. ___ NOTE:

Re: [Mimedefang] strip down mimedefang-filter to sub filter_recipient for md_check_against_smtp_server checks

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Mon, 10 Oct 2016, Marcus Schopen wrote: Am Freitag, den 07.10.2016, 14:49 +0200 schrieb Marcus Schopen: I'd like to start a second mimedefang instance, which is called before milter-greylist. This mimedefang should only check if recipients on

Re: [Mimedefang] strip down mimedefang-filter to sub filter_recipient for md_check_against_smtp_server checks

Hi, Am Freitag, den 07.10.2016, 14:49 +0200 schrieb Marcus Schopen: > Hi, > > I'd like to start a second mimedefang instance, which is called before > milter-greylist. This mimedefang should only check if recipients on > internal hosts exist, so incoming emails for non existing recipients >

[Mimedefang] strip down mimedefang-filter to sub filter_recipient for md_check_against_smtp_server checks

Hi, I'd like to start a second mimedefang instance, which is called before milter-greylist. This mimedefang should only check if recipients on internal hosts exist, so incoming emails for non existing recipients don't run into milter-greylist. I striped down the mimedefang-filter example to

Re: [Mimedefang] check header for X- entry

Am Mittwoch, den 05.10.2016, 20:22 +0200 schrieb Marcus Schopen: > Am Mittwoch, den 05.10.2016, 20:02 +0200 schrieb Marcus Schopen: > > Hi, > > > > I'd like to check the header for "X-Greylist" entry in filter_end and if > > it exists with an expected contend write a message to maillog > >

Re: [Mimedefang] check header for X- entry

Am Mittwoch, den 05.10.2016, 20:02 +0200 schrieb Marcus Schopen: > Hi, > > I'd like to check the header for "X-Greylist" entry in filter_end and if > it exists with an expected contend write a message to maillog > (md_graphdefang_log). But I can't find a function for parsing headers. > Do I have

[Mimedefang] check header for X- entry

Hi, I'd like to check the header for "X-Greylist" entry in filter_end and if it exists with an expected contend write a message to maillog (md_graphdefang_log). But I can't find a function for parsing headers. Do I have to parse the entire message? Ciao Marcus

Re: [Mimedefang] SA autolearn, missing bayes_journal file

Ah, got it. bayes_journal is just a temp file before synchronized into the databases. The server where I see it, is very low volume, so it takes some time until bayes_journal_max_size is reached. I thought it's a mimedefang permission problem. ___

[Mimedefang] SA autolearn, missing bayes_journal file

Hi, I'm wondering about missing bayes_journal file using mimedefang 2.78 and Spamassassin 3.4.1. On another instance with (what I see) same configuration this file is created. Because upgrading from a SA version < 3.4.0 I wiped its database "sa-learn -dbpath /var/spool/MIMEDefang/.spamassassin

Re: [Mimedefang] MIMEDefang 2.79 is released

On Wed, 28 Sep 2016 19:54:56 -0400 "Bill Cole" wrote: > The shebang line in script/mimedefang-util is hardcoded with > /usr/bin/perl rather than having a .in file with @PERL@. D'oh, I guess I should fix that... Regards, Dianne.

Re: [Mimedefang] MIMEDefang 2.79 is released

On 26 Sep 2016, at 10:14, Dianne Skoll wrote: Hello, MIMEDefang 2.79 is available at http://mimedefang.org/download Indeed, and of course updating to a new release is when bugs are discovered. The shebang line in script/mimedefang-util is hardcoded with /usr/bin/perl rather than having a

Re: [Mimedefang] MIMEDefang 2.79 is released

Thanks :) Med venlig hilsen Thomas Kristensen Storhaven 12 - 7100 Vejle Tlf: 75 72 54 99 - Fax: 75 72 65 33 E-mail: t...@multimed.dk -Oprindelig meddelelse- Fra: MIMEDefang [mailto:mimedefang-boun...@lists.roaringpenguin.com] På vegne af Marcus Schopen Sendt: 27. september 2016 13:59

Re: [Mimedefang] MIMEDefang 2.79 is released

Hi Thomas, Am Montag, den 26.09.2016, 17:32 + schrieb Thomas Kristensen: > Hey > > Any ETA on the ubuntu apt release? Or isnt it you that are releasing to those > repos? I built an upstream release for Ubuntu. You can download binary and source package here:

Re: [Mimedefang] MIMEDefang 2.79 is released

Okay thanks :) Med venlig hilsen Thomas Kristensen Storhaven 12 - 7100 Vejle Tlf: 75 72 54 99 - Fax: 75 72 65 33 E-mail: t...@multimed.dk -Oprindelig meddelelse- Fra: MIMEDefang [mailto:mimedefang-boun...@lists.roaringpenguin.com] På vegne af Dianne Skoll Sendt: 26. september 2016

Re: [Mimedefang] MIMEDefang 2.79 is released

On Mon, 26 Sep 2016 17:32:25 + Thomas Kristensen wrote: > Any ETA on the ubuntu apt release? I don't have any connection with that... I'm just upstream for all the distros. Regards, Dianne. ___ NOTE: If there is a disclaimer or

Re: [Mimedefang] MIMEDefang 2.79 is released

Hey Any ETA on the ubuntu apt release? Or isnt it you that are releasing to those repos? Med venlig hilsen Thomas Kristensen Storhaven 12 - 7100 Vejle Tlf: 75 72 54 99 - Fax: 75 72 65 33 E-mail: t...@multimed.dk -Oprindelig meddelelse- Fra: MIMEDefang

[Mimedefang] MIMEDefang 2.79 is released

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hello, MIMEDefang 2.79 is available at http://mimedefang.org/download Release notes follow. Regards, Dianne. 2016-09-26 Dianne Skoll * MIMEDefang 2.79 RELEASED * Add the --data-dump option to

Re: [Mimedefang] $QueueId not allways defined

On Mon, 26 Sep 2016 05:59:59 + Thomas Kristensen wrote: > How do i apply the patch? I need to apply it to the source and then > compile a my self, right? Yes. I will probably release 2.79 soon, with the patch. Regards, Dianne.

Re: [Mimedefang] $QueueId not allways defined

How do i apply the patch? I need to apply it to the source and then compile a my self, right? Med venlig hilsen Thomas Kristensen Storhaven 12 - 7100 Vejle Tlf: 75 72 54 99 - Fax: 75 72 65 33 E-mail: t...@multimed.dk -Oprindelig meddelelse- Fra: MIMEDefang

Re: [Mimedefang] $QueueId not allways defined

On Sat, 24 Sep 2016 17:20:16 + Thomas Kristensen wrote: > But it still doesnt work. I still got the NOQUEUE in filter_begin. Right, you need to apply the patch. Regards, Dianne. ___ NOTE: If there is a disclaimer or other legal

Re: [Mimedefang] Domain canonifyin​g and RFCs

Marcus Schopen wrote: P.S. I know the setting confDONT_EXPAND_CNAMES will disable this behaviour, but I would prefer not to implement this. Also I cannot modify the DNS records since it is an external DNS server. They insist their DNS settings are RFC compliant. Their

Re: [Mimedefang] Domain canonifyin​g and RFCs

Am Donnerstag, den 13.10.2011, 10:57 +0200 schrieb Ernst du Plooy: > I posted the following on the sendmail (comp.mail.sendmail) newsgroup, > but I don't get any reaction. I realise this is not a mimedefang > problem, but I'm sure some of you have also run into this issue. > > RFC 821 section

Re: [Mimedefang] $QueueId not allways defined

Thanks for that. I have updated my postfix configuration with the setting. I use only filter_begin, so i should be good with the mimedefang version i got, however i cant seem to find a version number on mimedefang. But it still doesnt work. I still got the NOQUEUE in filter_begin. Med venlig

Re: [Mimedefang] conditionally add boilerplate in message with more than one recipient

> From: "Richard Laager" >> OK, got it. However, I want all the filtering stuff in the filter*() >> functions to be applied to the "resent" message to ORG, except the >> boilerplate. I guess it's not >> possible because resend_message resends the ORIGINAL message and won't

Re: [Mimedefang] $QueueId not allways defined

On Fri, 23 Sep 2016 22:49:39 -0400 "Bill Cole" wrote: > So if you're not running MD 2.78 plus the patch available at > http://lists.roaringpenguin.com/pipermail/mimedefang/2015-April/037618.html Ooh... I really should release 2.79. I have a few patches

Re: [Mimedefang] $QueueId not allways defined

On Fri, 23 Sep 2016 21:51:19 + Thomas Kristensen wrote: > I just installed postfix and mimedefang, and i works pretty nice. > But in some cases that $QueueId is not defined, only as NOQUEUE. Sendmail picks a Queue ID as soon as the MAIL From: SMTP command is received.

Re: [Mimedefang] $QueueId not allways defined

On 23 Sep 2016, at 17:58, Thomas Kristensen wrote: Hallo I just installed postfix and mimedefang, and i works pretty nice. But in some cases that $QueueId is not defined, only as NOQUEUE. I cant see why this is only happing to some of the mails and not all. I tend to be some a certin host,

[Mimedefang] $QueueId not allways defined

Hallo I just installed postfix and mimedefang, and i works pretty nice. But in some cases that $QueueId is not defined, only as NOQUEUE. I cant see why this is only happing to some of the mails and not all. I tend to be some a certin host, but on sometimes the variable is fine, even from the

[Mimedefang] $QueueId not allways defined

Hallo I just installed postfix and mimedefang, and i works pretty nice. But in some cases that $QueueId is not defined, only as NOQUEUE. I cant see why this is only happing to some of the mails and not all. I tend to be some a certin host, but on sometimes the variable is fine, even from the

Re: [Mimedefang] conditionally add boilerplate in message with more than one recipient

On 09/22/2016 11:54 AM, Vieri Di Paola wrote: >> From: "Richard Laager" >>> It's a typo, I presume? In my example, u...@domain.com wants the >>> boilerplate and u...@domain.org doesn't. So I guess you meant "resend to >>> u...@domain.com, >>>

Re: [Mimedefang] conditionally add boilerplate in message with more than one recipient

On 09/21/2016 05:13 PM, Vieri Di Paola wrote: >> From: "Richard Laager" >> So in your case, you would resent to u...@domain.org, >> delete_recipient(u...@domain.org), and then add the boilerplate. > > It's a typo, I presume? In my example, u...@domain.com wants the

Re: [Mimedefang] conditionally add boilerplate in message with more than one recipient

> From: "Richard Laager" > So in your case, you would resent to u...@domain.org, > delete_recipient(u...@domain.org), and then add the boilerplate. It's a typo, I presume? In my example, u...@domain.com wants the boilerplate and u...@domain.org doesn't. So I guess you meant

Re: [Mimedefang] conditionally add boilerplate in message with more than one recipient

On 09/21/2016 09:09 AM, Vieri Di Paola wrote: >> You can stream_by_recipient() so MIMEDefang resends the message for each >> recipient. In this way, your filter code can handle recipients >> differently. Note the warnings in the mimedefang-filter man page, though. > > The man page isn't too

Re: [Mimedefang] conditionally add boilerplate in message with more than one recipient

On 09/21/2016 07:16 AM, Vieri Di Paola wrote: > Suppose I have an email that's being sent To: u...@domain.org, > u...@domain.com. > > @Recipients will hold both addresses. > I'd like mimedefang to add a boilerplate only for the message being sent to > u...@domain.com. > > Is that possible? >

[Mimedefang] mimedefang mailing list page

I noticed that Norton Safe Web (DNS) blocks access to mimedefang's mailing list page and throws this warning: Threat Name: W97M.Downloader Location: https://antispam.roaringpenguin.com/canit/s.php?s=jballard%40hendersoncountync.org=hendersoncountync-org=09RCo3dkr=16bd6564=1=1.2

[Mimedefang] conditionally add boilerplate in message with more than one recipient

Hi, Suppose I have an email that's being sent To: u...@domain.org, u...@domain.com. @Recipients will hold both addresses. I'd like mimedefang to add a boilerplate only for the message being sent to u...@domain.com. Is that possible? If so, how? I can only add boilerplates in filter_end but

Re: [Mimedefang] %2C instead of whitspaces in sendmail log

--On September 20, 2016 at 17:24:44 +0200 Marcus Schopen wrote: > > when I try to log the spam score names to sendmail log using > > md_graphdefang_log('spam_full_report', $hits, $names, $RelayAddr); > > all whitespaces are replaced by "%2C" e.g.: > >

Re: [Mimedefang] %2C instead of whitspaces in sendmail log

--On September 20, 2016 at 11:48:17 -0400 Joseph Brennan wrote: > The function takes only 3 arguments. Try > > md_graphdefang_log('spam_full_report',"$hits $names", $RelayAddr); Oh! I forgot that just before this we do: $names =~ s/,/ /g; to change the commas to

Re: [Mimedefang] filter_bad_filename based on recipient

Am Montag, den 19.09.2016, 08:57 -0400 schrieb Dianne Skoll: > On Mon, 19 Sep 2016 14:48:16 +0200 > Marcus Schopen wrote: > > > is it possible to define $bad_exts in sub filter_bad_filename based on > > domain name? I'd like to filter ".docm"-attachments, but not globally > >

Re: [Mimedefang] filter_bad_filename based on recipient

Hi > is it possible to define $bad_exts in sub filter_bad_filename based on > domain name? I'd like to filter ".docm"-attachments, but not globally > for all domains on that server, just for my private domain. Seems to > be that $recipient is not known in sub filter_bad_filename? Sure it is. You

Re: [Mimedefang] filter_bad_filename based on recipient

On Mon, 19 Sep 2016 14:48:16 +0200 Marcus Schopen wrote: > is it possible to define $bad_exts in sub filter_bad_filename based on > domain name? I'd like to filter ".docm"-attachments, but not globally > for all domains on that server, just for my private domain. Seems to >

Re: [Mimedefang] clamav-unofficial-sigs and pyzor

Am Montag, den 19.09.2016, 08:36 -0400 schrieb Dianne Skoll: > On Mon, 19 Sep 2016 07:46:11 +0200 > Marcus Schopen wrote: > > > my be a little bit off topic, but are there any experience with the > > efficiency of pyzor and clamav-unofficial-sigs [1]. > > No comment on pyzor

Re: [Mimedefang] clamav-unofficial-sigs and pyzor

On 09/19/2016 01:48 AM, Marcus Schopen wrote: > Did you activate all signatures > or just e.g. sanesecurity sigs? I read activating all signatures turns > clamav into an evil memory monster, while only activating sanesecurity > sigs catches most and doesn't need that much resources. I don't

Re: [Mimedefang] clamav-unofficial-sigs and pyzor

Hi Richard, Am Montag, den 19.09.2016, 01:23 -0500 schrieb Richard Laager: > On 09/19/2016 12:46 AM, Marcus Schopen wrote: > > my be a little bit off topic, but are there any experience with the > > efficiency of pyzor and clamav-unofficial-sigs > > We use clamav-unofficial-sigs. If clamd

Re: [Mimedefang] clamav-unofficial-sigs and pyzor

On 09/19/2016 12:46 AM, Marcus Schopen wrote: > my be a little bit off topic, but are there any experience with the > efficiency of pyzor and clamav-unofficial-sigs We use clamav-unofficial-sigs. If clamd triggers, it's a hard fail for us, regardless of whether it was a virus or spam rule. We do

[Mimedefang] clamav-unofficial-sigs and pyzor

Hi, my be a little bit off topic, but are there any experience with the efficiency of pyzor and clamav-unofficial-sigs [1]. I used pyzor years ago and didn't follow it since then. And a lot of locky mails passed my filter, therefore I tought clamav-unofficial-sigs with turning on sanesecurity

Re: [Mimedefang] reread mimedefang after sa-update

Hi Richard, Am Donnerstag, den 15.09.2016, 00:48 -0500 schrieb Richard Laager: [...] > So configure.in has a check for this pthread flag, but does not use > $PTHREAD_FLAG as part of the $CFLAGS for the SAFE_EMBED_PERL test. Patch > attached, which results in SAFE_EMBED_PERL set and reread working

Re: [Mimedefang] reread mimedefang after sa-update

Hi Richard, Am Donnerstag, den 15.09.2016, 00:48 -0500 schrieb Richard Laager: [...] > > I'm digging into it right now. The problem seems to be that Perl outputs > > -lpthread as a required LDFLAG, but gcc needs -pthread (with no "l"), or > > else it fails linking to the symbol

Re: [Mimedefang] reread mimedefang after sa-update

On Thu, 15 Sep 2016 00:48:01 -0500 Richard Laager wrote: > So configure.in has a check for this pthread flag, but does not use > $PTHREAD_FLAG as part of the $CFLAGS for the SAFE_EMBED_PERL test. > Patch attached, which results in SAFE_EMBED_PERL set and reread > working for

Re: [Mimedefang] reread mimedefang after sa-update

On 09/14/2016 11:12 AM, Marcus Schopen wrote: > Am Mittwoch, den 14.09.2016, 11:51 -0400 schrieb Dianne Skoll: >> On Wed, 14 Sep 2016 17:46:07 +0200 >> Marcus Schopen wrote: >> >>> Sep 14 17:39:55 scansrv mimedefang-multiplexor[24029]: Cannot destroy >>> and recreate a Perl

Re: [Mimedefang] reread mimedefang after sa-update

On Wed, 14 Sep 2016 20:39:19 +0200 Marcus Schopen wrote: > Hmmm, what's the performance loss if not using embedded Perl? There is some, but it's mostly related to startup costs. Once things are running, there's not a huge difference. Unless you're running a busy machine

Re: [Mimedefang] reread mimedefang after sa-update

Am Mittwoch, den 14.09.2016, 13:08 -0400 schrieb Dianne Skoll: > On Wed, 14 Sep 2016 18:12:39 +0200 > Marcus Schopen wrote: > > > Okay, but this might harm a mail which is in process. Any ideas how to > > fix above error? > > No... no idea. If you don't use embedded Perl

<    1   2   3   4   5   6   7   8   9   10   >