Re: mailSizeMax

Luiz Morte <[email protected]>
Newsgroups gmane.mail.qmail.ldap
Message-ID <[email protected]>
Philipp Kolloczek escreveu:
> Hi Luiz.
>
>   
>> I'm using the mailSizeMax attribute for block messages per user and
>> it's working great.
>> What I need: a custom message when one email is block for that limit.
>> Is this possible?
>> http://www.qmail-ldap.org/wiki/index.php/~control/quotawarning
>> quotawarning is for this message too?
>>     
>
> First, to whom this message should go? To the sender of the blocked 
> mail or the receiver?
>   
The sender.
> To have the sender informed you have to do nothing since the mail will
> bounce the sender will get the bounce with the information that the
> receivers side had not accepted that size.
>   
ok
> As far as I have it in mind qmail-ldap uses the quotawarning file to
> inform the receiver if a message could not get to him because of the
> quota limitations. Afaik as the mailSizeMax is a second line/type of quota
> the quotawarning will not be send to the receiver if one mail is
> over the mailsizeMax limit. Or named in another way mailSizeMax is
> "only" an individual limit of ~control/databytes. But remember the
> difference, with databytes a mail gets rejected by qmail-smtpd, with
> mailSizeMax the mail is rejected by qmail-lspawn as it is in the
> queue already. That's the reason why mailSizeMax can't be bigger
> than databytes.
>
> qmail-ldap by default will send the quotawarning if the mailbox
> is over 70% of one of the first line quotas ( size, number of messages )
> and one mail could not be delivered due to that this mail will over exceed
> the remaining limits.
>
> I guess you have to change the code in qmail-lspawn if you want the 
> receiver be noticed if a big mail hasn't come through.
>   

Thanks Philipp for the answer. My problem is: for my customer, he wants 
only his message as a return (not include the qmail message), but it´s 
working :)

Thanks any way.

Luiz.
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.