The mailing list for listmasters using Sympa

["O. Menkens" <address@concealed>]

Hi Matt, dear sympa-developers,

I guess, this kind of bugs, which appear only in case of errors, are 
very hard to debug for the sympa developers. Thus I think, it's a good 
idea if those bugs are reported. I don't know how to file bug reports to 
the sympa bug tracker, so I post it here.

The last few days I ran into a similar problem: We migrated our old 
solaris based sympa 5.3 server to sympa 6.1.22  on a Linux VM after some 
tests in the weeks before succeeded.
Now we realized, that some of the mails on some lists were archived, but 
not sent to the list. I (listmaster) received an error, that some 
messages could not be put into the bulkmailer with the hint, that I 
should check the logs.
The log file told me:
its-sympa-ext sympa[1438]: err Bulk::store() Unable to add message in 
bulkspool_table "INSERT INTO bulkspool_table (messagekey_bulkspool, 
messageid_bulkspool, message_bulkspool, lock_bulkspool, 
dkim_d_bulkspool, dkim_i_bulkspool, dkim_selector_bulkspool, 
dkim_privatekey_bulkspool) VALUES ('f740b42e890165cd3dc6fc9d24be56be', 
'<address@concealed>', 
'UmV0dXJuLVBhdGg6IDxoZWlrZS5ob3JzdG1hbm5AaWFpcy5mcmF1bmhvZmVyLmRlPgpYLU9yaWdp\nbmFsLVRvOiBsaW5rZWR0di1',
1, NULL, NULL, NULL, '')"; error :

Note the empty "error :" part at the end of the entry. I had to patch 
Bulk.pm (see below) to see the error string. With this patch it told me 
the error: "MySQL server has gone away"

Now google helped me to find the reason: I forgot to tune our database 
(http://www.sympa.org/manual/database#creating_a_sympa_database) and 
thus 'max_allowed_packet' was still on its default value of 1M. All 
mails, which were near 1M or bigger were not delivered.

Dear sympa-developers, please fix this error reporting :-)

Olaf M.

Here is the supposed patch:

--- bin-orig/Bulk.pm    2014-06-10 11:00:21.000000000 +0200
+++ bin/Bulk.pm 2014-08-21 12:36:12.000000000 +0200
@@ -552,15 +552,16 @@
                $messagekey, $msg_id, $msg, $dkim->{d}, $dkim->{i},
                $dkim->{selector}, $dkim->{private_key}
            )) {
+               my $errstring = $sth->errstr; # save the error, 
otherwise it will be modified later.
                do_log('err',
-                   'Unable to add message in bulkspool_table "%s"; 
error : %s',
+                   'Unable to add message in bulkspool_table "%s"; 
error : "%s"',
                    sprintf($statementtrace,
                        $dbh->quote($messagekey), $dbh->quote($msg_id),
                        $dbh->quote(substr($msg, 0, 100)),
                        $dbh->quote($dkim->{d}), $dbh->quote($dkim->{i}),
                        $dbh->quote($dkim->{selector}),
$dbh->quote(substr($dkim->{private_key}, 0, 30))
-                   ), $dbh->errstr
+                   ), $errstring
                );
                return undef;
            }


Am 20.08.2014 16:31, schrieb Matt Goebel:
> Hello,
>
>    I poked around but didn't see any mention of the following issue.
> I upgraded from sympa 6.1.17 to 6.1.22 for the dmarc changes and noticed
> that in a couple of places in List.pm that instead of using
>    do_log('err',
> the code references
>    do_log('error',
> which causes generic errors to be thrown, if those lines are reached, if
> say you haven't bothered to install the correct perl modules before
> testing the new version.
>
> Thanks,
> Matt Goebel