On 10/30/2015 10:04 AM, Jeroen Scheerder wrote: > L.S., > > I ran into a little something. I have separated my main smtp service > (tcp/25) and smtps/submission services (tcp/465, tcp/587). > The smtps/submission services have a few extra virtual aliases, but they also > (don't ask) add a header: > > % cat on2it-header-checks > /^Received:/i PREPEND X-ON2IT-Claimer: This message may contain > confidential or privileged information. > > (Since you probably do wonder > anyway, this is how I preemptively struck out > against having to insert > foolish disclaimers into message bodies.) > > My message_size_limit is set: > > message_size_limit = 10240000 > > The main smtp as well as the smtps/submission services report that size after > the EHLO: > > 250-SIZE 10240000 > > Sane clients respect that size limit and refuse to send messages exceeding > it. But since the message size will grow (by 82 bytes) after prepending a > header, it is entirely possible that this will push a message slightly below > the limit over the edge. Such a message will get sent by the client, only to > receive a "5.3.4 Error: message file too big" (and the cleanup process logs > "queue file size limit exceeded"). > > This has two disadvantageous consequences: > > a) Clients send (large) messages in vain > b) Some clients handle the SMTP error poorly (we've seen this mainly > for Android phones) > > This got me thinking. Would it be possible to have > > message_size_limit = 10240000 > > but have my smtps/submission services announce slightly less: > > 250-SIZE 10239918
I think you can override the message size limit for the submission port in master.cf: submission inet n - - - - smtpd -o message_size_limit=10239918 Kind regards, Martijn Brinkers -- CipherMail email encryption Open source email encryption gateway with support for S/MIME, OpenPGP and PDF messaging. https://www.ciphermail.com Twitter: http://twitter.com/CipherMail
