The mailing list for listmasters using Sympa

[Steve Shipway <address@concealed>]

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
address@concealed


-----Original Message-----
From: address@concealed 
[mailto:address@concealed] On Behalf Of Paul Menzel
Sent: Thursday, 24 April 2014 10:35 a.m.
To: address@concealed
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

Attachment: smime.p7s
Description: S/MIME cryptographic signature