On Tue, May 16, 2006 at 05:36:45PM -0000, [EMAIL PROTECTED] wrote:
> trivial fix: inhibit 'undefined value' warnings
> 
> --- spamassassin/trunk/lib/Mail/SpamAssassin/Message.pm (original)
> +++ spamassassin/trunk/lib/Mail/SpamAssassin/Message.pm Tue May 16 10:36:45 
> 2006
> @@ -145,7 +145,9 @@
>    }
>  
>    # Pull off mbox and mbx separators
> -  if ( $message[0] =~ /^From\s/ ) {
> +  if (!defined $message[0]) {
> +    # no separator, there's no message ;)
> +  } elsif ($message[0] =~ /^From\s/) {
>      # mbox formated mailbox
>      $self->{'mbox_sep'} = shift @message;
>    } elsif ($message[0] =~ MBX_SEPARATOR) {
> 

When can this happen, now that the "null message causes undefined value
warnings" bug (4884) was fixed?  @message should always have at least
1 entry in it now.

-- 
Randomly Generated Tagline:
"Remember that the next time when you're using virgin RAM, as opposed
 to RAM that's been touched." - Pat Beirnes

Attachment: pgpobrYbRcu0K.pgp
Description: PGP signature

Reply via email to