Below process can help you convert format.
Exporting Emails from Pegasus:
Open your Pegasus email client.
Locate the option for exporting or backing up emails. This can often be found in the "File" or "Tools" menu.
Choose a location on your computer to save the exported files and follow the on-screen instructions to complete the export process.

Importing into Outlook:
Open Microsoft Outlook on your computer.
Go to the "File" menu.
Select "Open & Export" or "Open."
Choose "Import/Export."
Select "Import from another program or file" and click "Next."
Choose "Outlook Data File (.pst)" and click "Next."
Browse to the location where you saved the exported Pegasus files and select the .pst file.
Choose the desired options for importing and click "Next."
Complete the import process.

Hi,

Using POP3 & IMAP setting pmail client not receiving emails from office365 mail server.

Note:
Office365 mail sever stopped the following ports pop3 & IMAP.

Please help, how to receive emails in pmail client.

Thank you

Step to AOL IMAP setting iPhone

On this page, you will find AOL Mail settings for the iPhone.  for setting up your AOL email on your iPhone.
1. Choose the settings Option in Your iPhone.

Frontier Mail Login With IMAP and POP3 Mail : https://www.realmailfix.com/blog/frontier-mail-setup-on-mozilla-thunderbird/

Don't do it from within Pegasus Mail. Exit the program and use the OS to move the entire top folder down to the new server.

OK, thanks.

If having more than one IMAP-mailbox and/or many folders, it takes a while vor Pegasus to completely close. Maybe Win10 shuts down before Pegasus has finished and the MAILBOXP.LCK remains in your mailboxdirectory.

I have configured Pegasus showing the little infowindow indicating new mails in my IMAP-Mailboxes. If that is closed by Pegasus at shutdown, you may shut down Windows (Win7 64bit and 32bit here).

Regards

     Olaf

[quote]The problem is pretty much just the inbox.  If I move all the emails to a tmp folder, and then move them back, the problem is cleared for a short while but comes back. [/quote]Why did you moved back the mails to inbox? After moving all emails back to inbox, you problems too are back. IIRC, the indexing works only in inbox and after having all mails back in inbox, mercury gets in trouble.

[quote]Since this is something that only recently started failing, I'm thinking that some spammer sent something that messed up mercury.[/quote]Possible but I believe not. Empty your inbox and one problem is gone.

Guy,  Thx for your help.  Yes, I had found that Apple doc and used it in my attempt to setup, but still had problems.  Also, I used Via direct SSL connect, but still no email.  Finally, after setting up the Tools/Internet Options, I also setup a Tools/IMAP Profile.  That finally did it.

Thx,

Mike T in VA

This article may explain many of my problems which (hopefully) are now resolved after all users with these devices have upgraded to the latest ios.

Bottom line is that Microsoft were advising Exchange administrators to block them !

Ios mail was seriously misbehaving with Mercury.

> I've set up my e-mail address through pegasus but want to switch to
> using IMAP, where can i find these settings for my e-mail address? A
> friend hosts my e-mail on his server

1.    Tools | IMAP Profiles allows you to setup an IMAP account.

2.    Tools | Internet options | (Sending) SMTP allows to to setup a SMTP host that supports the sending using the e-mail address of the IMAP4 account.

3,    Tools | Internet options | General allows you to setup your IMAP4 e-mail address.

[quote user="dilberts_left_nut"]

Grab a session log and see what is going on.

Should be pretty easy to spot the culprit (my money is on Exchange :) )

[/quote]

Hi dilberts_left_nut and all,

Well, too bad, I am not in the business of finding culprits, just not enough time, maybe when I retire (if ever) :) Seriously, DavMail turned out to be rather straightforward solution to my IMAP/Exchange headaches. This is free GPL software that runs on PC, presenting itself to PMAIL as POP3 server running on localhost. When polled by PMAIL it logs onto Exchange and retrieves new mail from it using .... its web interface! Works without a hitch so far, fingers crossed. Configuration is extraordinarily simple: run DavMail and supply Exchange web interface address to it. Enter "localhost" for PMAIL POP3 server with username and password required for Exchange login and make sure POP3 port is the same as in DavMail - that's it! Now PMAIL is happy fetching mail through tried and true POP3.

DavMail ( ) is being actively developed by Mickaël Guessant (just downloaded a new version) and sponsored by no else but French military. It is specifically aimed at Exchange to make it accessible by standard (i.e., not M$) protocols. There are few similar gateway products on the net, but most of them are out of date, hard to configure and unlikely to work reliably with Exchange anyway. DavMail offers POP3 which I am currently using, IMAP which I may try again after some cool off period :), SMTP for sending,  LDAP to access Exchange address books and Exchange calendar support. It can be run as a server on local network to be accessed by multiple clients. It is just a shame that someone's talent has to be used specifically to correct incompatibilities created by Micro$oft.

Cheers!

Hi Olaf!

Thanks so much for your reply and indeed it worked!

 [quote user="FJR"]

[quote user="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![/quote]

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

[/quote]

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.

[quote user="FJR"] 

[quote user="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.[/quote]

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.

[/quote]

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.

[quote user="FJR"] 

[quote user="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![/quote]

Should do!

[/quote]

Yay, it does!

[quote user="FJR"] 

[quote user="BoarX"]3. Move read messages from local inbox back to relevant IMAP folders as needed.[/quote]

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.

[/quote]

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!

> Yahoo! operates IMAP and secure IMAP servers (imap.mail.yahoo.com in particular), which are globally accessible.

I did verify that IMAP4 is now available from Yahoo.  This is the setting for a Yahoo Mail Plus account (i.e. not one of the free Yahoo accounts) that I am using and they work for me.  This may of may not be the same for your commercial account nor for the free Yahoo accounts.

(a) -POP3-

  Server host name: pop.mail.yahoo.com
  User name: <your_user_name>@yahoo.com
  Password: <your_password>
  Server TCP/IP port: 995
  SSL/TLS: via direct SSL connect
  Enable server certificate fingerprint tracking: unchecked

(b) -SMTP STARTTLS -

  Server host name: smtp.mail.yahoo.com
  Server TCP/IP port: 587
  SSL/TLS: via STARTTLS
  Enable server certificate fingerprint tracking: unchecked
  SMTP Authentication: Login to the SMTP server using POP3
  username/password (the Yahoo-POP3-definition has been chosen)

(c) - SMTP via SSL -

  Server host name: smtp.mail.yahoo.com
  Server TCP/IP port: 465
  SSL/TLS: via direct ssl connection
  Enable server certificate fingerprint tracking: unchecked
  SMTP Authentication: Login to the SMTP server using POP3
  username/password (the Yahoo-POP3-definition has been chosen)

(d) - IMAP4 via SSL -

  Server host name: imap.mail.yahoo.com
  User name: <your_user_name>@yahoo.com
  Password: <your_password>
  Server TCP/IP port: 993
  SSL/TLS: via direct SSL connect

http://help.yahoo.com/l/us/yahoo/mail/classic/mailplus/pop/pop-14.html

I'm testing Mercury/32 4.73 IMAP-functionality with PM 461 (and even Thunderbird) in a Novell Netware Environment (V6.5 - NDS). For some reasons we seperated "New Mailbox location" and "Home Mailbox Location" some 20 years ago (with Mercury/NLM). Because Mercury/32 obviously only looks at the "New Mailbox Location" (\\server\volume\home\~N\pmail) in PMAIL.INI, my existing folderstructure isn't involved, because it's in "Home-Mailbox Location" (\\server\volume\home\~N\pegasus).

At the moment IMAP of Mercury/32 doesn't support folders within folders, so build some trays and folders for testing. Works fine and is represented at the ...\pmail\HIERARCH.PM. But ... when I delete those trays, they are not realy deleted. They are still in HIERARCH.PM and do come up again everytime I create new folders or trays. It seems only the abbonnement is canceled! If I delete them from HIERARCH.PM via editor, they won't pop up any more. Bug?

Bye    Olaf

[quote user="Paavo"]

I have to watch for incoming spam some more -  does it indeed have the stored probablity initially as 100%. I suspect that the content of the message is not inspected when the imap inbox maillist (I do not use preview mode) is displayed. Therefore the spamhalter might not be avare of the spam at that moment.

[/quote]

Well seems that the new (spam) email in the IMAP inbox folder has stored spam probablity of 0% whilst the current spam probablity is 100%. That confirms for me that incoming email  in imap folder is not analysed when folder status is refreshed (this is logical).

However what could be a workable solution how to let pmail to deal with spam in IMAP mailbox?

[quote user="aderoy"]

There is a post in the Commnity Support regarding this. Sorry do not know how to reference. Basic idea:

Reading the blog and forums for Fastmail I was able to find this tidbit:

Try changing the hostname to insecuressl.messagingengine.com. We've added a couple of extra IP addresses and configured that hostname with SSLv2 support.

 ------------------------

Does work, otherwise use the non-SSL port (143).

[/quote]

Yes, I read the update on the blog after I posted here.  Thanks for the response.

Check the MercuryS log and the core log to see what is happening! If the message file (.CNM) is in the right mailbox directory you should be able to collect the message with IMAP.

In case you have any realtime antivirus software running please make sure to exclude all Mercury directories from scanning.