Re: SENDERCHECK patch

  Hello Hugo, hello all

do you/someone else still use this patch? I'm using it for quite a while 
and in general, I like it, because before we received lots of Spam with 
envsender=recipient. So I configured sendercheck="auth" for every 
connection, because my "locals" have to authenticate in any case. But 
today I observed a problem, which IMO I cannot circumvent easily, but 
maybe someone else has a good idea.

Think of (Mail-) DomainA, located on my qmail-ldap server. Additionally 
there is (Mail-)DomainB, located somewhere else. DomainB has a simple 
distribution list (forward to more than one recipient), containing at 
least one mailadress of DomainA........
Now my customer from DomainA sends a mail towards the distribution list 
within DomainB, the Mail server of DomainB splits the recipients and 
sends back a mail with envelope sender from DomainA, towards a recipient 
of DomainA. My qmail-ldap server now denies acceptance with "Auth 
needed"....

I think this is legitimate - and my only chance is to deactivate 
SENDERCHECK="AUTH".
Any thoughts?

Thanks,
Robert



Am 27.06.2009 21:24, schrieb Hugo Monteiro:
> Hello all,
>
> I've written a small patch that extends the SENDERCHECK facility. It 
> allows the definition of SENDERCHECK="AUTH", besides the already 
> existent STRICT and LOOSE.
>
> The behaviour of SENDERCHECK is the same, except that when set to 
> "AUTH", if the sender address is local, and is verified in LDAP, the 
> server will require that the sender is authenticated.
>
> I have written this patch because of the increasing number of spambots 
> forging valid local addresses. Many times using the same sender as the 
> recipient.
>
> Maybe this would be a good idea incorporate in a future qmail-ldap 
> release..?
>
> Best regards,
>
> Hugo Monteiro.
>