|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Re: the purpose of smtpd_sasl_authenticated_header
lst_hoe01
kwsoft.de
Date: Tue May 02 2006 - 15:13:22 CDT
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Zitat von Udo Rader <udo.rader
bestsolution.at>:
> Am Dienstag, den 02.05.2006, 21:35 +0200 schrieb Ralf Hildebrandt:
>> * Udo Rader <udo.rader
bestsolution.at>:
>> > Hi,
>> >
>> > as we are currently testing 2.3 I would like to know the rationale
>> > behind smtpd_sasl_authenticated_header.
>> >
>> > On one hand I find the flag useful for tracing purposes, but on the
>> > other hand I already see hordes of script kiddies/spammers harvesting
>> > the login names for brute force attacks.
>> >
>> > So what's the idea behind it?
>>
>> # postconf -d smtpd_sasl_authenticated_header
>> smtpd_sasl_authenticated_header = no
>>
>> The idea is to activate it if YOU think it's useful.
>
> yes, that is quite obvious, I am in control of any parameter, but I
> would like to know what's the idea behind it.
>
> If I was to setup a completely new, state of the art etc. server, (why)
> would I enable it?
As far as i remember there was some demand for this to distinguish
authenticated mail from other at a later stage (content filter ..).
Some sites may use it to assign every sent e-mail to a user without
scanning zhe logs.
But as said, if you have no idea what to do with leave it at default.
Regards
Andreas
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]