The mailing list for listmasters using Sympa

[Nick Holden <address@concealed>]

Hi Olivier,

Thanks for trying to help. I realise this may simply be that the list
type is one which is now supported differently in Sympa 6, but I am
currently stumped.

Here is an example of the moderation problem.

At 10:37 this morning the owner of one of the lists (called 'thought')
on my server sent a message to the list for distribution. As the list
requires moderation, sympa responded by sending back to him an email
which is titled "Message for list thought from email@emailaddress" - the
message begins "One new message for list thought from..." and includes
information about the message moderation queue and also a mailto link
for distributing or rejecting the message, using the keywords DISTRIBUTE
or REJECT.

Sympa also (as expected) sends him (as the originator of the message) an
email saying that his message has been forwarded to moderators.

He responds to the server that the message should be distributed.

Sympa then sends him a message advising him to send a message back to
the sympa server with the instruction "CONFIRM" and then the message ID.

The message ID is different between the sympa requests for DISTRIBUTE
and the one requesting CONFIRM, eg:


> To distribute the attached message in list thought:
> <mailto:address@concealed?subject=DISTRIBUTE%20thought%
20c5cbb26b128822235771b9e9b021e50d>
> Or send a message to address@concealed with the following
subject:
> DISTRIBUTE thought c5cbb26b128822235771b9e9b021e50d
>

... compared to ...


> To distribute the attached message in list thought, click on the URL:
>
> mailto:address@concealed?subject=CONFIRM%
20305d07584b15e913e94d51c83c5077ff
>
> Or send a message to address@concealed@ with the following
subject:
>
> CONFIRM 305d07584b15e913e94d51c83c5077ff


It seems as though sympa is trying to do two different things here, one
requiring the use of the CONFIRM keyword, and one using the DISTRIBUTE
keyword.

At receipt of the second request for confirmation, the list owner
abandoned the email process, and logged on using the web interface and
approved the message, which was then sent out in the usual way.

As you can imagine, this is confusing the list owner a lot!

So, is this some kind of bug? Or is it simply that the list is using the
wrong configuration?

Thanks,

Nick