On Tue, Apr 02, 2019 at 07:15:58PM +0200, Francesc Peñalvez wrote:
> smtpd_client_restrictions = permit_mynetworks permit_inet_interfaces
> permit_tls_all_clientcerts permit_sasl_authenticated
> permit_auth_destination
> check_client_access hash:/etc/postfix/access
The "permit_tls_all_
yes every change in access i use postmap access
i I will try the changes that you suggest and I will comment something
Thanks for help
El 02/04/2019 a las 21:11, Noel Jones escribió:
Great.
Change this:
smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated
defer_unauth_
Great.
Change this:
smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated
defer_unauth_destination permit_inet_interfaces check_client_access
hash:/etc/postfix/access reject_unknown_reverse_client_hostname
to this:
smtpd_relay_restrictions =
permit_mynetworks
pe
the problem that I have already described
I have several rules against spamers and one of them is to reject the
ips that are not resolved.
So when the resolution of the dns fails those ips are rejected for not
having an inverse. In the access I have the ips that interest me that
these locks pas
On 4/2/2019 12:15 PM, Francesc Peñalvez wrote:
the problem is with the directive
reject_unknown_reverse_client_hostname when there is a failure in
the resolution of the ip blocks the connection with this ip, to
avoid adding the access file the ip as indicated in the first mail,
but still block
the ip of my last mail does not match the first, but it is from the same
company that uses several ips and all of them are added to the access file
El 02/04/2019 a las 19:15, Francesc Peñalvez escribió:
the problem is with the directive
reject_unknown_reverse_client_hostname when there is a fa
the problem is with the directive reject_unknown_reverse_client_hostname
when there is a failure in the resolution of the ip blocks the
connection with this ip, to avoid adding the access file the ip as
indicated in the first mail, but still blocking that ip by not
resolving. activate the debug
On 2 Apr 2019, at 11:17, Francesc Peñalvez wrote:
following the instructions given to me place the access in front of
the rule that is not supported ips unresolved, and as I still have the
same problems I added a debug to that ip that interests me and among
other things in this debug I find th
On 4/2/2019 10:17 AM, Francesc Peñalvez wrote:
following the instructions given to me place the access in front of
the rule that is not supported ips unresolved, and as I still have
the same problems I added a debug to that ip that interests me and
among other things in this debug I find this:
following the instructions given to me place the access in front of the
rule that is not supported ips unresolved, and as I still have the same
problems I added a debug to that ip that interests me and among other
things in this debug I find this:
16:43:05 ns postfix / smtpd [28258]: generic_che
10 matches
Mail list logo
