I have 2 questions:
1 If Amavisd-new affect (damage) TLS functionality?
2 What is Closing a DNS loophole with obsolete per-site TLS policies in
postfix TLS Documentation,Amavisd-new with TLS postfix generate is problem?
Thanks
- Original Message -
From: Reindl Harald
To: postfix-users@postfix.org
Sent: Friday, June 17, 2011 2:32 PM
Subject: Re: Amavis 1024-1025 ports combine with TLS
Am 17.06.2011 13:22, schrieb gaby:
I want to use Postfix with TLS support ,but my postfix uses amavisd-new
filter,mails use 1024 and 1025 ports for
filtering in main.cf and master.cf
It is affect my TLS comunication (port 465)? Is possible appear DNS loophole
problem?
main.cf
amavisfeed unix- - n - 2 smtp
-o smtp_data_done_timeout=1200
-o smtp_send_xforward_command=yes
-o disable_dns_lookups=yes
-o max_use=20
master.cf
127.0.0.1:10025 inet n- n - - smtpd
-o content_filter=
-o smtpd_delay_reject=no
-o smtpd_client_restrictions=permit_mynetworks,reject
-o smtpd_helo_restrictions=
-o smtpd_sender_restrictions=
-o smtpd_recipient_restrictions=permit_mynetworks,reject
-o smtpd_data_restrictions=reject_unauth_pipelining
-o smtpd_end_of_data_restrictions=
-o smtpd_restriction_classes=
-o mynetworks=127.0.0.0/8
-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_milters
-o local_header_rewrite_clients=
i do not understand your problem
the filtering happens on loopback-device
where does TLS and even port 465 are involved?
signature.asc
Description: Binary data