[quote user="Paolo_DF"]
Hi all.
I started using Mercury in a new way (to me, at least).
This is what I did:
1. retrieve messages with Mercury from email account 1@...
2. use popfile daemon in order to classify messages
3. deliver to local user 1
4. apply filter in order to forward only non-spam messages to email address 2@...
This way, I use my old email address 1@... because everyone knows it, but receive all my mail on email address 2@... because it is a fresh address.
Now, of course, there is this local user 1 mailbox that *never* get any access, so it starts filling up.
And here is the question: how may I delete messages in local mailbox 1 since I never access it and only use it as a buffer?
Thank you all for your reply.
[/quote]
If you are never going to look at these then why not simply use a Mercury/32 filter to delete all of the messages marked spam by POPfileD before they are delivered to the user. This may require yuo to leave the local user blank in the MercuryD setup and alias this mail to user@local.domain so that core have a chance to filter them.
Personally though, I use the MOVE action to move all of these messages
to a spam user account so I can check for false positives.
[quote user="Paolo_DF"]<p>Hi all.</p><p>I started using Mercury in a new way (to me, at least).</p><p>This is what I did:</p><p>1. retrieve messages with Mercury from email account 1@...</p><p>2. use popfile daemon in order to classify messages</p><p>3. deliver to local user 1</p><p>4. apply filter in order to forward only non-spam messages to email address 2@...</p><p>This way, I use my old email address 1@... because everyone knows it, but receive all my mail on email address 2@... because it is a fresh address.</p><p>&nbsp;</p><p>Now, of course, there is this local user 1 mailbox that *never* get any access, so it starts filling up.</p><p>&nbsp;</p><p>And here is the question: how may I delete messages in local mailbox 1 since I never access it and only use it as a buffer?</p><p>&nbsp;</p><p>Thank you all for your reply.&nbsp;</p><p>[/quote]</p><p>&nbsp;</p><p>If you are never going to look at these then why not simply use a Mercury/32 filter to delete all of the messages marked&nbsp; spam by POPfileD before they are delivered to the user.&nbsp; This may require yuo to leave the local user blank in the MercuryD setup and alias this mail to user@local.domain so that core have a chance to filter them.</p><p>&nbsp;Personally though, I use the MOVE action to move all of these messages
to a spam user account so I can check for false positives.
&nbsp;</p><p>&nbsp;</p><p>&nbsp;</p>