The mailing list for listmasters using Sympa

["Chris Andrews" <address@concealed>]

My Custom Condition script was the problem.  I am not sure why, I think it
was one of the DBI calls I had – may be the $sth->finish(); commands I had
in there.  I change the way I was doing the SQL calls and then removed the
$sth->finish(); command and now the FASTcgi errors have disappeared.

Also if any one read the code I attached they will notice that I was a moron
and I was using "$sth->dump_results();" to get the results of the SQL count
statement.  That is wrong, so here is the corrected and function code:
 
-<Old code>--

  my $sth = $dbh->prepare($query);

  unless ($sth->execute)
    {
    do_log('err',"checkaltemails.pm - Unable to execute SQL statement
$dbh->errstr");
    $sth->finish();
    return 0;
    }

  my $altemailsubscribedtothelistcount = $sth->dump_results();

  $sth->finish();

--<New code>--

my @rowvalue = $dbh->selectrow_array($query);

my $altemailsubscribedtothelistcount = $rowvalue[0];

Thanks for all the help.

---
 Chris Andrews

________________________________________
From: Chris Andrews [mailto:address@concealed] 
Sent: Friday, February 02, 2007 1:36 PM
To: Olivier Salaun - CRU
Cc: address@concealed
Subject: [sympa-users] RE: FCGI malformed headers errors

I do see this error in the sympa log:

Feb  2 10:42:17 gwar wwsympa[21124]: Language::gettext(Sympa could not set a
cookie for login.\n Your should configure your browser to accept cookies)

I can see the cookie set in my browser.

I did add some code to the Auth.pm.  I wrote a script that would find out
all the users email addresses and standardize all their subscriptions and
admin roles to one address. 

Line 61:
             my $updateemailstoLDAPmail =
&BCCustomCode::standardize_on_main_ldap($canonic); #### Added by Chris to
standarize email addresses

Line 110:

                my $updateemailstoLDAPmail =
&BCCustomCode::standardize_on_main_ldap($canonic); #### Added by Chris to
standarize email addresses

Basically after a successful LDAP authentication it will do SQL replacements
in the owner and subscriber tables.

I also wrote some custom conditions that would again look up all of a users
aliases and check them all against the list of subscribers for the list.  I
also moneyed with a bunch of the sceneri files.  I will rip all of that out
and see if the errors persist.

Now that I am doing more thinking about it, I am now able to cause the
problem at will be creating a new list using a list template that uses this
sceneri file for sending:

<send.subscribers_only>

title.gettext Sending and posting privledges are limited to subscribers
only.
is_subscriber([listname],[sender])             smtp,smime,md5    -> do_it
CustomCondition::checkaltemails([sender],[listname]) smtp,smime,md5    ->
do_it
is_editor([listname],[sender])                 smtp,smime,md5    -> do_it
is_owner([listname],[sender])                  smtp,smime,md5    -> do_it
is_listmaster([sender])        md5,smime  -> do_it
true()                         md5,smime  ->
reject(reason='subscribers_only')

Attached are the customcondition and the chunk of Sympa logs from when I
click on a list to when I get the “500 Internal Service” error.

---
 Chris Andrews
 Boston College
 Collaboration Team

Attachment: smime.p7s
Description: S/MIME cryptographic signature