The mailing list for listmasters using Sympa

[Johann Spies <address@concealed>]

My normally reliable sympa server had a problem today: a long queue in
/var/spool/sympa/queue and it did not seem to do anything about the
queue.  I have tried restarting the process (/etc/init.d/sympa)
without it having any effect on the queue.  

In the end, I installed a security update of sympa (3.3.3-3woody2 on
Debian), copied the old configuration files back (the install script
did overwrite wwwsympa's configuration) and restarted the
process. Then it cleaned out the queue in a short time.

Now my questions:

1. What could have caused this behaviour of sympa not to complete it's
   queue?

2. What should an administrator like myself do in such a case?

3. This question is on another sympa topic.  Sympa never reports any
   bounced messages but a lot of messages like this sent to the
   administrator:

   From address@concealed Tue Feb 15 16:04:44 2005
   From: SYMPA <address@concealed>
   To: address@concealed
   Subject: Results of your commands
   Date: Tue, 15 Feb 2005 16:04:39 +0200

   > This is an automatically generated Delivery Status Notification.

   Command not understood: ignoring end of message.
   No command found in message

   My question: Why is this?  How do I get it to report bounces?

Regards
Johann

-- 
Johann Spies          Telefoon: 021-808 4036
Informasietegnologie, Universiteit van Stellenbosch

     "For by him were all things created, that are in  
      heaven, and that are in earth, visible and invisible, 
      whether they be thrones, or dominions, or  
      principalities, or powers; all things were created by 
      him, and for him."         Colossians 1:16