The mailing list for listmasters using Sympa

[Andreas Speck <address@concealed>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi there,
  We are running sympa-5.3.4 on Debian testing (the debian packages),
and recently we got the problem that sympa is rejecting messages which
should not be rejected.

1. A user tried to send an email to a list called africaworkinggroup.
This list is open for posting from subscribers, and the user is
subscribed to the list.

The scenario for the list is the send.private one:

title.gettext restricted to subscribers

match([header->X-Spam-Status],/Yes/)  smtp,smime,md5 -> reject,quiet
is_subscriber([listname],[sender])             smtp,smime,md5    -> do_it
is_editor([listname],[sender])                 smtp,smime,md5    -> do_it
is_owner([listname],[sender])                  smtp,smime,md5    -> do_it
true()               smtp,md5,smime  -> reject,quiet

(path: /etc/sympa/scenari/send.private)

In the log files, I can see the following:

Jun 19 11:50:34 lists sympa[25473]: main::DoFile()
Processing
/address@concealed ;
sender: "Jan Van Criekinge" <address@concealed>  ;
message-id: <015e01c8d1fa$3d1ba430$4001a8c0@DJ4N811J>

Jun 19 11:50:35 lists sympa[25473]: main::DoMessage() Message for
africaworkinggroup from address@concealed rejected()
because sender not allowed


However, this sender is a subscriber. The only problem I could see is
that at the time of sending the user was marked as bouncing.


2. I had a similar problem on another list, informe-oc. This list is set
to be a newsletter, and consequently the scenario is send.newsletter:

title.gettext Newsletter, restricted to moderators

match([header->X-Spam-Status],/Yes/)  smtp,smime,md5 -> reject,quiet
is_editor([listname],[sender])                 smtp,smime,md5     -> do_it
true()                                         smtp,smime,md5     -> 
reject,quiet

The sender address@concealed is set to be one of the owners,
and one of the moderators of the list. However, in the logs I could see:

Jun 18 13:27:42 lists sympa[3392]: main::DoFile() Processing
/address@concealed ;
sender: CO-Update <address@concealed>  ; message-id:
<address@concealed>
Jun 18 13:27:43 lists sympa[3392]: main::DoMessage() Message for
informe-oc from address@concealed rejected() because sender
not allowed


As I had to get the message out, I briefly set the scenario to
send.private (and then it worked), and then the message was accepted.
However, I forgot to reset it to send.newsletter, so that someone else
managed to send a message to the list too, who wasn't supposed to be
able to do so.

- From the logs it seems that co-update-editor might also have been set as
bouncing at the time I sent the message (I didn't check that back then):

lists:/home/andreas# tail -2000 /var/log/sympa.log | grep co-update-editor
Jun 19 09:39:37 lists task_manager[25481]: main::expire_bounce() expire
bounces for subscriber address@concealed of list informe-oc
(last distribution 19 Jun 2008, last bounce 21 Apr 2008 )

Could this be the problem? Do the scenarios imply that a bouncing list
member (who might have bounced just once, i.e. due to a full mailbox)
cannot send a message? I think that would be problematic.


Otherwise, I have no explanation for this problem.

Any clues?

Thanks,
Andreas

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkhczwoACgkQvoa8wUUHIBGREQCeIXuBY4Zl4RI442vfZ/Jj2QxH
B8YAoLCYXtChCS6BaUGB1ng4iY5vaIQN
=/g4E
-----END PGP SIGNATURE-----