From: Graham Murray <graham@gmurray.org.uk>
To: ding@gnus.org
Subject: 8-bit spam broke mail spooling
Date: Fri, 14 Mar 2008 12:03:40 +0000 [thread overview]
Message-ID: <87ejadv7fn.fsf@newton.gmurray.org.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 550 bytes --]
I have identified the problem which I mentioned earlier which caused my
incoming mail to not be spooled. All was OK until a particular spam
message using 8-bit encoding. This mail was spooled but with a lot of
'garbage' at the end, but no messages after it were spooled to the nnml
mailboxes. I found 2 of these in the one Incoming file.
It is a bit worrying that a spam mail can stop gnus imported any more
mail from the same /var/spool/mail/user file.
I have tared and gzipped (to stop it breaking anyone else's gnus) the
first offending spam.
[-- Attachment #2: brokegnus.tar.gz --]
[-- Type: application/octet-stream, Size: 4191 bytes --]
reply other threads:[~2008-03-14 12:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87ejadv7fn.fsf@newton.gmurray.org.uk \
--to=graham@gmurray.org.uk \
--cc=ding@gnus.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).