[quote user="ccomley"]

Can I stick my oar in here as we've been trying to resolve this problem for Johnny and getting nowhere.

It's not MTU or similar. The problem exists even if the Pegasus workstation is on the same LAN as the server. It's not time-out either. The session dies off, no amount of waiting for it to come back helps.

The server is Microsoft Exchange Server 2003 (SBS2003 version) with SP2, being accessed in this case via POP3. (MS's standard POP3 server module, no special add-ins.)  

The problem seems to be a specific mail item in the queue. The "manual" resolution is to use OutlookWebAccess to open up the mailbox, and move the offending item to a subfolder, or delete it, then PMail is able to fetch the other items in the queue entirely normally.

We do not think the "rogue" email is corrupt. The problem recurrs whenever that sender sends a similar missive. They tend to send mail with complex HTML content - but so far as I can work out *what* is contained within the message body shoujld just be regarded as "payload" by the POP process so it really shouldn't matter, even if the resulting email is one which Pmail can't display properly, etc. it should still download it.

I am investigating to see if it's a known issue with ES2003(POP).

I believe the *server* has a Nvidia chipset, I'll investigate changing this setting on the server and see if that makes any difference!! <later> It's a Nvidia board with an Nvidia Gig nic but there isn't a parameter called "checksum offload".

 [/quote]

Agreed, POP3 process should only get hung if there was some highbit character stream in the body that could block the TCP/IP process.  You might need to use "Selective mail download" on this specific message type while you have turned on the session logging. 

FWIW, the server itself can cause the packet fragmentation if there is a firewall running blocking outbound packets.  However is the packet discovery is turned off on the client side then this becomes a non-problem.

You might also try turning on blocking sockets using the -Z 1024 commandline option to see if this helps.

 1024    Use blocking sockets; may be needed for some
    defective WINSOCK implementations.
 

Dear rusty,

I think this is bad luck and you can't do anything inside of Pegasus Mail. I just tried deleting a folder (of course a test folder...); the folder seems to be deleted on operation system level. I recommend the following to you (but without any guarantee....):

0/ Try to avoid loading new files or doing changes to your entire file system.

1/ Make a - or better two - complete Backup(s) of your Pegasus Mail system AND your Mailbox.

2/ Use a tool to unerase the file on the operation system level. (Pegasus Mail folders consist of two files: .pmi and .pmm Unix mailboxes consist of a .mbx and a .pmg-file)

3/ As soon as you have unerased the file start Pegasus Mail. Please do not download or send mails in this session.

4/ Create a new folder in Pegasus (store no mail in it).

5/ Terminate Pegasus Mail

6/ Check (e.g. with motepad) in your mailbox directory the file HIERARCH.PM, look for the filename of the new folder; it's the last string in the first quoted field and starts with UNX or FOL (e.g. UNX056E1 or FOL06B44).

7/ Write down the file name of this new folder

8/ Delete the files of the new folder

9/ Rename the files of the old folder to the name of the new folder.

10/ Restart Pegasus Mail.

If this "restore" doesn't work please restore the backup you did in step 1.

For the future: Consider a regular and robust backup of your mails.

Yours,
Markus

Have tried re-indexing the folder? I had this same problem and reindexing sorted it out. Make a copy of the folder's pmm and pmi files first though, just in case it goes wrong.

Great! It works perfectly. I couldn't have found this myself, to put it mildly.

Thanks a lot, Thomas. You're a great help - and not just for me, I notice.
Keep up the good work!

H. Pelissier

Exceedingly minor correction to prior post: her rev is 4.12a, not 4.12c, not that it probably impacts the answer.

-=s 

The Pegasus Mail address book can be converted to many formats using "Dawn, the Address Converter and Manager"
http://mysite.verizon.net/zakharin/software/Dawn/ ... just pick one that MacMail can import.

[quote user="oonumberoo"]

Many thanks.

As "Internet formatted" came up automatically, I assumed this to be the one suggested, especially as my signature contains a website address, which I assumed would fall into the "formatted content" category.  

[/quote]

The problem is that the formatted signature is only used for a formatted message where the "Rich text" box is checked.

I was confusing the filter rules with the toolbar icon that must filter the open folder only (no action option to delete on server).  The POP3 ruleset you pointed to does allow to delete on server... and that did the trick after I also selected the new ruleset in the POP3 account download controls.  Thanks Thomas!

Regards,
Stan

Hi !

Thanks a lot Thomas, it worked perfectly fine.

Cheers ! 

Ginhead. 

Thanks Thomas, changed a few settings and all is ok!

Yes, it was that simple!

Thank you guys!

Joost

Just in case this may be it. I use several different identities in Pegasus Mail to access completely different pop3 accounts but had accidentally ticked "checking multiple identities" under the "receiving pop3" Internet options. It did not matter when I used selective mail download but when I just hit download I had a similar effect ... just an idea.

Cheers

Thomas

I imagine by now you have solved this either by brains or brute force. I also had this along with other installation problems.

To solve it I had to get a PMGATE.SYS into the Pmail/Programs folder. I generated this on the server with Mercury using UNC format for the path. Then I copied it across to the folder on the remote machine. Bingo!

The override of which they speak is of the format IN: and is placed with a space before the troublesome address. Since in my case I used the address book name it then came back from Mercury with "this user is not known on this system". Trying again with the email address proper it seemed to get posted off via Mercury and subsequent emails have not repeated the problem.

Anne Wainwright
 

I have amended the batch file kept in the Pmail Programs directory of the portable drive to be:

 winpm-32.exe -MS -roam

Seems to work very well.  The only exception is that the DOS style command window (in XP Pro) stays open unless I manually close it.  Apart from that minor thing this appears to do the trick, even shows single-user mode for one of the instances in the taskbar so I can tell them apart.  Your point is well noted about accessing the same mailboxes.  I can see the potential for confusion.  I had to edit a multi-pop entry to put mail into the correct folder.  But this is what I was seeking.  Thanks for the assistance.

Thanks Thomas.  I'll have a more detailed look at this at the weekend. 

I put an old Win98 machine on the network and that worked fine (using the same version of Pegasus Mail).  I'm not sure if it's a TCP/IP or DNS problem with the XP machine, or an underlying problem with the communication between the SMB software (VisionFS - it's old) and XP.

I've tried doing a command prompt copy of the attachment on the server to another folder on the server, and that only takes seconds.  I suppose I need to try copying between the PC and the server to see if that's slower than expected.  I'll maybe try out a network sniffer on the LAN to see if there are any clues in the packet captures. 

I love Pegasus, however one thing that always drives me nuts is the locking that Pegasus places on a folder after you attach files from it to an email. Unless you close and reopen Pegasus you cannot delete such folder.

Not sure why such lock is not released once email has been sent. Many times I unzip or copy files to a newly created fodler for emailing and each time I need to close Pegasus before I can delete it.

Any chance of fixing this in the new release?

Thanks.

[quote user="Bendt Skov"]Have been running without Symantec email checking in 2 weeks now, but unfortunately it is the same, my folders are deleted from time to time.  PMI files are there, but PMMs end up with 1 or 2 messages.[/quote]

Something is affecting the system.  How much free drive space is there?  Are you running anything at all that is accessing the Pegasus Mail files other than Pegasus Mail?  Might try turning off the drive write-behind caching as well.

Thank you for your reply; however,  I'm not clear on where you are suggesting I check.  If I review my distribution lists, that is, I click on each D-List in the Distribution Listing available via the F6 key and review the contents on the right panel, each address appears in good order (no odd characters, etc.).  I can not find any file named "list" or "list list".   I think I must have a bad distribution list though somewhere because Pegasus also bombs when I try to add an address to a distribution list by right clicking on the new message and selecting "Add Sender's Address To..." and then click on "Distribution List..."

 RESOLUTION:  Divide and Conquer...I moved all my personal D-List files (*.PML) to a temporary folder and tried above processes.  Both now work fine so apparently all my System D-List (*.PML) files are fine.  Next, I added half of my personal D-List files (*.PML) back and tried again.  Still all is working as it should.  Finally, I added the other half of my personal D-List files (*.PML) back and tried still again.  I fully expected it to crash, but it didn't. [:D] It seems the process of removing the personal D-List files (*.PML) out of my pmail directory and then copying them back must have fixed some slight file corruption in one or more of the D-List files.  I closed and re-opened Pegasus and all seems to still be working.  Thank you for focusing my attention on the D-List files.[D]

[quote user="David Suchy"]Does Pegasus use "Message-ID:" and "References:" fields from message header
when sorts folders into threads? It does not seem to me.[/quote]

Not is does not. 

Thomas,

Actually, I just figured it out. What I did was to set the flag in the PMGATE.SYS to force all mail through the gateway. Then, I went into the internet settings on the SMTP page and set the "Use in preference to LAN mailer for internet mail", and presto, internet mail goes through the SMTP process, getting my internet address as a reply to, and local mail goes through the gateway and gets my local address as a reply to.

In explanation, we have a WAN, and some users have internaet mail access, and some do not, so the reply to address becomes important.

 I'll check out Han's website. Thanks for the pointer. Thanks also for your patience & help.

Ed