Differences

This shows you the differences between two versions of the page.

--- faq:spam:recover [2013/01/12 08:27]
dothebart spam recovery howto.
+++ faq:spam:recover [2013/01/12 08:55] (current)
dothebart
@@ Line 22: / Line 22: @@
 ======Clearing the Situation=====
-And now you're in the need for a way to delete a huge number of jobs from the Queue, right? Since webcit dynamicaly decides which representation to provide for a room, and the mailqueue is just another (hidden) room, you simply need to chose another representation by changing the **//view//** parameter in the URL in your browser from **11** to **1** and press enter. Now you've got the compfy mailbox view, you will get a better view of the situation. There are two sorts of messages in this room: those with regular subjects, and those with QMSG as subject. its always pairs of them; the QMSG with the queueing information, and the regular mail. We suspect that __NONE__
+And now you're in the need for a way to delete a huge number of jobs from the Queue, right? Since webcit dynamicaly decides which representation to provide for a room, and the mailqueue is just another (hidden) room, you simply need to chose another representation by changing the **//view//** parameter in the URL in your browser from **11** to **1** and press enter. Now you've got the compfy mailbox view, you will get a better view of the situation. There are two sorts of messages in this room: those with regular subjects, and those with QMSG as subject. its always pairs of them; the QMSG with the queueing information, and the regular mail. We assume that __NONE__ of the mails currently in the Queue will be sent. Select all of them and press <del> to move them into your personal trashbin. You can later check, whether there are mails from your users that they should send again. Please note that you should respect the privacy of your users.
+=====getting back to normal business=====
+Now that you
+  * removed the spam from your mailqueue
+  * identified & cleared possible infections on the client host
+you need to
+  * configure the new password on the client and tell the user his new password for the web login (or better let him choose a new one which mustn't be the old one)
+  * educate you user about possible attack vectors, and that his credentials are possibly burned, and he should change passwords on other accounts
+  * re-enable the inbound SMTP-Ports
+  * remove the outbound mailblock setting from your initscript
+  * restart citserver
+  * send a test mail!
+  * check whether you made it into some RBL, and clear the situation with them; else some remote hosts may reject mails from you as spam...