Quanah Gibson-Mount a écrit :
> Hi,
> 
> I was wondering if anyone had some suggestions on how to deal with an
> issue we're seeing when having both a content filter and a before-queue
> milter in place with postfix.
> 
> Right now, we run through amavis as our content filter:
> 
> main.cf:
> content_filter = smtp-amavis:[127.0.0.1]:10024
> 
> master.cf:
> smtp-amavis unix -      -       n       -       10  smtp
>        -o smtp_data_done_timeout=1200
>        -o smtp_send_xforward_command=yes
>        -o disable_dns_lookups=yes
>        -o max_use=20
> 127.0.0.1:10025 inet n  -       n       -       -  smtpd
>        -o content_filter=
>        -o local_recipient_maps=
>        -o virtual_mailbox_maps=
>        -o virtual_alias_maps=
>        -o relay_recipient_maps=
>        -o smtpd_restriction_classes=
>        -o smtpd_delay_reject=no
>        -o smtpd_client_restrictions=permit_mynetworks,reject
>        -o smtpd_helo_restrictions=
>        -o smtpd_sender_restrictions=
>        -o smtpd_milter=
>        -o smtpd_recipient_restrictions=permit_mynetworks,reject
>        -o mynetworks_style=host
>        -o mynetworks=127.0.0.0/8
>        -o strict_rfc821_envelopes=yes
>        -o smtpd_error_sleep_time=0
>        -o smtpd_soft_error_limit=1001
>        -o smtpd_hard_error_limit=1000
>        -o smtpd_client_connection_count_limit=0
>        -o smtpd_client_connection_rate_limit=0
>        -o
> receive_override_options=no_header_body_checks,no_unknown_recipient_checks,no_address_mappings
> 
> 127.0.0.1:14225 inet n  -       n       -       -  smtpd
>        -o smtpd_tls_cert_file=/home/xxxxxx
>        -o smtpd_tls_key_file=/home/xxxxxx
> 127.0.0.1:14265 inet n  -       n       -       -  smtpd
>        -o smtpd_tls_cert_file=/home/xxxxxxx
>        -o smtpd_tls_key_file=/home/xxxxxxxx
>        -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes
> 
> 
> We've also added a milter that does some spam checking as well. 
> However, this milter is getting 127.0.0.1 as the client IP address from
> postfix.
>> From looking at the logs, this is being done by Amavis.  And if we
>> turn off 
> using amavis, the correct client IP ends up being used.  Is there any
> way in postfix to force the milter processing to come before amavis,
> since it is rewriting the values used for the "_" and {client_addr}?
> 


you have a problem with the smtpd before the content_filter, yet you
only show infos about the other smtpd...

so let me mount my /dev/crystal/ball: would it be because of the missing
 's' in smtpd_milters?

Reply via email to