Milter-greylist

Hi,

The README says that to use milter-greylist one has to set these
in sendmail.cf:

  O Milter.macros.connect=j,{if_addr}
  O Milter.macros.envfrom=i

Is this really necessary ? When not setting them, the default in
sendmail.cf is set to:

  O Milter.macros.connect=j, _, {daemon_name}, {if_name}, {if_addr}
  O Milter.macros.envfrom=i, {auth_type}, {auth_authen}, {auth_ssf}, {auth_author}, {mail_mailer}, {mail_host}, {mail_addr}

Not sure if I understand the libmilter docs correctly, and whether
milter-greylist needs this exact settings. Is anyone running without
setting Milter.macros ?

Maybe the only real modifications that are needed for milter-greylist
are {verify} when using STARTTLS and {greylist} when using access DB
with milter-greylist.

Thanks,

mp.

At 03:07 PM 5.31.2005 +0200, Martin Paul wrote:
>Hi,
>
>The README says that to use milter-greylist one has to set these
>in sendmail.cf:
>
>  O Milter.macros.connect=j,{if_addr}
>  O Milter.macros.envfrom=i
>
>Is this really necessary ? When not setting them, the default in
>sendmail.cf is set to:
>
>  O Milter.macros.connect=j, _, {daemon_name}, {if_name}, {if_addr}
>  O Milter.macros.envfrom=i, {auth_type}, {auth_authen}, {auth_ssf},
{auth_author}, {mail_mailer}, {mail_host}, {mail_addr}
>
>Not sure if I understand the libmilter docs correctly, and whether
>milter-greylist needs this exact settings. Is anyone running without
>setting Milter.macros ?
>
>Maybe the only real modifications that are needed for milter-greylist
>are {verify} when using STARTTLS and {greylist} when using access DB
>with milter-greylist.
>
>Thanks,
>
>mp.
>

My understanding is that any of those macro setting must include the
settings needed to run the various apps, including to accomodate
milter-greylist --

I have several milters running and use the ones below, which includes
thoses needed by milter-greylist. Without the macros, I get errors -- short
answer is to put in the macros when an app says it is needed to run properly.

define(`confMILTER_MACROS_CONNECT', `j, {daemon_name}, {if_name},
{if_addr}, {client_addr}, {client_name}, {client_port}, {client_re
solve}')
define(`confMILTER_MACROS_HELO', `{tls_version}, {cipher}, {cipher_bits},
{cert_subject}, {cert_issuer}, {verify}')
define(`confMILTER_MACROS_ENVFROM', `i, {auth_type}, {auth_authen},
{auth_ssf}, {auth_author}, {mail_mailer}, {mail_host}, {mail_add
r}')
define(`confMILTER_MACROS_ENVRCPT', `{rcpt_mailer}, {rcpt_host},
{rcpt_addr}, {greylist},')



Happy trails,
Jack L. Stone

System Admin
Sage-american

Martin Paul <martin@...> wrote:

> Not sure if I understand the libmilter docs correctly, and whether
> milter-greylist needs this exact settings. Is anyone running without
> setting Milter.macros ?

It's an exhaustive list for the situation where you use all the optional
features (STARTTLS and friends). Of course depending on your setup, you
might need less macros.

-- 
Emmanuel Dreyfus
http://hcpnet.free.fr/pubz
manu@...

> It's an exhaustive list for the situation where you use all the optional
> features (STARTTLS and friends). Of course depending on your setup, you
> might need less macros.

Ok, I got it now. In fact there's already milter-greylist.m4,
which does the correct thing - it adds just those macros to
Milter.macros.* which are actually missing in sendmail's default.

Maybe you could move that at the top of chapter 2 in the README,
as the recommended way (and/or remove the gory details for modifying
the .cf file directly, which nowadays is quite uncommon).

mp.

Martin Paul <martin@...> wrote:

> Maybe you could move that at the top of chapter 2 in the README,
> as the recommended way (and/or remove the gory details for modifying
> the .cf file directly, which nowadays is quite uncommon).

Heh, that's the way I do it...

-- 
Emmanuel Dreyfus
Le cahier de l'admin BSD 2eme ed. est dans toutes les bonnes librairies
http://www.eyrolles.com/Informatique/Livre/9782212114638/livre-bsd.php
manu@...