Message stuck in `sympa/auth` instead of `sympa/moderation`

[Paul Menzel]

Dear Sympa folks,


I am using Debian Wheezy with Sympa 6.1.11~dfsg-5.

A message of a non-subscriber was sent to a private list and for some
reason I did not get a moderation message and it is also not listed in
the moderation table in Sympa’s Web interface WWS.

Searching for that message, I found it in the directory
`/var/spool/sympa/auth/`.

Do you have an idea how it got into the directory `sympa/auth` instead
of `sympa/moderation`? How can these messages be controlled/managed? Did
I miss something in Sympa’s Web interface?


Thanks,

Paul

[Steve Shipway]

The auth queue is where messages go if your scenario specifies request_auth. This scenario action is more commonly used for subscription but can also be used for sending.

This is when the user is emailed back with a 'did you really send this message?' request, and they need to reply 'yes I did' with the accompanying MD5 key before it is released (after which it may go into the moderation queue or be distributed), confirming their identity.

You should check the send scenario you have on this list to make sure it is what you want; maybe you meant to have 'editorkey' instead? Compare the senari send.privateorpublickey and send.privateoreditorkey

I've created an add-in for Sympa that lets you view the auth queue, but we now no longer have any lists that use this.

Steve

Steve Shipway
s.shipway-1/***@public.gmane.org


-----Original Message-----
From: sympa-users-request-***@public.gmane.org [mailto:sympa-users-request-***@public.gmane.org] On Behalf Of Paul Menzel
Sent: Thursday, 24 April 2014 10:35 a.m.
To: sympa-users-***@public.gmane.org
Subject: [sympa-users] Message stuck in `sympa/auth` instead of `sympa/moderation`

Dear Sympa folks,


I am using Debian Wheezy with Sympa 6.1.11~dfsg-5.

A message of a non-subscriber was sent to a private list and for some reason I did not get a moderation message and it is also not listed in the moderation table in Sympa’s Web interface WWS.

Searching for that message, I found it in the directory `/var/spool/sympa/auth/`.

Do you have an idea how it got into the directory `sympa/auth` instead of `sympa/moderation`? How can these messages be controlled/managed? Did I miss something in Sympa’s Web interface?


Thanks,

Paul

[Paul Menzel]

Dear Steve,

Post by Steve Shipway
The auth queue is where messages go if your scenario specifies
request_auth. This scenario action is more commonly used for
subscription but can also be used for sending.
This is when the user is emailed back with a 'did you really send this
message?' request, and they need to reply 'yes I did' with the
accompanying MD5 key before it is released (after which it may go into
the moderation queue or be distributed), confirming their identity.
You should check the send scenario you have on this list to make sure
it is what you want; maybe you meant to have 'editorkey' instead?
Compare the senari send.privateorpublickey and
send.privateoreditorkey.

[
]

you hit the nail on the hat! That was exactly it! Thanks!

I thought the users would read the replies with instructions when they
do *not* use their mail, they subscribed with to the list. Guess I was
wrong.

Using Sympa’s Web interface, I changed the configuration from
`privateorpublickey` to `privateoreditorkey` now.

Changing that configuration option, there is an interesting conceptual
decision now for Sympa. Should it also notify the moderators about the
messages waiting for authentication and allow them to distribute these
messages?


Thanks again,

Paul