Tags: anti-virus, browser, error, linux, match, network, networking, pattern, platform, product, security, spamassassin, status, summary, uninitialized, value, version

New: Use of uninitialized value in pattern match (m//) ...error

On Networking » Networking

12,624 words with 22 Comments; publish: Sat, 10 May 2008 22:31:00 GMT; (450105.47, « »)

Summary: Use of uninitialized value in pattern match (m//)

error

Product: Spamassassin

Version: 3.1.0

Platform: PC

S/Version: Linux

Status: NEW

Severity: normal

Priority: P5

Component: spamassassin

AssignedTo: dev (AT) spamassassin (DOT) apache.org

ReportedBy: gour (AT) mail (DOT) inet.hr

Hi!

After upgrading to 3.1.0 on my Gentoo box, I experience the following error when

retrieving email with getmail:

Delivery error (command maildrop 13642 error (0, Use of uninitialized value in

pattern match (m//) at

/ line 119.

Use of uninitialized value in pattern match (m//) at

/ line 119.

Use of uninitialized value in pattern match (m//) at

/ line 119.))

msg 1/2 (1136 bytes), delivery error (command maildrop 13642 error (0, Use of

uninitialized value in pattern match (m//) at

/ line 119.

Use of uninitialized value in pattern match (m//) at

/ line 119.

Use of uninitialized value in pattern match (m//) at

/ line 119.))

It looks like SA fails on certain spam messages since after manually removing

offended message from the server, it run fine until stumbled upon another

'problematic message'.

Sincerely,

Gour

You are receiving this mail because:

You are the assignee for the bug, or are watching the assignee.

All Comments

Leave a comment...

  • 22 Comments
    • Additional Comments From gour (AT) mail (DOT) inet.hr 2005-11-15 09:14

      Created an attachment (id=3255)

      ()

      text of the message SA is failing on

      Hi!

      Here is the (one)message which caused SA to fail with the Use of uninitialized

      value in pattern match (m//)error and it is saved from the webmail interface

      on my ISP server.

      Sincerely,

      Gour

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #1; Sat, 10 May 2008 22:32:00 GMT
    • Additional Comments From mquinteiro (AT) cic-systems (DOT) com 2005-11-18 19:03

      Chech that you are running de good version off spamd, I had the same problem. if

      you run older version you will see in the log that you are running 3.1.0 but

      it's false. do

      whereis spamd

      and see if you have more than one instance and delete the older

      (In reply to comment #0)

      Hi!

      After upgrading to 3.1.0 on my Gentoo box, I experience the following error when

      retrieving email with getmail:

      Delivery error (command maildrop 13642 error (0, Use of uninitialized value in

      pattern match (m//) at

      / line 119.

      Use of uninitialized value in pattern match (m//) at

      / line 119.

      Use of uninitialized value in pattern match (m//) at

      / line 119.))

      msg 1/2 (1136 bytes), delivery error (command maildrop 13642 error (0, Use of

      uninitialized value in pattern match (m//) at

      / line 119.

      Use of uninitialized value in pattern match (m//) at

      / line 119.

      Use of uninitialized value in pattern match (m//) at

      / line 119.))

      It looks like SA fails on certain spam messages since after manually removing

      offended message from the server, it run fine until stumbled upon another

      'problematic message'.

      Sincerely,

      Gour

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #2; Sat, 10 May 2008 22:33:00 GMT
    • Additional Comments From apache.network.questionfor.info.a.leader-bg.com 2005-11-19 22:31

      I have the same problem after the SA upgrade on Gentoo. I have checked and I

      only have one version installed.

      The value that is not initialized is $self->{'type'}.

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #3; Sat, 10 May 2008 22:34:00 GMT
    • schulz (AT) adi (DOT) com changed:

      What |Removed |Added

      CC| |apache.network.questionfor.info.a.leader-bg.com

      Additional Comments From schulz (AT) adi (DOT) com 2005-11-21 15:38

      I have found that if I install a new version of SpamAssassin into the same

      location as an older version without first cleaning out the older version,

      the new version will fail with strange errors. There will be files from

      the older version that are not removed or replaced by the newer version.

      Try cleaning everything out and reinstalling.

      Is that attached email the whole email? It seems to be just headers.

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #4; Sat, 10 May 2008 22:35:00 GMT
    • felicity (AT) apache (DOT) org changed:

      What |Removed |Added

      Target Milestone|Undefined |3.1.5

      Additional Comments From felicity (AT) apache (DOT) org 2006-08-02 00:47

      does this error still occur with a newer 3.1.x? I seem to recall something

      about this problem, but don't remember the solution unfortunately. :(

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #5; Sat, 10 May 2008 22:36:00 GMT
    • Additional Comments From apache.network.questionfor.info.a.leader-bg.com 2006-08-02 05:44

      I run v. 3.1.3 and recently had the same problem again. I do not think it has

      been fixed in general, although might have been fixed for some types of

      messages.

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #6; Sat, 10 May 2008 22:37:00 GMT
    • Additional Comments From tocharian (AT) gentoo (DOT) org 2006-08-02 12:28

      Upgrading to 3.1.3 seems to have resolved the issue on my machine.

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #7; Sat, 10 May 2008 22:38:00 GMT
    • felicity (AT) apache (DOT) org changed:

      What |Removed |Added

      Target Milestone|3.1.5 |3.1.6

      Additional Comments From felicity (AT) apache (DOT) org 2006-08-13 00:33

      the message attached to this ticket shows no problems with 3.1.4 on my machine.

      can anyone else provide a sample message which shows the issue?

      also, it's not clear from the reports -- how are people calling SA when they see

      this problem? "spamassassin", "spamc" / "spamd", something else?

      thanks.

      btw: until there's more information, I'm moving the ticket to the next release's

      milestone.

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #8; Sat, 10 May 2008 22:39:00 GMT
    • Additional Comments From tocharian (AT) gentoo (DOT) org 2006-08-13 00:47

      The problem manifested itself on my machine when I was trying to learn spam with

      sa-learn. I no longer have any sample messages to provide however since the

      issue was fixed for me.

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #9; Sat, 10 May 2008 22:40:00 GMT
    • Additional Comments From apache.network.questionfor.info.a.leader-bg.com 2006-08-16 03:53

      I have been monitoring for errors since my last post and there are none. This

      problem is fixed for me. Thanks for the great work!

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #10; Sat, 10 May 2008 22:41:00 GMT
    • spamassassin (AT) dostech (DOT) ca changed:

      What |Removed |Added

      Status|NEW |RESLVED

      Resolution| |WRKSFRME

      Additional Comments From spamassassin (AT) dostech (DOT) ca 2006-09-28 18:34

      Works for me (SpamAssassin version 3.1.6-r438346, running on Perl version 5.8.8)

      and apparently everyone else, so closing.

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #11; Sat, 10 May 2008 22:42:00 GMT
    • duncf (AT) debian (DOT) org changed:

      What |Removed |Added

      Status|RESLVED |REPENED

      Resolution|WRKSFRME |

      Additional Comments From duncf (AT) debian (DOT) org 2006-11-01 21:59

      suggests that the problem is encountered in sa-learn, and provides a patch. I

      still can't reproduce it, but I see that there may be a problem here.

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #12; Sat, 10 May 2008 22:43:00 GMT
    • duncf (AT) debian (DOT) org changed:

      What |Removed |Added

      Target Milestone|3.1.6 |3.1.7

      Version|3.1.0 |SVN Trunk (Latest Devel

      | |Version)

      Additional Comments From duncf (AT) debian (DOT) org 2006-11-01 22:12

      duncf.network.questionfor.info.gold:~/svn/spamassassin$ svn commit

      Sending

      Transmitting file data .

      Committed revision 470240.

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #13; Sat, 10 May 2008 22:44:00 GMT
    • Additional Comments From duncf (AT) debian (DOT) org 2006-11-01 22:17

      Created an attachment (id=3740)

      ()

      patch for this problem

      Ready for review (do we need a 3.1.8 milestone?)

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #14; Sat, 10 May 2008 22:45:00 GMT
    • spamassassin (AT) dostech (DOT) ca changed:

      What |Removed |Added

      Target Milestone|3.1.7 |3.1.8

      Additional Comments From spamassassin (AT) dostech (DOT) ca 2006-11-01 22:44

      (In reply to comment #14)

      Ready for review (do we need a 3.1.8 milestone?)

      There already is one.

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #15; Sat, 10 May 2008 22:46:00 GMT
    • duncf (AT) debian (DOT) org changed:

      What |Removed |Added

      Summary|Use of uninitialized value |[review] Use of

      |in pattern match (m//) |uninitialized value in

      |error |pattern match (m//) error

      Status Whiteboard| |2 votes needed

      Additional Comments From duncf (AT) debian (DOT) org 2006-11-01 22:56

      Ha it's at the top of the list. I knew I should stop trying to work after 1:00

      Anyways, please review attachment 3740

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #16; Sat, 10 May 2008 22:47:00 GMT
    • Additional Comments From felicity (AT) apache (DOT) org 2006-11-02 07:59

      I'd rather know what the problem is than trying to patch around it. Anytime

      there's a Message::Node object, the type is set by the parse functions. undef

      in parse should be replaced by "text/plain", etc. So if type is undef, there's

      a bug somewhere that needs to be fixed.

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #17; Sat, 10 May 2008 22:48:00 GMT
    • felicity (AT) apache (DOT) org changed:

      What |Removed |Added

      Target Milestone|3.1.8 |3.2.0

      Additional Comments From felicity (AT) apache (DOT) org 2006-12-08 11:49

      I'm going to -1 this for previously stated reasons (fix the problem, don't

      bandaid around the problem) and punt to 3.2.

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #18; Sat, 10 May 2008 22:49:00 GMT
    • Additional Comments From spamassassin (AT) dostech (DOT) ca 2006-12-08 11:56

      This got committed to trunk BTW revision 470240.

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #19; Sat, 10 May 2008 22:50:00 GMT
    • Additional Comments From felicity (AT) apache (DOT) org 2006-12-08 12:02

      (In reply to comment #19)

      This got committed to trunk BTW revision 470240.

      thanks, I've reverted it out for now. :)

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #20; Sat, 10 May 2008 22:51:00 GMT
    • Additional Comments From felicity (AT) apache (DOT) org 2006-12-08 12:11

      Actually, the debian bug that caused the reopen here was also about 3.1.0.

      Prodding around, it looks like bug 4884 may be related, and a patch was applied

      for it in 3.1.2. person said they had the problem in 3.1.3, but no message

      was provided.

      So if someone sees this problem with a recent 3.1 version (3.1.7 is the current

      latest), please take the message causing the issue and attach it to this ticket.

      Thanks.

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #21; Sat, 10 May 2008 22:53:00 GMT
    • jm (AT) jmason (DOT) org changed:

      What |Removed |Added

      Status|REPENED |RESLVED

      Resolution| |WRKSFRME

      Additional Comments From jm (AT) jmason (DOT) org 2006-12-13 04:34

      since nobody has been able to provide a test case or reproduce the issue, I'm

      closing WRKSFRME until we see a sample message that demos the problem with

      current SVN. please reopen if you've got one, of course ;)

      You are receiving this mail because:

      You are the assignee for the bug, or are watching the assignee.

      #22; Sat, 10 May 2008 22:54:00 GMT