Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
why does pegasus need two spam folders here?
14 views
Skip to first unread message
Ulrich G. Kliegis
Feb 16, 2012, 3:04:42 AM2/16/12
to
Hi all,
in order to overcome the invisibility of folders carrying names that
range further down in the alphabet, I use prefixes for many
foldernames that I want to keep in my immediate scope, like
#oldstuffmaillist, >satnews etc.
In the same manner, I renamed the standard 'junk and suspicious mail'
folder to '#junk...' and set that as the destination for sorted-out
spam in pegasus' spamholder setup. Fine, that worked for years now.
The false positives have reached a good low level, so, everything
looked fine. Having that folder in immediate reach facilitates the
finding of the odd false-positive very much.
The folders that don't carry prefixes here are more for the purpose of
collecting and archiving various maillist content, so, I don't cast an
eye there often but I know it is there. Also fine so far.
Yesterday, I glanced at those 'basement' folders again - and saw,
consciously for the first time, that there existed a non-#ed 'junk and
suspicious...' folder, well filled with much less spam than useful
content, even some bitterly missed mails which I thought had arrived
in nirvana a long time ago.
So, it took me some time to sort the contents to their defined
locations, always making sure that I declared those as non-spam.
Finally, the folder was almost empty, and I renamed it to 'old junk'.
A few minutes later, there was the 'junk and spuspicious...' folder
again, filling up slowly again.
All the time, the other '#junk...' folder exists on and fills
continuously with real spam.
There is no place in pegasus where I have defined the non-# folder as
a destination for spam. And the mysterious fact is that pegasus uses
both at its own decretion.
Pegasus 4.41 german version, Win XP. Pegasus serves as my one and only
mail client for all accounts that I use, so I have defined a couple of
identities - all of that working fine since 1998 here.
So, where is the catch? How can I teach Pegasus to use just and only
the junk folder that I define? Is there some definition in a
configuration file where I can change that behaviour?
Thanks for your empathy - and maybe some good advice!
Cheers,
Ulli.
in order to overcome the invisibility of folders carrying names that
range further down in the alphabet, I use prefixes for many
foldernames that I want to keep in my immediate scope, like
#oldstuffmaillist, >satnews etc.
In the same manner, I renamed the standard 'junk and suspicious mail'
folder to '#junk...' and set that as the destination for sorted-out
spam in pegasus' spamholder setup. Fine, that worked for years now.
The false positives have reached a good low level, so, everything
looked fine. Having that folder in immediate reach facilitates the
finding of the odd false-positive very much.
The folders that don't carry prefixes here are more for the purpose of
collecting and archiving various maillist content, so, I don't cast an
eye there often but I know it is there. Also fine so far.
Yesterday, I glanced at those 'basement' folders again - and saw,
consciously for the first time, that there existed a non-#ed 'junk and
suspicious...' folder, well filled with much less spam than useful
content, even some bitterly missed mails which I thought had arrived
in nirvana a long time ago.
So, it took me some time to sort the contents to their defined
locations, always making sure that I declared those as non-spam.
Finally, the folder was almost empty, and I renamed it to 'old junk'.
A few minutes later, there was the 'junk and spuspicious...' folder
again, filling up slowly again.
All the time, the other '#junk...' folder exists on and fills
continuously with real spam.
There is no place in pegasus where I have defined the non-# folder as
a destination for spam. And the mysterious fact is that pegasus uses
both at its own decretion.
Pegasus 4.41 german version, Win XP. Pegasus serves as my one and only
mail client for all accounts that I use, so I have defined a couple of
identities - all of that working fine since 1998 here.
So, where is the catch? How can I teach Pegasus to use just and only
the junk folder that I define? Is there some definition in a
configuration file where I can change that behaviour?
Thanks for your empathy - and maybe some good advice!
Cheers,
Ulli.
Michael in der Wiesche
Feb 16, 2012, 8:58:44 AM2/16/12
to
Am 16.02.2012, 09:04 Uhr, schrieb Ulrich G. Kliegis
<diesemailadressevonUlliistzwaret...@kliegis.de>:
> So, where is the catch? How can I teach Pegasus to use just and only
> the junk folder that I define? Is there some definition in a
> configuration file where I can change that behaviour?
Check your "Content Control" and "Spamhalter" settings for the folder they
use.
Michael
--
PGP Key ID (RSA 2048): 0xC45D831B
PGP Plugin for Pegasus Mail: <http://www.pmpgp.de/pmpgp/>
S/MIME Fingerprint: 26 5c a3 60 02 c6 e3 8a 75 70 d5 6a 67 ff d3 8d b0 b5
5e 5b
<diesemailadressevonUlliistzwaret...@kliegis.de>:
> So, where is the catch? How can I teach Pegasus to use just and only
> the junk folder that I define? Is there some definition in a
> configuration file where I can change that behaviour?
use.
Michael
--
PGP Key ID (RSA 2048): 0xC45D831B
PGP Plugin for Pegasus Mail: <http://www.pmpgp.de/pmpgp/>
S/MIME Fingerprint: 26 5c a3 60 02 c6 e3 8a 75 70 d5 6a 67 ff d3 8d b0 b5
5e 5b
Ulrich G. Kliegis
Feb 17, 2012, 3:05:00 AM2/17/12
to
On Thu, 16 Feb 2012 14:58:44 +0100, "Michael in der Wiesche"
<---idw.d...@t-online.de> wrote in
comp.mail.pegasus-mail.ms-windows:
>
>Check your "Content Control" and "Spamhalter" settings for the folder they
>use.
Michael,
thank you so much! Until yesterday, I was not aware of the 'content
control' relevance in this matter, actually, I had never cared about
it all the years - now I mended the destination folder there, and
everything seems fine now. Sheesh.
Case closed for the time being.
Cheers,
U.
<---idw.d...@t-online.de> wrote in
comp.mail.pegasus-mail.ms-windows:
>
>Check your "Content Control" and "Spamhalter" settings for the folder they
>use.
thank you so much! Until yesterday, I was not aware of the 'content
control' relevance in this matter, actually, I had never cared about
it all the years - now I mended the destination folder there, and
everything seems fine now. Sheesh.
Case closed for the time being.
Cheers,
U.
0 new messages