Re: [qmailtoaster] Changing the max spam/clam scan message size

Hi Steve, I've been looking into this a little, and here's what I found at http://spamassassin.apache.org/full/3.1.x/doc/spamc.html. CONFIGURATION FILE The above command-line switches can also be loaded from a configuration file. The format of the file is similar to the SpamAssassin

Re: [qmailtoaster] vchkpw segfaults and spamdyke errors

> On Jun 6, 2016, at 11:58 PM, Eric wrote: > > http://thedjbway.b0llix.net/daemontools/softlimit.html > Well, I understand the basic concepts of softlimit. My question was really: is 1.28 gigabytes a reasonable

Re: [qmailtoaster] Changing the max spam/clam scan message size

> On Jun 7, 2016, at 12:03 PM, Eric wrote: > > Steve, > > Is this what you're looking for? > > /var/qmail/control/databytes > > Eric Hi Eric. I believe that’s the setting that controls the maximum message size that the server will accept for delivery. I’m looking

Re: [qmailtoaster] vchkpw segfaults and spamdyke errors

That's what I arbitrarily set mine to. You could jump up incrementally until you reach the right limit. You may not need that much. For that matter, I may not need that much. As I recall, I think I set it high to temporarily stop the errors and just forgot about it. The server has been running

Re: [qmailtoaster] vchkpw segfaults and spamdyke errors

> On Jun 7, 2016, at 11:38 AM, Eric wrote: > > And, "reasonable" is what the program, or library, needs. If 16000 KB is > not sufficient you must bump it up. Either qmail-smtp or libc or both are > trying to access memory not allocated to them, so, it must be

Re: [qmailtoaster] vchkpw segfaults and spamdyke errors

Am 07.06.2016 um 16:09 schrieb Steve Linberg: On Jun 6, 2016, at 11:58 PM, Eric > wrote: http://thedjbway.b0llix.net/daemontools/softlimit.html Well, I understand the basic concepts of softlimit. My question was really: is 1.28

Re: [qmailtoaster] vchkpw segfaults and spamdyke errors

And, "reasonable" is what the program, or library, needs. If 16000 KB is not sufficient you must bump it up. Either qmail-smtp or libc or both are trying to access memory not allocated to them, so, it must be increased. Admittedly, I'm not sure about all the details, but if you ran the

Re: [qmailtoaster] Changing the max spam/clam scan message size

Steve, Is this what you're looking for? /var/qmail/control/databytes Eric On 6/7/2016 9:58 AM, Steve Linberg wrote: Thanks in advance for all the assistance with the current toaster iteration, it’s monstrously helpful. The scanner won’t scan emails larger than 500k by default, and some

[qmailtoaster] Changing the max spam/clam scan message size

Thanks in advance for all the assistance with the current toaster iteration, it’s monstrously helpful. The scanner won’t scan emails larger than 500k by default, and some spammers have figured out that by getting attachments just over 500k, they can bypass scanning on systems left at the