Yahoo Groups archive

Milter-greylist

Index last updated: 2026-04-28 23:32 UTC

Message

Re: [milter-greylist] How to use sm_macro "maybe_forged" macro?

2016-01-18 by Chris

On Mon, 18 Jan 2016 08:24:00 +0000 "Emmanuel Dreyfus manu@...
[milter-greylist]" <milter-greylist@yahoogroups.com> wrote

> On Sun, Jan 17, 2016 at 09:54:37PM -0800, 'Chris' miltgrey@...
> [milter-greylist] wrote: > It's not clear to me what format/syntax that entry
> should be. > Can someone please indicate what that entry should be
> > under the "Milter options" section?
> 
> Here is what I have
> O Milter.macros.connect=H, j, _, {daemon_name}, {daemon_port}, {if_name},
> {if_ad dr}, {client_addr}
> O Milter.macros.helo={tls_version}, {cipher}, {cipher_bits}, {cert_subject},
> {ce rt_issuer}
> O Milter.macros.envfrom=i, {auth_type}, {auth_authen}, {auth_ssf},
> {auth_author} , {mail_mailer}, {mail_host}, {mail_addr}
> O Milter.macros.envrcpt={rcpt_mailer}, {rcpt_host}, {rcpt_addr}

Thank you very much for the reply, Emmanuel.
Do any of those entries provide for
sm_macro "maybe_forged"	"{client_resolve}" "FORGED"
from the example in greylist.conf?
I would have *guessed* that I needed the following from my
current sendmail.cf && <host-name>.cf:

O Milter.macros.envrcpt={greylist}

into

O Milter.macros.envrcpt={greylist}, {client_resolve}

in order to get that. As well as changing:

define(`confMILTER_MACROS_ENVRCPT', `{greylist}')

into 

define(`confMILTER_MACROS_ENVRCPT', `{greylist}, {client_resolve}')

in my <host-name>.mc

Am I wrong?

Thanks again, Emmanuel. For taking the time to respond.

--Chris
> 
> 
> 
> -- 
> Emmanuel Dreyfus
> manu@...

Attachments

Move to quarantaine

This moves the raw source file on disk only. The archive index is not changed automatically, so you still need to run a manual refresh afterward.