Yes, that box is checked. I have also set the "name for default mail folder" parameter in the Options --> basic settings as the IMAP new mail folder.

 I do have the "Automatically the new mail folder at startup" parameter unchecked at this point. I tried leaving it checked, but that only opens the new mail folder on the local machine, not the one from the IMAP interface.

Is there some other setting I don't see?

I have been a Pegusus user for a long time now, and I think the product is great!

 I have implemented it across the company but I have am having problems with remote users opening emails with large attachments. When someone tried to open an email with an attachment, and they are not on the LAN but attached over our WAN, Pegusus can take as much as 5 min! The program will display "Saving Mesaage Status" this whole time.

 The wan links are mixed, some are DSL, some are fractional T1, however. This seems ecessive. It seems to happen across all users and workstations.

 Is there a setting somewhere that may cut this time down? Does anyone else see this behavoir in the Pegusus client?

 I did manage to save sometime by using Mercury 32 to poll the pop servers, saving Pegusus from having to download the messages itself, but the time lag is still excessive.

If you have Content Control activated look at the settings that limit the size of message to be examined, under the Message Tests, the value of  "Check at most...." should be altered if it is currently zero (whole message)

Martin 

The delay while extracting the file is to be expected but 5 minutes is way too long.  You might want to try using IMAP4 for those on a DSL or fractional T1 connection.  IMAP4 is a lot faster over slow links.

I checked the content control. Currently it is disabled, so I don't think this is the the issue. Any other ideas?

I thought IMAP4 was for downloading messages from a mail server, is that not true? These aer messages that have already meen downloaded via mercury/32. The Pegasus client is simply accessing them from the Netware server via the natime Pmail transport. How would I access these messages on the netware server via IMAP4?

Mercury/32 has access to the users mail directory and it you connect via MercuryI as an IMAP4 client then you will have access to all of the users mail folders.

When I try to access the mailbox via IMAP in Mercury, I get this message from Pegasus:

Profile 'Mercury32':

The IMAP server that manages this mailbox or folder has reported an error during the operation you have attempted to perform.

The operation cannot be completed.

The session log from Mercury shows this as the result of the attempt:

22:44:16.000: Connection from 192.246.117.242, Sat Feb 16 22:44:16 2008<lf>
22:44:16.000: << * OK server2 IMAP4rev1 Mercury/32 v4.52 server ready.<cr><lf>
22:44:16.078: >> A1 LOGIN "xxx" "xxxxxxx"<cr><lf> * Note Edited out username & password for post
22:44:19.078: << A1 NO Error attaching to mailbox (may be in use by another process).<cr><lf>
22:44:19.156: --- Connection closed normally at Sat Feb 16 22:44:19 2008. ---
22:44:19.156:

By the way, I have been trying to use the web ckient in Novell's Virtual Office. I've discovered that it also uses IMAP, but it won't show the contents of the mailbox. The mercury log from it's attempt looks like this:

13:25:41.796: Connection from 192.246.117.30, Sat Feb 16 13:25:41 2008<lf>
13:25:41.812: << * OK server2 IMAP4rev1 Mercury/32 v4.52 server ready.<cr><lf>
13:25:41.812: >> A0 CAPABILITY<cr><lf>
13:25:41.812: << * CAPABILITY IMAP4rev1 AUTH=PLAIN X-MERCURY-1<cr><lf>
13:25:41.812: << A0 OK CAPABILITY complete.<cr><lf>
13:25:41.812: >> A1 AUTHENTICATE PLAIN<cr><lf>
13:25:41.812: << +<cr><lf>
13:25:41.812: >> RUpSAEVKUgBkcmFj<cr><lf>
13:25:44.859: << A1 OK AUTHENTICATE completed.<cr><lf>
13:25:44.859: >> A2 LIST "" "U:\\MAIL\\60800000"<cr><lf>
13:25:44.859: << A2 OK LIST completed.<cr><lf>
13:25:44.859: >> A3 LIST "" "U:\\MAIL\\60800000"<cr><lf>
13:25:44.859: << A3 OK LIST completed.<cr><lf>

 But I have to not be in Pegasus to get this. The folder listed is my pegasus mail folder on the novell server (yes its bindery based, I know!). Unfortunately, the client reports unable to connect to the server, with an HTTP error # 500. Not sure what that means.

If Pegasus Mail is currently running pointing at the mailbox then the mailboxp.lck file will prevent the connection of any IMAP4 client.  FWIW, this is what it looks like when running Mercury/32 against a v3.2 server.  Note there is NO directory spec required in the LIST command since the Mercury/32server is talking to the Netware bindery via the Novell Client 32 and Netware dll.

--- Sat, 16 Feb 2008 21:51:02 ---
Connect to '192.168.1.5' port 143, timeout 30.
21:51:02.812 [*] Connection established to 192.168.1.5
21:51:02.921 >> 0076 * OK novelltstephenson.com IMAP4rev1 Mercury/32 v4.61 beta 2 server ready.\0D\0A
21:51:02.921 << 0015 A1 CAPABILITY\0D\0A
21:51:02.921 >> 0047 * CAPABILITY IMAP4rev1 AUTH=PLAIN X-MERCURY-1\0D\0A
21:51:02.921 >> 0028 A1 OK CAPABILITY complete.\0D\0A
21:51:02.921 << 0036 A2 LOGIN "thomas/THOMAS" "xxxxxxxxxx"\0D\0A
21:51:07.781 >> 0024 A2 OK LOGIN completed.\0D\0A
21:51:07.781 << 0015 A3 LIST "" ""\0D\0A
21:51:07.781 >> 0027 * LIST (\\Noselect) "/" ""\0D\0A
21:51:07.781 >> 0023 A3 OK LIST completed.\0D\0A
21:51:07.781 << 0016 A4 LIST "" "*"\0D\0A
21:51:07.796 >> 0033 * LIST (\\NoInferiors) "/" INBOX\0D\0A
21:51:07.796 >> 0044 * LIST (\\NoInferiors) "/" "* CA-14 Move *"\0D\0A
21:51:07.796 >> 0038 * LIST (\\NoInferiors) "/" "* Spam *"\0D\0A
21:51:07.796 >> 0046 * LIST (\\NoInferiors) "/" "* Yahoo Groups *"\0D\0A



 

So, you cannot read the bindery mailbox via IMAP when pegasus is running? How would I check mail using pegasus if it's not running? I can't use the native pegasus transport because it's too slow, but I can't use IMAP4, which is supposed to be faster, because pegasus is running. Sounds like a conundrum....

Also, I tried to reconfigure the Virtual Office web client, but I still get nothing back from Mercury. I still get the "The server encountered an internal error () that prevented it from fulfilling this request." error back from mercury, even though mercury shows me logged in in the MercuryI module.

[quote user="Ed Rush"]

So, you cannot read the bindery mailbox via IMAP when pegasus is running? How would I check mail using Pegasus Mail if it's not running? I can't use the native Pegasus Mail transport because it's too slow, but I can't use IMAP4, which is supposed to be faster, because Pegasus Mail is running. Sounds like a conundrum....

Also, I tried to reconfigure the Virtual Office web client, but I still get nothing back from Mercury. I still get the "The server encountered an internal error () that prevented it from fulfilling this request." error back from mercury, even though mercury shows me logged in in the MercuryI module.

[/quote]

You run Pegasus mail without the Netware support as a IMAP4 client only.   Any time you are not on the local lan it makes sense to use IMAP4 rather than the direct access for speed of operation.  I do this when I'm on the road with my laptop even when running with a fast link.  When running on a slow, expensive link (like on my last cruise) it makes even more sense.to use POP3 and work offline unless you must access one of your folders.

Have no idea what is happening with the virtual office web client since it's asking for a specific path and it should not do that.  I suspect it's improperly setup to ask for a specific directory.

OK, sot that worked better. Down to a minute for an email with a 3MB attachement.

Is there anyway to make the IMAP open automatically when Pegasus is opened? As it is, I must go to tools-->IMAP profiles and connect to the IMAP profile to activate it. Can they be made to default connection?

[quote user="Ed Rush"]

Is there anyway to make the IMAP open automatically when Pegasus is opened? As it is, I must go to tools-->IMAP profiles and connect to the IMAP profile to activate it. Can they be made to default connection?

[/quote]

In the IMAP profile editor in Pegasus Mail, switch to the "Settings" page and check "Always connect to this profile when Pegasus Mail starts up".

Cheers!

-- David --


PS: Based on the transcript you sent, your Novell IMAP-based webmailer is broken, or has been badly misconfigured. It shouldn't be passing a Windows path around that way.

The Novell IMAP client does seem to be tricky, I cannot get the mailbox field to clear. More research is required.

 I did what you suggested, and that worked as far as automatically logging in to the IMAP server. Now, how do I get Pegasus to actually display that folder upon opening Pegasus as if it were the new mail folder? I have set it as the default mail folder, both in the IMAP settings as well as the basic settings screen. I have also left the folder open when I closed pegasus (the save desktop state parameter is checked), but still the folder doesn't open automatically.

 Any suggestions there?

[quote user="Ed Rush"]

The Novell IMAP client does seem to be tricky, I cannot get the mailbox field to clear. More research is required.

 I did what you suggested, and that worked as far as automatically logging in to the IMAP server. Now, how do I get Pegasus to actually display that folder upon opening Pegasus as if it were the new mail folder? I have set it as the default mail folder, both in the IMAP settings as well as the basic settings screen. I have also left the folder open when I closed pegasus (the save desktop state parameter is checked), but still the folder doesn't open automatically.

 Any suggestions there?

[/quote]

Have you tried using the  "Make this definition's INBOX folder the default new mail folder:" in the IMAP4 configuration?

When this option is checked, Pegasus Mail will regard the INBOX from this definition as its primary new mail folder when the definition is active. The effect of this is that pressing <Ctrl+W>, or selecting any option that views your new mail will open this folder instead of the normal (local) new mail folder.