On 08/06/16 16:24, Catalin Bucur wrote: > submission inet n - n - - smtpd > -o syslog_name=postfix/submission > -o smtpd_etrn_restrictions=reject > -o smtpd_enforce_tls=yes > -o smtpd_tls_auth_only=yes > -o smtpd_sasl_auth_enable=yes > -o smtpd_use_tls=yes > -o receive_override_options=no_address_mappings > -o > smtpd_client_restrictions=permit_mynetworks,permit_sasl_authenticated,reject > > > > Jun 8 16:20:21 mail postfix/submission/smtpd[3746]: connect from > unknown[213.233.85.145] > Jun 8 16:20:21 mail postfix/submission/smtpd[3746]: NOQUEUE: reject: > CONNECT from unknown[213.233.85.145]: 554 5.7.1 > <unknown[213.233.85.145]>: Client host rejected: Access denied; proto=SMTP > > > Doar daca scot linia cu smtpd_client_restrictions din master.cf imi > functioneaza trimiterea.
Am gasit raspunsul pana la urma: "> smtpd_delay_reject = no http://www.postfix.org/postconf.5.html#smtpd_delay_reject Here, most likely. Ran into something very similar last week, and this was the cause. I suspect that if you were to increase logging detail, you'd find that 'permit_sasl_authenticated' evaluates to zero during the client restrictions stage because of a delay in getting back an answer from whatever SASL backend you have in use. Postfix evaluates the rest of the client restrictions, and denies you access. Try setting 'smtpd_delay_reject' to yes, which is the default, and consolidate all your restrictions under 'smtpd_recipient_restrictions' instead." Intr-adevar aveam setat pe no smtpd_delay_reject pentru alte restrictii. Am revenit pe yes deocamdata si s-a rezolvat si problema initiala. Numai bine, Catalin Bucur _______________________________________________ RLUG mailing list [email protected] http://lists.lug.ro/mailman/listinfo/rlug
