On 27.03.08 11:34, NFN Smith wrote:
> I'm currently running spamassassin 3.2.1-1~bpo.1 from the Debian
> etch-backports branch (yes, I know that backports now has 3.2.4
> available, and I'll be upgrading shortly).
Just FYI:
Debian volatile archive has 3.2.3 and 3.2.4 was planned. Unlike backpor
Kris Deugau wrote:
NFN Smith wrote:
I'll check the MD archives for release notes, and see what's in the
Testing branch.
Just checked the changelog; there was a fix for this in MD 2.63 upstream:
Yep. I found that shortly after I posted.
Backporting the Debian package should be a matter
NFN Smith wrote:
The Debian release number of MIMEDefang I'm running is 2.57-5. It may
be that when Debian froze what went into etch, the current copy of MD
was the one with that glitch in it.
I'll check the MD archives for release notes, and see what's in the
Testing branch.
The fix went
NFN Smith wrote:
Hmmm... So this may be an issue with MIMEDefang.
The Debian release number of MIMEDefang I'm running is 2.57-5. It may
be that when Debian froze what went into etch, the current copy of MD
was the one with that glitch in it.
I'll check the MD archives for release notes, and
Jason Bertoch wrote:
I just discovered that over the last several weeks, I'm getting an
accumulation of hidden .spamassassin temporary files accumulating in
/tmp, that aren't getting deleted, and as a result, that volume is
filling up.
There was a version upgrade to SpamAssassin some time a
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of NFN Smith
Sent: Thursday, March 27, 2008 2:35 PM
To: users@spamassassin.apache.org
Subject: tmp file handling
>I'm currently running spamassassin 3.2.1-1~bpo.1 from the Debian
>etch-backports branc
I'm currently running spamassassin 3.2.1-1~bpo.1 from the Debian
etch-backports branch (yes, I know that backports now has 3.2.4
available, and I'll be upgrading shortly).
On my installation, I'm calling SpamAssassin from MIMEDefang, and so I'm
not running spamc and spamd .
I just discovered
