This kind of truncation is quite common when users change the display pixel dimensions and change the font to Small. Applications are not aware of video driver settings except for pixel width/height settings and frequently make no attempt to adjust positioning of objects on their displays

Martin 

Alphabetical is all there is, sorry.

I've learned to deal with this in a couple of ways.  First, a space is a character and unlike Windows folders, PMail folder names can include leading spaces.  If you prepend one or more spaces before the folder names, they jump to the top of the list.  Second, I use the alpha sort to my advantage by naming the folders things like "PMK - Pegasus Mail 'Keepers'".  Then when I'm in the folder list if I type "PMK" the cursor jumps directly to the first matching folder. I don't really care what order they're in as long as I remember the first few letters of critical folders.

I had no problem reading my TBird addressbook - It was just that when it was written out for Pegasus, it never seemed to work (PM didn't recognize it properly). I would end up with an addressbook named "C", with no entries, and it would replace whatever addressbook I had before hand. I finally just created a tab-delimited file from my TBird addressbook and imported that OK into PM.

As for the mailboxes - Yes they showed up if I put them in the mail directory with an *.mbx extension. However, nested folders didn't work. A TBird folder can contain either messages or other folders, and PM didn't see them as nested. I just copied all the non-nested mailboxes, recreated the rest and then manually moving things where they needed to go. Took a little while, but not too bad.

At this point, I appear to be fully migrated, with the possible exception of a few rules, maybe. 

Thanks.
 

1) We have the winpm.exe file stored on a central server, where a user opens pmail, that it directs them to their inbox (also stored on the server).  Is there a way to verify?

2) How do I check this?

 Thank you,

Matt

After a week of fiddling with their new downgrade... errr... upgrade, Earthlink seems to have gotten their mail server working. All is well. My faithful Pegasus is working properly. Apparently it was the server that was not in compliance. LOL!

 Thanks for the help. I needed that information on Security Settings to get Peg working again! You folks are and always have been great to work with.

Progress update:

I did some further testing with a folder of 4 emails, all of which

should trigger a rule to change the messages a different color. 

Dist

List1 - combination of real addresses and alias names. Results: The

emails matching the real addresses in the list were changed, the alias

emails were not changed.

Dist List2 - only real address entries in the list. Results: All emails were matched and colors were changed.

Dist List3 - only alias entries in the list. Results: No emails were matched and colors were not changed.

Final conclusion: If the distribution list contains real addresses, a "scan list" rule will work on matched emails. It will NOT work with alias names.

The real problem:

The PMAIL help documentation says a "scan list" will work with either

an alias name or an address. That is not true. Even more confusing, when

building a distribution list by selecting the entries from an address

book, the alias name is what is stored. That would lead a user to

believe that the alias name can be used in a scan list rule. I find no

place in the help doc that says a "scan list" must use a distribution

list with real addresses. Can this anomaly be fixed?

Earlier in this thread, user "twonotes" was chastised for calling this problem a "bug". I'm sorry, but I have to agree with his statement that the scan list function does not work as advertised and is therefore a "bug". Either the documentation should be changed to clarify the problem or the software should be changed to agree with the documentation.

Thanks to all that helped with this problem. At this point it appears my only recourse is to go back and rebuild this distribution list using real addresses. Bummer!

That worked great Thomas. Thanks

Yes that is true.  When one of the salesmen got a blackberry I

forwarded all of his internet and local mail to his new email address

on  the Blackberry server.  This worked great but when

sending an email that involved  "Custom headders for this message"

under the SPECIAL tab then Pegasus would crash.   There are

two ways for the blackberry to get email without

exchange/groupwise/notes and tahat is by frowarding  or setting up

the Blackberry server to use POP to get the mail from our mercury32

server.  

hth  Randy 

Angus,

Thank you for your thoughtful suggestion.  At the time of my problem, the Pegasus windows was clear of any subordinate windows.  Maybe my problem was that when I anticipated appearance of the options sub-window, I did not not notice appearance of the scrollbars.

You were correct that sudden appearance of scroll bars should have given me a clue.  When I was looking for the options window, I apparently failed to note the suddenly apparent scrollbars.  Thank you for your patience and your perception.

In your IMAP profile editor, switch to the "Performance" page and uncheck "Use fast folder listing commands".

This problem is in the queue to be fixed.

Cheers!

-- David --

Not sure if this is more Mercury/32 or Pegasus Mail related. Please locate in the most logical or beneficial thread.

This snapin is great - it has made our

administration much easier. In using the snapin along with Mercury/32 v4.52(modules

S,P,E,D,X,I) in NDS mode, I have found a couple things that need to be changed

or added in the documentation (I am using v1.10b).

1. The syntax to ignore sorting and

place no spaces in front of the address reads Myforcefirst=N in the

documentation. What actually works (as found by turning on Mydebug) is

Forcefirst=N. I needed to get the "compute" function to remove the space

that gets added to the LDAP address by default.

2. The reason I found this error in

the documentation is that when using Mercury/32 + LDAP addresses + Pegasus Mail

(currently using v4.31), messages being sent to any yahoo address (US or Korea,

at least) are rejected because a space exists in the addresses. To get the

messages to deliver (to yahoo.com and some other domains), the leading space

must not be present in the address.

The MercuryE error that I've

commonly seen when trying to deliver messages where the sender LDAP address has

a leading space is “Connection error during handshake” or a 550 “…does not

conform…” .

[quote user="Cherylez"]

OK...it seems to have "magically" started receiving again...but I did learn it is not sending anymore.  I have attempted several tests...and they never show up.

I did try a telnet port to 110...and it never returns a thing.  In fact the window just closes upon running the command.

Is the ' after the domain required?

[/quote]

Sorry, that was a typo on my part, the ' is neither required nor desired.  However, when testing sending you need to go into port 25.  There is also the possibility that your ISP requires authentication and is acting as a user agent on port 587.  You really need to talk to your ISP and ask them specifically what you need top be doing since this sounds like your ISP has changed things.

Thank you very much, that worked[:)]

There probably isn't a day goes by where I don't search my new mail folder, usually many times. Believe me, if this were a clear problem, it wouldn't last a second (the problems that get fixed fastest are always the ones that impact on me personally).

If you can come up with any more clues as to what might be happening, please mention them here and I'll try to make time to look into them.

Cheers!

-- David --

[quote user="dthomsen8"]

My button panel has disappeared from my primary user, but it is still there on three other less frequently used users.  How do I get it back?

I tried changing Tools, Advanced Settings, Load Windows Internet Services to "Never" and back to "Always" but there was no fix.  The other users are set at "Always" and the button panel and the POP3 and SMTP buttons work just fine. 

[/quote]

When you change back to "Always" or "On demand" from none you need to close and re-open the program. 

[quote user="twonotes"]

If that is how it is supposed to work then I will shuffle all my Identities around so that the <DEFAULT> one is the one I use with IMAP.

[/quote]

Yes, that's probably the best solution if you don't want to manually choose the identity before sending e-mails.

Thanks everyone. I can now use Pegasus from the non-Admin account. Like I said in one of my earlier posts, I've been using Pegasus since Windows 3.1 and a mostly text-based internet, and didn't want to give up on this. Thanks again for your time and expertise. Anyway to mark this thread "solved"?

What is the source of the emails which truncate?  I'll bet there is a problem with them having lines of text that are longer than the official RFC maximum for email (I think it's either 512 or 1024 characters in one line).  AOL is notorious for this.

   

Hi,

Thanks for your help (it was much appreciated!).

It turned out that one of my less-than-careful mates had sent an email with a suspect attachment.  Once I'd looked at my mail through my ISP's website & deleted the dodgy message, everything was ship-shaped & Bristol fashion once more.

Thanks again for taking the trouble to help.

All the best,

Felicity x

NOT really needing any assistance at this time.  Just wanted to pass on how my PMail is operating, without any difficulty.  If this is not acceptable in here then delete my POSTS.  Do not want to cause any problems just wanting to share.

 I have been using my systems for about 10 years from here at home, XP H/E SP-2 for about two weeks moved to this one from Win98SE and before that Win95 and Win3.11.  Have been on the web since before the "www" was ever started, about 1986 when I first started using TCP/IPs to surf, rather slow and combersome.

 Thank you for reading my post and this reply plus I appologize for any Miss-Understanding, have a great day,