l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2004 Jun 10 17:20

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
[vox-tech] postfix question: content inspection for junk elimination
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[vox-tech] postfix question: content inspection for junk elimination

I am using Postfix 2.0.16 to send and receive mail on wotan.hajhouse.org for
my several domains. I am using the content inspection mechanism
(header_checks, body_checks, etc) to identify spam and other junk messages
by regexps (PCRE) in order to reject such messages at SMTP time. This is
nice because it is very fast and avoids the extra CPU time and memory that
an external filter would require. I have some issues:

1. HTML-format messages

	I want to reject all messages that contain only a text/html part and not
	a text/plain alternative. That means that either there is a single
	attachment of type text/html or that there is a multipart/alternative
	attachment containing a single text/html subpart. In my experience, all
	such messages are junk.

	On the other hand, legitimate messages from clueless people who send in
	HTML format invariably consist of a multipart/alternative wrapper
	containing a text/html part and a text/plain part, the latter being the
	former minus HTML formatting cruft.

	Were it up to me, I would reject all HTML messages, including the
	legitimate ones above, since I consider HTML mail an abomination and a
	waste of bandwidth. But some people actually like lots of busy formatting
	in their e-mail and some do not know how to turn it off. Hardly anyone
	reads the informative bounce messages that wotan.hajhouse.org produces.

	So I want to reject the first class of messages described above, but
	accept the second, possibly returning a non-fatal warning to the sender.
	Any ideas?

2. Zip attachments

	I am also rejecting all zip files. This has so far been fine, since all
	zip files received for the last few months have been viruses. But surely
	there is a better way, other than blocking based on known virus
	signatures. Perhaps accepting zipfiles from people who have previously
	send us mail, but not from random senders. But how to do that? Can
	patterns be made conditional on the sender's address using buildin
	postfix mechanisms or do I need an external scanner like SpamAssassin?

	I usually ask people to send tarballs instead of zipfiles. Can popular
	DOS compression programs create tarballs?

Henry House
Please don't sent me HTML mail! My mail system will reject it.
The unintelligible text that may follow is a digital signature.
See <http://hajhouse.org/pgp> to find out how to use it.
My OpenPGP key: <http://hajhouse.org/hajhouse.asc>.

Attachment: signature.asc
Description: Digital signature

vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
EDGE Tech Corp.
For donating some give-aways for our meetings.