Skip to Content.
Sympa Menu

en - Re: [sympa-users] Bad configuration file

Subject: The mailing list for listmasters using Sympa

List archive

Chronological Thread  
  • From: Olivier Salaun <address@concealed>
  • To: address@concealed
  • Cc: address@concealed
  • Subject: Re: [sympa-users] Bad configuration file
  • Date: Thu, 03 May 2001 15:43:18 +0200

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



Archive powered by MHonArc 2.6.19+.

Top of Page