Pegasus Mail & Mercury

Hi all,

After happily (well, 98% of the time :)) using Pegasus for my e-mail over POP3 connection for 10+ years, I am now forced into some major change. My university decided to move all mail to M$ Exchange 2010 without POP3 support - not that POP3 is not available under Exchange, but they figured it was "outdated" and decided to save money on it. Alas, I am forced to use IMAP - thankfully it is still supported. At first I thought it was in a way a positive development - after all I can get all my folders (hundreds of them, 1Gb+ space) be stored on the central and regularly backed up server, while being able to access them from anywhere I am. I was able to establish IMAP connection without much trouble and it seems working, but then, after some experimentation and perusing this forum, I realised to my disappointment that many of Pegasus strongest features, like Spamhalter, autofiltering, etc. do not work with IMAP inbox - got excited about these since I haven't upgraded since 2004, but then what a bummer!

Long story short, being new to filtering, I am wondering if something like this may still work:

1. Create folder-on-open filtering rule for IMAP inbox forcing all messages from there to be moved to local inbox. I figure this will require extra click to open IMAP inbox, but I can live with that.

2. Hopefully such move will invoke all Pegasus "normal" processing - Global Whitelist, Spamhalter, Content Control, Autofiltering, etc. - but will it? That's the main question!

3. Move read messages from local inbox back to relevant IMAP folders as needed.

This of course will result in lots of back and forth net traffic, but these days with connections getting faster and faster it shouldn't be an issue anymore.

As I understand, all this IMAP "deficiency" stems from the fact that Pegasus cannot "sense" when new mail appears in IMAP inbox, since incoming transport is now handled by remote server, not Pegasus itself. However I see that Pegasus is able to periodically poll that inbox and I am puzzled as to why such poll cannot trigger some scenario similar to one described above?

Any thoughts on this are greatly appreciated!

BoarX:

I realised to my disappointment that many of Pegasus strongest features, like Spamhalter, autofiltering, etc. do not work with IMAP inbox - got excited about these since I haven't upgraded since 2004, but then what a bummer!

Your university has central IMAP-Server but no central SPAM-control? Strange!

1. Create folder-on-open filtering rule for IMAP inbox forcing all messages from there to be moved to local inbox. I figure this will require extra click to open IMAP inbox, but I can live with that.

Create a "General filtering rule" (have a look for correct menue ... I translate from german Pegasus - sorry). Maybe you call it "IMAP-INBOX". Create a rule on attributes NOT read (choose "read mail" and "NOT" at the buttom). Because of last step you may not want to copy all mails to local inbox.

2. Hopefully such move will invoke all Pegasus "normal" processing - Global Whitelist, Spamhalter, Content Control, Autofiltering, etc. - but will it? That's the main question!

Should do!

3. Move read messages from local inbox back to relevant IMAP folders as needed.

Due to one the porcessed files should not be copied to IMAP inbox or they should be marked read. Another way may be to set a color in step one to indicate files to be already processed.

bye   Olaf

Hi Olaf!

Thanks so much for your reply and indeed it worked!

FJR:

BoarX:

I realised to my disappointment that many of Pegasus strongest features, like Spamhalter, autofiltering, etc. do not work with IMAP inbox - got excited about these since I haven't upgraded since 2004, but then what a bummer!

Your university has central IMAP-Server but no central SPAM-control? Strange!

Well, they do have central SPAM-control, but since substantial portion of my incoming e-mails are in Cyrillic, rather than English/Latin, that central SPAM-control tends to generate false positives, so I prefer to do filtering with Pegasus, when everything is under my own control - and so far it worked pretty well with just Content Control and now there is also Spamhalter.

FJR:

 

BoarX:

1. Create folder-on-open filtering rule for IMAP inbox forcing all messages from there to be moved to local inbox. I figure this will require extra click to open IMAP inbox, but I can live with that.

Create a "General filtering rule" (have a look for correct menue ... I translate from german Pegasus - sorry). Maybe you call it "IMAP-INBOX". Create a rule on attributes NOT read (choose "read mail" and "NOT" at the buttom). Because of last step you may not want to copy all mails to local inbox.

Why, in fact I don't intend to read any messages in IMAP inbox, even when I see them there, thus all the messages that ever get there are going to be unread and hence get filtered. Thus the rule I created applies unconditionally to all messages in IMAP inbox. Even if they eventually end up in some IMAP folder, I don't mind extra net traffic. That way I let my SPAM-filter do its work before I even try to open anything.

FJR:

 

BoarX:

2. Hopefully such move will invoke all Pegasus "normal" processing - Global Whitelist, Spamhalter, Content Control, Autofiltering, etc. - but will it? That's the main question!

Should do!

Yay, it does!

FJR:

 

BoarX:

3. Move read messages from local inbox back to relevant IMAP folders as needed.

Due to one the porcessed files should not be copied to IMAP inbox or they should be marked read. Another way may be to set a color in step one to indicate files to be already processed.

Of course it doesn't make sense to copy anything back into IMAP inbox, as the result is going to be an endless filtering loop. I usually copy messages to folders manually, but may try autofiltering in future.

All in all, the method does work, just requires two extra clicks of a mouse: first on IMAP inbox to initiate associated filter and second on local inbox to initiate SPAM-filter, content control, white//blacklists, etc. There are some issues with Pegasus IMAP functionality when connected to Exchange, but I am going to report them separately.

Have fun everyone!