I have just started to use the public folders feature of Pegasus Mail, and it seems to be a little annoying difference with regular folders. When you move unread messages to regular folders, the text next to its icon is colored in green, so you can always know if for a given folder you have still unread messages. However, with public folders, it seems this coloring option is not available. Is this the case or is it possible to activate it ? If that's the case, then I shall suggest in the relevant forum section to add this as a new feature for the next version of "Mail Store". Thanks for your help.
I often experiment this king of problem. First the message counter in one of my IMAP folder disappears (normally the iNBOX), then Pegasus states there was an error on the IMAP server and afterwards I get a MS C++ Runtime Library stating that there was a buffer overrr.
I normally restart PMAIL, reconnect to the IMAP server, right click on the INOBX fodler (or the one on which I have the problem) and clear both the header and body cache, then a reindex the folder and the problem is solved.
Sometimes, like today, this solution doesn't work and PMAIL contunies to crash.
In this situation I used to access my IMAP server via a web client move a substantial amount of messages from the INBOX folder to another one and hope that PMAIL is able to reindex the faulting folder. Of course I will prefer to have a "real solution".
Is the use of the mbxmaint.exe and check and reindex the faulting folder teh "real solution"?
Here is another option you might try. The reason that deletions are so slow is that it is moving each message to the "deleted" folder, and this takes time. Even if you normally allow messages to go there, you can bypass that option by holding down the <CTRL> key while deleting. You can select a whole group of messages by using <CTRL>-A or by using your <CTRL> or shift keys while selecting message to delete, then hold down the <CTRL> key while deleting. This bypasses the deleted folder altogether and is almost instantaneous. Be careful, though. When you do this, the messages are gone forever.
Suddenly cannot edit pop3 hosts for any identity. When I go into network configuration, click on receiving pop3, select a host and click on edit, PMail crashes. Using version 4.41 on XP. I've gone through all the usual maintenance procedures including reinstalling. Any ideas why this is suddenly happening. Thanks for your help.
How do I tell Pmail to put oputgoing mail into my new Queue location?
You have to use pconfig.exe (nconfig.exe NDS) to change the location of the Mercury queue for any client using Netware. If the Netware queue directory is still valid you might be able to setup a secondary queue in Mercury/32 pointing at that directory as an easy solution to the problem.
You are of course correct that both A and B can be achieved easily enough.
But there can always be that moment where neither A nor B exists due to migration to another computer, etc.
If there was at least a "folder does not exists" error which would tell Pegasus to simply ignore the filter, write to its log and continue with the next applicable filter. As it stands, Pegasus chokes. Maybe the problem is not Pegasus but Vista? I don't know enough about this type of programming to tinker with this myself, but in my world things desirably gracefully degrade.
I already have a folder named "To Publicity" which is giving me problem while i try to save sent copies on it. I think Thomas means changing the name of "To Publicity to something else
Is this, by any chance, one of those "mysterious" empty messages that, on locating the corresponding files, appear to occupy zero bytes of disk space? If it is, you can find the answer . If it isn't, what do you see if you go to File | Review queued mail?
If I import a tab delimited text file with Name and email columns, the name shows up correctly
but the email goes into the phone column and truncates.
[/quote]
Can't reproduce that at all here. However, when I click the the "Open or manage address books" icon in the toolbar, I don't get the Addressbook menu until I flip to the folders window and back again.
Either your firewall or ISP is blocking outbound connections to port 25 or the receiving server is rejecting your connection on account of your IP address.
Easy fix is use MercC to relay via your ISP's SMTP smarthost.
I was, of course, too impatient to wait for any replies, thus went ahead and "discovered" what could have been obvious all along... right while you were replying to this message. Thus I have already created a new thread, but I will leave it up, if only to double the chances for anybody else labelling this as a potential "bug" to find consolation quickly.
Sorry for the alarm again. And thanks for the official solution.
Geo, thanks for taking over there. For a few days I was only able to access the net via my phone and I was never going to type in all that needed to be explained in long form. You did a better job than I would anyway. Cheers.
Found if the folder was created first on the IMAP server then a copy the messages across (in groups of less then 2500). The larger messages could cause 'not responing' message ballons.
If the IMAP server is on a local network (100/1000) there would be problems only when the server was overloaded. Which acted similar to the FastMail situation above. This was very unlikely to happen.
[/quote]
Indeed there could be problems if moving large amount of data on IMAP. For example in my case there is a intrusion prevention system between my client PC and IMAP server - the large amount of data (or the sequence of commands who knows) triggers the Intrusin Prevention filters to drop some sessions (irrelevant of IMAP client: pegasus, thundebird - same result ). So some version of throttling or limiting the amount of data/commands per second would be perhaps desirable to avoid such things.
However - this is not the case I have described! In my case the mail move operation that initially starts on one target folder continues after moving the folder tree at a different target folder. The mails are mispalced. This is completely different and most probably Pegasus related bug, not server side bug.