Re: PATCH: saslauthd show remote ip address

Quanah Gibson-Mount: > Amavis passes it back to Postfix on port 25, and boom, the sasl bits are > called, even though no auth is involved. If you know that an SMTP daemon will not receive AUTH commands, disable SASL in master.cf, with "-o smtpd_sasl_auth_enable=no". Wietse

Re: PATCH: saslauthd show remote ip address

--On Saturday, January 09, 2016 9:06 AM -0500 Wietse Venema wrote: Quanah Gibson-Mount: Amavis passes it back to Postfix on port 25, and boom, the sasl bits are called, even though no auth is involved. If you know that an SMTP daemon will not receive AUTH commands,

Re: PATCH: saslauthd show remote ip address

Quanah Gibson-Mount: > --On Saturday, January 09, 2016 9:06 AM -0500 Wietse Venema > wrote: > > > Quanah Gibson-Mount: > >> Amavis passes it back to Postfix on port 25, and boom, the sasl bits are > >> called, even though no auth is involved. > > > > If you know that an

Re: PATCH: saslauthd show remote ip address

--On Tuesday, January 05, 2016 12:46 PM -0800 Quanah Gibson-Mount wrote: --On Tuesday, January 05, 2016 3:43 PM -0500 Wietse Venema wrote: I think I mentioned in this thread that the patch is not complete because the Cyrus implementation expects a

Re: PATCH: saslauthd show remote ip address

--On Thursday, December 10, 2015 11:49 AM -0800 Quanah Gibson-Mount wrote: --On Thursday, December 10, 2015 2:29 PM -0500 Wietse Venema wrote: Quanah Gibson-Mount: --On Thursday, December 10, 2015 2:02 PM -0500 Wietse Venema

Re: PATCH: saslauthd show remote ip address

Quanah Gibson-Mount: > --On Thursday, December 10, 2015 11:49 AM -0800 Quanah Gibson-Mount > wrote: > > > --On Thursday, December 10, 2015 2:29 PM -0500 Wietse Venema > > wrote: > > > >> Quanah Gibson-Mount: > >>> --On Thursday, December 10, 2015 2:02

Re: PATCH: saslauthd show remote ip address

--On Tuesday, January 05, 2016 3:43 PM -0500 Wietse Venema wrote: I think I mentioned in this thread that the patch is not complete because the Cyrus implementation expects a string of the form "ipaddress:portnumber", and the patch provides the address only. Yep.

Re: PATCH: saslauthd show remote ip address

--On Wednesday, December 02, 2015 9:05 AM -0500 Wietse Venema wrote: Selcuk Yazar: Thank you Koko for warning , hopelessly i try to my chance :( but i found this after ,i sent email "...From a cursory inspection of lib/pwcheck.c, saslauthd does not get passed any

Re: PATCH: saslauthd show remote ip address

Quanah Gibson-Mount: > --On Thursday, December 10, 2015 2:02 PM -0500 Wietse Venema > wrote: > > > This is not completely trivial because the port information needs > > to be consistent with information from proxies, postscreen, and > > XCLIENT, otherwise results will be

Re: PATCH: saslauthd show remote ip address

--On Thursday, December 10, 2015 2:29 PM -0500 Wietse Venema wrote: Quanah Gibson-Mount: --On Thursday, December 10, 2015 2:02 PM -0500 Wietse Venema wrote: > This is not completely trivial because the port information needs > to be consistent

Re: PATCH: saslauthd show remote ip address

--On Thursday, December 10, 2015 2:02 PM -0500 Wietse Venema wrote: This is not completely trivial because the port information needs to be consistent with information from proxies, postscreen, and XCLIENT, otherwise results will be incorrect. Ok, good to know. Is

Re: PATCH: saslauthd show remote ip address

Quanah Gibson-Mount: > --On Wednesday, December 02, 2015 9:05 AM -0500 Wietse Venema > wrote: > > > Selcuk Yazar: > >> Thank you Koko for warning , hopelessly i try to my chance :( > >> > >> but i found this after ,i sent email > >> > >> "...From a cursory inspection of

PATCH: saslauthd show remote ip address

Selcuk Yazar: > Thank you Koko for warning , hopelessly i try to my chance :( > > but i found this after ,i sent email > > "...From a cursory inspection of lib/pwcheck.c, saslauthd does not get > passed > any client IP information and cannot log it or forward it to pam..." Postfix currently