Day '34' out of range 1..31 at /usr/share/perl5/Mail/SpamAssassin/Util.pm line 446

[Christian Holtje]

Binary package hint: spamassassin

I keep getting messages in my logs at the end of the month like this:
Day '34' out of range 1..31 at /usr/share/perl5/Mail/SpamAssassin/Util.pm line 446

I know this is due to spammers not understanding elementary date math, but Spamassassin should handle it better.

This looks like it was fixed in SpamAssassin 3.2.0 or greater.

See: http://issues.apache.org/SpamAssassin/show_bug.cgi?id=5361

Ciao!

[Scott Kitterman (kitterman)]

What version are you running. That was fixed in 3.1.5 and so should not affect Feisty (which has 3.1.7).

[Christian Holtje (docwhat)]

Package: spamassassin
Version: 3.1.7-2ubuntu1
Filename: pool/universe/s/spamassassin/spamassassin_3.1.7-2ubuntu1_all.deb
Size: 974198
MD5sum: d41f0e958e56d1259566b1bb8e660bb6
SHA1: ea8dbfe07f6d1f2764ceec6b4b148eee9e02f4b1
SHA256: 29abe5a8838a3f636010bbcfda24481857390a603091ce5bca035752c7c15c4b

Package: spamc
Version: 3.1.7-2ubuntu1
Filename: pool/universe/s/spamassassin/spamc_3.1.7-2ubuntu1_i386.deb
Size: 75272
MD5sum: d8e4cefa71dc5fe2c8bf1f46eedcedd4
SHA1: 528b8249b60177a1dbeeb8c8be6d8e4707ffb15b
SHA256: 065f90cec4111edfb529fb3206a0840aac24043d679031a5efaa189a45e6b831

I'm still getting these messages (the number has incremented from 34 to 35):
Day '35' out of range 1..31 at /usr/share/perl5/Mail/SpamAssassin/Util.pm line 446

I double checked and I only have one version installed (no copy in /usr/local, no copy in any user's home dir, etc.).

I'm doing a reinstall of spamassassin and spamc to verify that I have the correct version....
Nope, still a problem.

In theory, there is no difference between theory and practice. In practice, however.... ^_^

Ciao!

[Christian Holtje (docwhat)]

5361 was marked a duplicate. Pointing it at the original.

[Scott Kitterman (kitterman)]

Spamassassin 3.2.1 is available in feisty-backports. You might try it and see if the problem persists.

[Christian Holtje (docwhat)]

I seem to have no problems with 3.2.1 from back ports. I haven't seen a single peep, whereas before it was giving me an error every few minutes (in time with the spam... :-).

Ciao!

[Scott Kitterman (kitterman)]

Then it sounds to me like the patch was just mis-tagged in the SpamAssassin bugzilla as to which release it was applied to. I'm marking this fix released based on the disappearance of the problem with the newer version. Please re-open if you find the problem recurring.

[topher (xophervt)]

I am still seeing this on Dapper (LTS).
The latest backport of SA is 3.1.3.
Is there an update in the queue?

Thx

[Scott Kitterman (kitterman)]

None has been requested. Dapper lacks some of the dependencies for 3.2,
but I think a 3.1.7 backport would be reasonable if it were
requested/tested.