The mailing list for listmasters using Sympa

["Nicolas Brouard" <address@concealed>]

OK, updating the scenario with old-style moderation is a good idea.

If, for backward compatibility, you need to keep the old term of "editor", I
suggest you to change the label from "moderated with key md5 (editokey)" to,
simply, "moderated (editorkey)" because nobody knows what md5 means. Then
change the label "moderated (editor)" to "moderated old fashion (editor)",
or something like that. A native english speaking contributor could improve
the label. Idem for other languages.

And in any case, the garbage message output from the actual "editor" seting
is horrible. I remarked that in version 3.1.1 it does not work as good as
you said.

 The moderator does not receive an original copy of the message. He receives
a single message with a clear Subject: Article to be approved" but a garbage
body.

If somebody could confirm my trials, it would mean that nobody in the world
is actually using the old "editor" fashion.

I suggest that even if a garbage is sent in the warning message, something
like "Ask the owner of the list to update the configuration parameter of
your list from "send editor" to "send editorkey" will be included in the
body. This code could be inserted in an "else" statement after the "if md5"
in List.pm described earlier.

I also suggest to suppress any reference to md5, to simplify owner's life.

Nicolas Brouard
Institut national d'études démographiques
mailto:address@concealed

-----Message d'origine-----
De : address@concealed [mailto:address@concealed]De la part de Olivier Salaun
Envoyé : jeudi 3 mai 2001 15:43
À : address@concealed
Cc : address@concealed
Objet : Re: [sympa-users] Bad configuration file


Hi,

send.editor is Sympa's old style of moderation :
        1/ Sympa sends to the moderator
                * an original copy of the message
                * a copy tagged as "Article to be approved"
        2/ The second  copy of the message is just meant to
           catch the moderator's eyes.
        3/ The redistributes the message to the list. Sympa knows
          check the mesages's X-Sender header field.

This is not used anymore and the scenario should be renamed "old-style
moderation".

'md5' in List::send_to_editor() means that Sympa uses moderation keys to
distribute/reject messages. It's much more efficient and it does a
better
message encapsulation job.

I don't think making old-style moderation MIME-compliant is worth.

Nicolas Brouard wrote:

> When I set a list to the standard "send editor", the message received
> by the moderator is garbage. If set to "privateoreditorkey" it is OK
> (the moderator can read the message, accept or reject).
>
> I tried to enter the code and discovered that within List.pm the
> process skips some lines of code if the method is not equal to md5
> (there is no print MIME-Version, boundary and dialog to ask the
> moderator). There is probably something wrong on my local
> configuration, but what? Any ideas?
> [...]
>   what happens if not md5: garbage for the moderator?
> return $modkey;
>
> I am not familiar of what md5 is (I thought it was a simple checksum)
> and why the incoming message are not detected as md5 message in case
> of "send editor".



--
Olivier Salaün
Comité Réseau des Universités