Milter-greylist

Petter Larsen <petter.larsen@...> wrote:

> I get huge mail bunch to non existing users. They also get
> autowhite-listed when they are resend earlier than 30 minutes.
> 
> Is it possible to block this?

If you have a local alias table for all recipients, you can do that:
some.user@...   login@...

milter-ahead is another option that will let you check the recipient
validity before accepting the mail.

I'm also considering writing a milter that would reject any mail to a
recipient not listed in a file. That should be easy to do and quite
stable. I'll need to find a name: milter-badrcpt? :)

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

On Sun, Jul 11, 2004 at 07:59:55PM +0200, Emmanuel Dreyfus wrote:
> > I get huge mail bunch to non existing users. They also get
> > autowhite-listed when they are resend earlier than 30 minutes.
> > Is it possible to block this?
> If you have a local alias table for all recipients, you can do that:
> some.user@...   login@...

There is a better way to implement this with sendmail:

1.) Add "FEATURE(blacklist_recipients)" to the ".mc" file used to built
    your sendmail configuration.

2.) Add the domain you are accepting e-mail for to "/etc/mail/relay-domains".

3.) Instead of adding ...

To:domain.com					RELAY

   ... to "/etc/mail/access" add explicit entries like this:

user1@...				RELAY
user2@...				RELAY
user3@...				RELAY
[...]
user99@...				RELAY
To:domain.com					error:5.1.1:550 User unknown

Using a setup like this will make sure that your mail only accepts e-mail
for valid address. The sendmail on my system bounces invalid addresses
without greylisting them:

Jul 11 03:49:03 colwyn sm-mta[25815]: i6B1n0Yf025815: ruleset=check_rcpt, arg1=<fuji@...>, relay=[65.182.128.171], reject=550 5.1.1 <fuji@...>... User unknown
Jul 11 03:49:03 colwyn sm-mta[25815]: i6B1n0Yf025815: from=<Santiago@...>, size=0, class=0, nrcpts=0, proto=SMTP, daemon=MTA, relay=[65.182.128.171]

This is of course only necessary when your system accepts e-mail for
non-local users. Invalid local addresses will always be bounced before
greylisting is applied.

	Kind regards

-- 
Matthias Scheler                                  http://scheler.de/~matthias/

Petter Larsen <petter.larsen@...> wrote:

> > If you have a local alias table for all recipients, you can do that:
> > some.user@...   login@... 
> Can't say I understand this.

Sendmail will reject invalid recpipients in its local domains during the
SMTP session. It seems your setup is a MX that forward everything to
another machine (let's call it mailhost), else you woundln't accept
invalid recipients.

A possible way of dealing with that is to treat your domain as local on
the MX and have an alias table that forward the mail to mailhost. That
way your MX will not accept mail to an invalid recipient.

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

On Sun, Jul 11, 2004 at 11:21:14PM +0200, Matthias Scheler wrote:
> 
> Using a setup like this will make sure that your mail only accepts e-mail
> for valid address. The sendmail on my system bounces invalid addresses
> without greylisting them:
> 
> Jul 11 03:49:03 colwyn sm-mta[25815]: i6B1n0Yf025815: ruleset=check_rcpt, arg1=<fuji@...>, relay=[65.182.128.171], reject=550 5.1.1 <fuji@...>... User unknown
> Jul 11 03:49:03 colwyn sm-mta[25815]: i6B1n0Yf025815: from=<Santiago@...>, size=0, class=0, nrcpts=0, proto=SMTP, daemon=MTA, relay=[65.182.128.171]
> 
> This is of course only necessary when your system accepts e-mail for
> non-local users. Invalid local addresses will always be bounced before
> greylisting is applied.

We use a perl script to populate an access file from Exchange's LDAP
info and reject as above. Of course, if Exchange didn't blindly accept
and then reject later, we wouldn't have to jump though these hoops.

Graham

Petter Larsen <petter.larsen@...> wrote:

> I get huge mail bunch to non existing users. They also get
> autowhite-listed when they are resend earlier than 30 minutes.

If anyone is interested, I wrote a milter that does an access-list on
recipients. A bit like the recipient blacklist of sendmail, except that
it supports regex.

No doc, no configure script, I just wrote it for myself, but I can
publish it "as is" if someone is interested.

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

At 09:33 PM 7.27.2004 +0200, manu@... wrote:
>Petter Larsen <petter.larsen@...> wrote:
>
>> I get huge mail bunch to non existing users. They also get
>> autowhite-listed when they are resend earlier than 30 minutes.
>
>If anyone is interested, I wrote a milter that does an access-list on
>recipients. A bit like the recipient blacklist of sendmail, except that
>it supports regex.
>
>No doc, no configure script, I just wrote it for myself, but I can
>publish it "as is" if someone is interested.
>
>-- 
>Emmanuel Dreyfus

Please count me as being VERY interested. I really like the "milter"
approach in order to catch the bad stuff as close to the front door (MTA)
as possible.

I'm using
FBSD-4.10/Sendmail-8.12.11/Milter-Greylist-1.53/Milter-Regex-1.5/Spamass-mil
ter-0.2.0_4/spamassassin-2.63(spamd)/Procmail-3.22_4

I've tried to add Milter-Sender without luck -- it core dumps and dies.

Again, please add me to the list for your new milter.... thanks!

Best regards,
Jack L. Stone,
Administrator

Sage American
http://www.sage-american.com
jacks@...

On Tue, Jul 27, 2004 at 09:00:04PM -0500, Jack L. Stone wrote:
> >If anyone is interested, I wrote a milter that does an access-list on
> >recipients. A bit like the recipient blacklist of sendmail, except that
> >it supports regex.
(snip)
> Please count me as being VERY interested. I really like the "milter"
> approach in order to catch the bad stuff as close to the front door (MTA)
> as possible.

Here it is, "as-is" after 4 hours of work, to get just what I want:

ftp://ftp.espci.fr/pub/milter-rcptfilter/milter-rcptfilter-0.5.tgz
SHA1 (milter-rcptfilter-0.5.tgz) = bd45295e07cb38099926cfebc25badbe9b1492f9

In a world where I could fork myself, I'd use that as a base to make
milter-acl, which would enable filtering with strings or regex on 
connexion IP, connexion DNS, helo string, envelope from, envelope recipient, 
header or body. It could have rule grouping, and a quick keyword to pass
through the next rules, 

I imagine an access file like this, a la ipfilter:

reject quick helo "^192\.0\.2\.1" message "Hello string should be your FQDN, not my IP"
reject /^TVqQAAMAAAA/ message "No win32 bins here" head 100
accept rcpt "precautious.user@example;com" group 100
accept rcpt "another.user@example;com" group 100
tempfail quick ip "192.0.240.1" message "I know you are an evil spammer so I'll always tempfail you just to waste your mail queues"

But I have no time to work on that. 

-- 
Emmanuel Dreyfus
manu@...

At 10:20 AM 7.28.2004 +0000, Emmanuel Dreyfus wrote:
>On Tue, Jul 27, 2004 at 09:00:04PM -0500, Jack L. Stone wrote:
>> >If anyone is interested, I wrote a milter that does an access-list on
>> >recipients. A bit like the recipient blacklist of sendmail, except that
>> >it supports regex.
>(snip)
>> Please count me as being VERY interested. I really like the "milter"
>> approach in order to catch the bad stuff as close to the front door (MTA)
>> as possible.
>
>Here it is, "as-is" after 4 hours of work, to get just what I want:
>
>ftp://ftp.espci.fr/pub/milter-rcptfilter/milter-rcptfilter-0.5.tgz
>SHA1 (milter-rcptfilter-0.5.tgz) = bd45295e07cb38099926cfebc25badbe9b1492f9
>
>In a world where I could fork myself, I'd use that as a base to make
>milter-acl, which would enable filtering with strings or regex on 
>connexion IP, connexion DNS, helo string, envelope from, envelope recipient, 
>header or body. It could have rule grouping, and a quick keyword to pass
>through the next rules, 
>
>I imagine an access file like this, a la ipfilter:
>
>reject quick helo "^192\.0\.2\.1" message "Hello string should be your
FQDN, not my IP"
>reject /^TVqQAAMAAAA/ message "No win32 bins here" head 100
>accept rcpt "precautious.user@example;com" group 100
>accept rcpt "another.user@example;com" group 100
>tempfail quick ip "192.0.240.1" message "I know you are an evil spammer so
I'll always tempfail you just to waste your mail queues"
>
>But I have no time to work on that. 
>
>-- 
>Emmanuel Dreyfus

Thanks, Emmanuel. I'll start playing with this one. Appreciate your work!

Best regards,
Jack L. Stone,
Administrator

Sage American
http://www.sage-american.com
jacks@...

On Tue, Jul 27, 2004 at 09:00:04PM -0500, Jack L. Stone wrote:
> Again, please add me to the list for your new milter.... thanks!

I released milter-rcptfilter-0.6 this morning. It fixes a case sentiveness
problem when matching addresses.

ftp ftp://ftp.Espci.fr/pub/milter-rcptfilter/milter-rcptfilter-0.6.tgz
SHA1 (milter-rcptfilter-0.6.tgz) = 7ffd8ea6fa73850743d67e2c8dfd0725be70f438
-- 
Emmanuel Dreyfus
manu@...

Emmanuel: Thanks for the new version. Alas, yesterday I ran into an install
snag on the first version because it wants "pthreads" which my FBSD
environment doesn't have.....

Any way around that....??

At 09:19 AM 7.29.2004 +0000, you wrote:
>On Tue, Jul 27, 2004 at 09:00:04PM -0500, Jack L. Stone wrote:
>> Again, please add me to the list for your new milter.... thanks!
>
>I released milter-rcptfilter-0.6 this morning. It fixes a case sentiveness
>problem when matching addresses.
>
>ftp ftp://ftp.Espci.fr/pub/milter-rcptfilter/milter-rcptfilter-0.6.tgz
>SHA1 (milter-rcptfilter-0.6.tgz) = 7ffd8ea6fa73850743d67e2c8dfd0725be70f438
>-- 
>Emmanuel Dreyfus
>manu@...
>
>
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>

Best regards,
Jack L. Stone,
Administrator

Sage American
http://www.sage-american.com
jacks@...

"Jack L. Stone" <jacks@...> writes:

> Emmanuel: Thanks for the new version. Alas, yesterday I ran into an install
> snag on the first version because it wants "pthreads" which my FBSD
> environment doesn't have.....

Which release of FreeBSD are you running ?

At 02:57 PM 7.29.2004 +0200, Cyril Guibourg wrote:
>"Jack L. Stone" <jacks@...> writes:
>
>> Emmanuel: Thanks for the new version. Alas, yesterday I ran into an install
>> snag on the first version because it wants "pthreads" which my FBSD
>> environment doesn't have.....
>
>Which release of FreeBSD are you running ?
>

Running FBSD-4.10-R....

Any ideas?

Best regards,
Jack L. Stone,
Administrator

Sage American
http://www.sage-american.com
jacks@...

Jack L. Stone <jacks@...> wrote:

> Emmanuel: Thanks for the new version. Alas, yesterday I ran into an install
> snag on the first version because it wants "pthreads" which my FBSD
> environment doesn't have.....

Heh, I told you it was "as-is".
Remove -lpthread and build with -pthread or -l_c, both should work.

-- 
Emmanuel Dreyfus
Il y a 10 sortes de personnes dans le monde: ceux qui comprennent 
le binaire et ceux qui ne le comprennent pas.
manu@...

At 07:32 PM 7.29.2004 +0200, you wrote:
>Jack L. Stone <jacks@...> wrote:
>
>> Emmanuel: Thanks for the new version. Alas, yesterday I ran into an install
>> snag on the first version because it wants "pthreads" which my FBSD
>> environment doesn't have.....
>
>Heh, I told you it was "as-is".
>Remove -lpthread and build with -pthread or -l_c, both should work.
>
>-- 
>Emmanuel Dreyfus
>

Indeed you did say "as-is" and that echoed in my head as I typed the appeal
for help.

Your -pthread modification seems to have done the trick for the build. Now
to try it....

Perhaps my question has eliminated other similar questions like this by
some with equal or less FBSD ability......

Thanks again, Emmanuel. BTW, am really enjoying "milter-greylist".

Best regards,
Jack L. Stone,
Administrator

Sage American
http://www.sage-american.com
jacks@...

"Jack L. Stone" <jacks@...> writes:

> Running FBSD-4.10-R....

4.10 has pthreads

> Any ideas?

Check cc & ld args. there should be no -lc_r and there should be -pthreads

This is one issue I faced with milter-greylist. You can glance at
milter-greylist port patch files.

Hope this helps.

Cyril Guibourg <cg+milter-greylist@...> writes:

> Hope this helps.

Ooops, I didn't saw that Emmanuel already gave to you the solution.

At 09:04 PM 7.29.2004 +0200, Cyril Guibourg wrote:
>Cyril Guibourg <cg+milter-greylist@...> writes:
>
>> Hope this helps.
>
>Ooops, I didn't saw that Emmanuel already gave to you the solution.
>

That's OK, I can use all the help I can get. Appreciate the response.

As a follow-up, I have it running nicely and now just have to start
building the block/pass list. I have log level running at 14 and see that
it is running right in the proper order I wanted.

I can see this will become a favorite watering hole for me! I jumped for
joy at getting more control at the MTA sendmail level to avoid needing
those heavier uses of resources used by SpamAssassin and others.

Thanks to Emmanuel again -- looking forward to the new features allowing
the milters to read access-type files, perhaps -- or whatever works best.

Best regards,
Jack L. Stone,
Administrator

Sage American
http://www.sage-american.com
jacks@...

At 03:45 PM 7.29.2004 -0500, Jack L. Stone wrote:
>At 09:04 PM 7.29.2004 +0200, Cyril Guibourg wrote:
>>Cyril Guibourg <cg+milter-greylist@...> writes:
>>
>>> Hope this helps.
>>
>>Ooops, I didn't saw that Emmanuel already gave to you the solution.
>>
>
>That's OK, I can use all the help I can get. Appreciate the response.
>
>As a follow-up, I have it running nicely and now just have to start
>building the block/pass list. I have log level running at 14 and see that
>it is running right in the proper order I wanted.
>

FBSD-4.10/Sendmail-8.12.11

I have the rcptfilter installed and some favorite pests placed in the
config file, including a test ISP address I used. Nothing is being blocked
that I can see.

According to the maillog, the rcptfiler is connecting and continues to hang
in there, but doesn't snag anything.

I have the filter loading okay in the sendmail.cf and use the following to
start it:
/usr/local/sbin/milter-rcptfilter -c /usr/local/etc/rcptfilter.conf \
	-p /var/run/milter-rcptfilter/rcptfilter.sock

Anyone else having better luck??

Best regards,
Jack L. Stone,
Administrator

Sage American
http://www.sage-american.com
jacks@...

On Fri, Jul 30, 2004 at 07:59:57AM -0500, Jack L. Stone wrote:
> I have the filter loading okay in the sendmail.cf and use the following to
> start it:
> /usr/local/sbin/milter-rcptfilter -c /usr/local/etc/rcptfilter.conf \
> 	-p /var/run/milter-rcptfilter/rcptfilter.sock
> 
> Anyone else having better luck??

Of course I have :)

What do you have in sendmail's log? Does milter-rcptfilter go to error state?
If you run the rcptfilter in the foreground (using -d), what do you have?

If you can't get what"s wrong, try adding a printf in mlfi_connect() to see
if the milter is invoked at all when a new connection gets in.

-- 
Emmanuel Dreyfus
manu@...

At 01:07 PM 7.30.2004 +0000, Emmanuel Dreyfus wrote:
>On Fri, Jul 30, 2004 at 07:59:57AM -0500, Jack L. Stone wrote:
>> I have the filter loading okay in the sendmail.cf and use the following to
>> start it:
>> /usr/local/sbin/milter-rcptfilter -c /usr/local/etc/rcptfilter.conf \
>> 	-p /var/run/milter-rcptfilter/rcptfilter.sock
>> 
>> Anyone else having better luck??
>
>Of course I have :)
>

...of course

>What do you have in sendmail's log? Does milter-rcptfilter go to error state?
>If you run the rcptfilter in the foreground (using -d), what do you have?
>

No error state -- looks normal (to me)
I did run it with the -D but not -d yet

>If you can't get what"s wrong, try adding a printf in mlfi_connect() to see
>if the milter is invoked at all when a new connection gets in.
>

I'll try that too....

Here's the maillog on one incoming showing milter connections & continues:

=======================================================
Jul 30 09:22:01 sage-american sm-mta[51967]: i6UEM1cl051967: Milter
(rcptfilter): init success to negotiate
Jul 30 09:22:01 sage-american sm-mta[51967]: i6UEM1cl051967: Milter
(greylist): init success to negotiate
Jul 30 09:22:01 sage-american sm-mta[51967]: i6UEM1cl051967: Milter
(milter-regex): init success to negotiate
Jul 30 09:22:01 sage-american sm-mta[51967]: i6UEM1cl051967: Milter
(spamassassin): init success to negotiate
Jul 30 09:22:01 sage-american sm-mta[51967]: i6UEM1cl051967: Milter:
connect to filters
Jul 30 09:22:01 sage-american sm-mta[51967]: i6UEM1cl051967:
milter=rcptfilter, action=connect, continue
Jul 30 09:22:01 sage-american sm-mta[51967]: i6UEM1cl051967:
milter=greylist, action=connect, continue
Jul 30 09:22:01 sage-american sm-mta[51967]: i6UEM1cl051967:
milter=milter-regex, action=connect, continue
Jul 30 09:22:01 sage-american sm-mta[51967]: i6UEM1cl051967:
milter=spamassassin, action=connect, accepted
Jul 30 09:22:01 sage-american sm-mta[51967]: i6UEM1cl051967:
milter=milter-regex, action=helo, continue
Jul 30 09:22:01 sage-american milter-greylist: i6UEM1cl051967: address
65.68.247.73 is in exception list
Jul 30 09:22:01 sage-american sm-mta[51967]: i6UEM1cl051967:
milter=greylist, action=mail, continue
Jul 30 09:22:01 sage-american sm-mta[51967]: i6UEM1cl051967:
milter=milter-regex, action=mail, continue
Jul 30 09:22:01 sage-american sm-mta[51967]: i6UEM1cl051967:
milter=rcptfilter, action=rcpt, continue
Jul 30 09:22:01 sage-american sm-mta[51967]: i6UEM1cl051967:
milter=greylist, action=rcpt, continue
Jul 30 09:22:01 sage-american sm-mta[51967]: i6UEM1cl051967:
milter=milter-regex, action=rcpt, continue
Jul 30 09:22:02 sage-american sm-mta[51967]: i6UEM1cl051967:
from=<jack@...>, size=2291, class=0, nrcpts=1,
msgid=<GJENLKEBMBFGINPDCHJKEEPEDLAA.jack@...>, proto=SMTP,
daemon=MTA, relay=adsl-65-68-247-73.dsl.crchtx.swbell.net [65.68.247.73]
Jul 30 09:22:02 sage-american sm-mta[51967]: i6UEM1cl051967: Milter add:
header: X-Greylist: Sender IP whitelisted, not delayed by
milter-greylist-1.5.3 (sage-american.com [192.168.0.5]); Fri, 30 Jul 2004
09:22:02 -0500 (CDT)
Jul 30 09:22:02 sage-american sm-mta[51967]: i6UEM1cl051967:
milter=milter-regex, action=header, continue
Jul 30 09:22:02 sage-american last message repeated 14 times
Jul 30 09:22:02 sage-american sm-mta[51967]: i6UEM1cl051967:
milter=milter-regex, action=eoh, continue
Jul 30 09:22:02 sage-american sm-mta[51967]: i6UEM1cl051967:
milter=milter-regex, action=body, continue
Jul 30 09:22:02 sage-american sm-mta[51967]: i6UEM1cl051967: Milter accept:
message
=======================================================

>-- 
>Emmanuel Dreyfus
>manu@...
>
>
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>

Best regards,
Jack L. Stone,
Administrator

Sage American
http://www.sage-american.com
jacks@...

At 09:28 AM 7.30.2004 -0500, Jack L. Stone wrote:
>At 01:07 PM 7.30.2004 +0000, Emmanuel Dreyfus wrote:
>>On Fri, Jul 30, 2004 at 07:59:57AM -0500, Jack L. Stone wrote:
>>> I have the filter loading okay in the sendmail.cf and use the following to
>>> start it:
>>> /usr/local/sbin/milter-rcptfilter -c /usr/local/etc/rcptfilter.conf \
>>> 	-p /var/run/milter-rcptfilter/rcptfilter.sock
>>> 
>>> Anyone else having better luck??
>>
>>Of course I have :)
>>
>
>...of course
>
>>What do you have in sendmail's log? Does milter-rcptfilter go to error
state?
>>If you run the rcptfilter in the foreground (using -d), what do you have?
>>
>
>No error state -- looks normal (to me)
>I did run it with the -D but not -d yet
>

The -d switch is illegal says the script, but here's the -D switch output:

root@sage-american>> /usr/local/sbin/milter-rcptfilter -u smmsp -D -c
/usr/local/etc/rcptfilter.conf -p /var/run/milter-rcptfilter/rcptfilter.sock
milter-rcptfilter: reloading /usr/local/etc/rcptfilter.conf
milter-rcptfilter: adding regex /.*@.*opplink\.com/: Block
milter-rcptfilter: adding regex /.*@.*\.biz/: Block
milter-rcptfilter: adding regex /lkfjj@cebik\.com/: Block
milter-rcptfilter: adding regex /.*@.*mail\.ru/: Block
milter-rcptfilter: adding regex /.*@.*sharingexperiences\.info/: Block
milter-rcptfilter: adding regex /.*@.*sharingopinion\.net/: Block
milter-rcptfilter: adding regex /.*@.*compsandbonus\.com/: Block
milter-rcptfilter: adding regex /.*@.*microsoft\.com/: Block
milter-rcptfilter: adding regex /.*@.*eudora\.com/: Block
milter-rcptfilter: adding regex /.*@asafeserver\.com/: Pass
milter-rcptfilter: adding regex /sales@nittany-scientific\.com/: Pass
milter-rcptfilter: adding regex /trish@nittany-scientific\.com/: Pass
milter-rcptfilter: adding regex /.*@netwood\.net/: Pass

Best regards,
Jack L. Stone,
Administrator

Sage American
http://www.sage-american.com
jacks@...

At 01:07 PM 7.30.2004 +0000, Emmanuel Dreyfus wrote:
>On Fri, Jul 30, 2004 at 07:59:57AM -0500, Jack L. Stone wrote:
>> I have the filter loading okay in the sendmail.cf and use the following to
>> start it:


>If you can't get what"s wrong, try adding a printf in mlfi_connect() to see
>if the milter is invoked at all when a new connection gets in.
>

As my ealier message shows, it is being invoked. It connects and continues.

Here's another log:

Jul 30 10:03:21 sage-american sm-mta[52261]: i6UF3LqZ052261: Milter
(rcptfilter): init success to negotiate
Jul 30 10:03:21 sage-american sm-mta[52261]: i6UF3LqZ052261: Milter
(greylist): init success to negotiate
Jul 30 10:03:21 sage-american sm-mta[52261]: i6UF3LqZ052261: Milter
(milter-regex): init success to negotiate
Jul 30 10:03:21 sage-american sm-mta[52261]: i6UF3LqZ052261: Milter
(spamassassin): init success to negotiate
Jul 30 10:03:21 sage-american sm-mta[52261]: i6UF3LqZ052261: Milter:
connect to filters
Jul 30 10:03:21 sage-american sm-mta[52261]: i6UF3LqZ052261:
milter=rcptfilter, action=connect, continue
Jul 30 10:03:21 sage-american sm-mta[52261]: i6UF3LqZ052261:
milter=greylist, action=connect, continue
Jul 30 10:03:21 sage-american sm-mta[52261]: i6UF3LqZ052261:
milter=milter-regex, action=connect, continue
Jul 30 10:03:21 sage-american sm-mta[52261]: i6UF3LqZ052261:
milter=spamassassin, action=connect, continue
Jul 30 10:03:21 sage-american sm-mta[52261]: i6UF3LqZ052261:
milter=milter-regex, action=helo, continue
Jul 30 10:03:21 sage-american sm-mta[52261]: i6UF3LqZ052261:
milter=spamassassin, action=helo, continue
Jul 30 10:03:21 sage-american sm-mta[52261]: i6UF3LqZ052261:
milter=greylist, action=mail, continue
Jul 30 10:03:21 sage-american sm-mta[52261]: i6UF3LqZ052261:
milter=milter-regex, action=mail, continue
Jul 30 10:03:21 sage-american sm-mta[52261]: i6UF3LqZ052261:
milter=spamassassin, action=mail, continue
Jul 30 10:03:21 sage-american sm-mta[52261]: i6UF3LqZ052261:
milter=rcptfilter, action=rcpt, continue

>-- 
>Emmanuel Dreyfus
>manu@...
>
>
>
> 
>Yahoo! Groups Links
>
>
>
> 
>
>

Best regards,
Jack L. Stone,
Administrator

Sage American
http://www.sage-american.com
jacks@...

On Fri, Jul 30, 2004 at 10:04:59AM -0500, Jack L. Stone wrote:
> As my ealier message shows, it is being invoked. It connects and continues.

Then add a printf in mlfi_envrcpt, add some prntf in except_check to see
what's going on when a mail gets in. The code is quite simple.

-- 
Emmanuel Dreyfus
manu@...