On Wed, 8 Jun 2016, Mark London wrote:
Hi - We received an email with several large postscript attachments, and the
content type was "text/plain". This caused our spamassassin server to use
up 100% CPU, parsing the attachments as text. I temporarily disabled spam
scanning to allow the message to go through. How can I prevent this in the
future? I know about the time limit feature, but this doesn't prevent the
server from running 100% of the time, before the time limit is reached. Any
suggestions? Thanks. - Mark
Content-Transfer-Encoding: base64
Content-Type: text/plain;
name=OTBW_3D_256_ngtot100_de03_coll_dissip_1248.ps
Content-Disposition: attachment;
filename=OTBW_3D_256_ngtot100_de03_coll_dissip_1248.ps
Ouch. Please file a bug for that.
Do you have something that could catch text/plain + *.ps before SA get
handed the message (e.g. a regex milter or other test)?
--
John Hardin KA7OHZ http://www.impsec.org/~jhardin/
jhar...@impsec.org FALaholic #11174 pgpk -a jhar...@impsec.org
key: 0xB8732E79 -- 2D8C 34F4 6411 F507 136C AF76 D822 E6E6 B873 2E79
-----------------------------------------------------------------------
Rights can only ever be individual, which means that you cannot
gain a right by joining a mob, no matter how shiny the issued
badges are, or how many of your neighbors are part of it. -- Marko
-----------------------------------------------------------------------
169 days since the first successful real return to launch site (SpaceX)
