Milter-greylist

On Wed, 25 Oct 2006, manu@... wrote:

> Date: Wed, 25 Oct 2006 18:02:58 +0200
> From: manu@...
> Reply-To: milter-greylist@yahoogroups.com
> To: milter-greylist@yahoogroups.com
> Subject: Re: [milter-greylist] How to use sendmail db files?
> 
> Jeff A. Earickson <jaearick@...> wrote:
>
>> I stuck the line below into macro.c.  Now I get beaucoup of:
>> milter-greylist: ...  me->m_macro = "{popauth}", value = "(null)"
> (snip)
>> # Milter options
>> O Milter.LogLevel=12
>> O Milter.macros.connect=j,{if_addr}
>> # O Milter.macros.helo={verify}, {cert_subject}
>> O Milter.macros.envfrom=i,{popauth}
>> O
> Milter.macros.envrcpt={rcpt_mailer},{rcpt_host},{rcpt_addr},{greylist},{
> popauth}
>> #O Milter.macros.eom={msg_id}
>>
>> trying various settings for envfrom and envrcpt (I don't understand
>> what happens here, so I don't know what I am doing).  Nothing that
>> I have tried in the Milter.macros gives me anything other than
>> value = "(null)" in the syslog lines.  Here is what some of the syslogging
>> looks like:
>
> Weird. Can you add another mg_log to check what happens if you try to
> other macros that are known to be okay? Can you read {i} or {rcpt_addr},
> for instance?

I'm confused again...  The line that I added in macro_check() seems 
general -- it should report on any macro, right?  But all it ever
mentions is {popauth}.  What would I put where?  Can't I just put
"debug" in the greylist.conf file and get a lot of debugging?  Maybe
this is overkill...

Jeff Earickson
Colby College