Skip to Content.
Sympa Menu

en - [sympa-users] Re: Sympa choking on non-encoded header data?

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Liam Kirsher <address@concealed>
  • To: address@concealed
  • Subject: [sympa-users] Re: Sympa choking on non-encoded header data?
  • Date: Tue, 19 Jun 2007 13:41:39 -0700

Hi --

I didn't see any responses to my message... should I report this as a bug?

Liam

Liam Kirsher wrote:
> Hi --
>
> Sympa (5.3b4) dumped again, but this time I think I found a little more
> information, that may help discover the problem.
>
> The status when the problem was reported was that one sympa.pl process
> was running and the other had died.
>
> I stopped and restarted sympa, and initially there were two sympa.pl
> processes (as expected) but then one of them died again, and the messages
> in ~sympa/spool/msg were still just sitting there not being processed.
> At this point some additional files showed up in the ~sympa/spool/tmp
> directory, and one of them also had the line quoted below about
> "Unrecognized line... Message.pm line 89".
>
> I removed a bunch of spam messages from the msg directory and was able
> to restart sympa normally, and now it's running. So, I think that one
> of the messages was causing a problem.
>
> You can check out the files here: http://www.numenet.com/sympa-err
>
> In ~sympa/spool/tmp I found three files:
> 13885.stderr
> 13886.stderr
> sympa_dump.1181582290.23287
>
> The last line of 13885.stderr is:
>
>> Unrecognised line: address@concealed> at /home/sympa/bin/Message.pm
>> line 89
>>
> If you look at that msg, you can see that Amavis added
>
>> BAD HEADER Non-encoded 8-bit data
>>
> And I suspect that the non-encoded From line may be causing the problem in
> sympa.
>
> The dump file seems to have been created after wwwsympa received some
> strange input. I found this in /var/log/messages and /var/log/sympa:
>
> Jun 11 10:17:24 pythagoras wwsympa[23287]: [robot lists.mpjc.org]
> [client 65.88.178.10] [rss] do_lists(,)
> Jun 11 10:17:32 pythagoras wwsympa[23284]: [robot lists.mpjc.org]
> [client 65.88.178.10] do_lists(,)
> Jun 11 10:17:57 pythagoras wwsympa[23286]: [robot lists.mpjc.org]
> [client 65.88.178.10] [list bulletin] do_subscribe()
> Jun 11 10:17:57 pythagoras wwsympa[23286]: [robot lists.mpjc.org]
> [client 65.88.178.10] [list bulletin] do_subrequest()
> Jun 11 10:17:57 pythagoras wwsympa[23286]: Invalid email address ''
> Jun 11 10:18:10 pythagoras wwsympa[23287]: [robot lists.mpjc.org]
> [client 65.88.178.10] get_parameters: syntax error for parameter list
> value 'http:��lists..
> mpjc.org�wws�subrequest�bulletin' not conform to regexp
> /^[\w\-\.\+]*$/ ;
> dumped vars in /home/sympa/spool/tmp/sympa_dump.1181582290.23287
> Jun 11 10:18:10 pythagoras wwsympa[23287]: [robot lists.mpjc.org]
> [client 65.88.178.10] do_subrequest()
> Jun 11 10:18:10 pythagoras wwsympa[23287]: [robot lists.mpjc.org]
> [client 65.88.178.10] do_subrequest: no list
> Jun 11 10:18:21 pythagoras wwsympa[23284]: [robot lists.mpjc.org]
> [client 65.88.178.10] [list bulletin] do_rss_request
>
> ------------------------
>
> So -- this may actually be two problems? Any help would be appreciated.
>
> There is quite a bit of spam arriving. I discard the worst, but to avoid
> false positives I have to allow a somewhat lenient spam policy. I think
> there
> is a way to have sympa discard spam (that is, as identified by SpamAssassin
> headers). Can someone remind me what it is?
>
> Best,
> Liam
>
>
>
>
>
>
>

--
Liam Kirsher
PGP: http://liam.numenet.com/pgp/




Archive powered by MHonArc 2.6.19+.

Top of Page