Hi,
I've noticed an interesting class of stuck inbound messages on my mail
queue. Each message has two subject lines, and is addresses to someone with
an Exim filter vacation message.
Each filter contains an autoreply that looks something like this:
# Exim filter <-- default autoreply created by atlas -->
# Check for spam
if personal
and $h_X-Bogosity does not begin "Spam"
then
mail
text "blah...\n"
once /var/exim/vacation/system/jd33/once
once_repeat 7d
log /var/exim/vacation/system/jd33/once.log
subject "Re: $h_subject"
endif
A relevant log entry looks like this:
2006-12-13 01:41:33 jd33 at sussex.ac.uk R=systemforward defer (-17): error
in filter data: \n not followed by space in "Re: SWiSHzine November
2006\nSWiSHzine November 2006" in mail command
And, relevant headers like this:
Subject: SWiSHzine November 2006
F From: SWiSHzone <swishzine@???>
R Reply-To: SWiSHzone <swishzine@???>
Errors-To: SWiSHzone <swishzine@???>
Date: Tue, 28 Nov 2006 09:25:34 -0500
Subject: SWiSHzine November 2006
List-Unsubscribe: <
https://my.swishzone.com/users/maillist.asp>
List-Subscribe: <
https://my.swishzone.com/users/maillist.asp>
List-Help: <
https://my.swishzone.com/users/maillist.asp>
Now, as it happens the bulk of this stuff is spam (but hey, it's email, so
the bulk of it would be spam).
Anyway, I guess this is a bug in mail feature of Exim filters - if the
constructed Subject header contains new lines, then they should be followed
by spaces, no?
--
Ian Eiloart
IT Services, University of Sussex
