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

2016-10-11 Thread Marcus Schopen
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)

2016-10-11 Thread 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 > 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)

2016-10-11 Thread Marcus Schopen
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)

2016-10-11 Thread 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. Regards, Dianne. ___ NOTE: