how_to:delete_outqueue_messages_directly_from_the_database
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
| how_to:delete_outqueue_messages_directly_from_the_database [2014/06/10 11:30] – external edit 127.0.0.1 | how_to:delete_outqueue_messages_directly_from_the_database [2018/06/28 09:33] – [To delete the messages] paul | ||
|---|---|---|---|
| Line 31: | Line 31: | ||
| If you know the IP address the unwanted messages came from, you could use:\\ | If you know the IP address the unwanted messages came from, you could use:\\ | ||
| - | '' | + | '' |
| If you know the authenticated sender the unwanted messages came from, you could use:\\ | If you know the authenticated sender the unwanted messages came from, you could use:\\ | ||
| - | '' | + | '' |
| etc. | etc. | ||
| Line 43: | Line 43: | ||
| CLUSTER VERBOSE outqueue.outrecipients;'' | CLUSTER VERBOSE outqueue.outrecipients;'' | ||
| + | ===Alternative method (quicker)=== | ||
| + | |||
| + | An alternate way to delete **ALL** the outqueue messages, and related information (but not settings or messages in mailboxes) is to stop VPOP3 first, and then use: | ||
| + | |||
| + | '' | ||
| + | |||
| + | This will delete all the relevant tables from the database, including their contents, so will be a lot quicker. When you restart VPOP3 it will recreate the deleted tables. You cannot selectively delete messages in this case. If you are using some sort of third party database replication, | ||
how_to/delete_outqueue_messages_directly_from_the_database.txt · Last modified: 2018/11/14 10:45 by 127.0.0.1
Page Tools
