[quote user="Dustoff"]Yes, I can list many identities in the SMTP network configuration and switch between them by using the disable/enable buttons on the right side to choose the one I wish to use at the moment. It does NOT matter where that identity is in the list if it is the only one enabled. Perhaps if I moved the desired one to the top of the list that would work as well but I have not tried it since I feel more comfortable disabling the ones I am not using.[/quote]

Go to Tools / Identities and create a new Identity and then 'become' it.  Now set up the SMTP setting you want for that. This will be activated every time you become that identity - there's no need to enable/disable items each time.  You can set the shortcut to start in a specific identity or change manually after starting.  There are quite a few options which are identity-specific, including your email address.

[quote]Neither the manual nor the help files describe the way to choose between multiple SMTP identities and I had to figure it out for myself.[/quote]

The help has a detailed section on Identities and Attaching identities to folders. It doesn't mention SMTP explicitly, but does talk about different POP3 definitions.

From Thomas's reply it seems that concurrent running is no problem.

The install on the usb drive can potentially be used on any pc you plug it into, if that could be an advantage.

There are instruction on the forum for installing on a usb device to avoid problems when the drive letter changes.

thank you for the quick answer

Regards,

Ben 

When it is a stand-alone PC (for test purposes) and you are only sending messages to yourself, there is no SMTP host to consider. It is simply Pegasus Mail that isn't working correctly.

This may seem an insignificant issue, but sending emails with messy code displayed is not a very "attractive" advertisement of the product. A product of which I am a hugh fan. My Outlook colleagues are just waiting for issues like this to force a switch from using Pegasus Mail. I am a lone voice in a field of Microsoft corn.

Thanks for your help.

Regards. Stephen S.

I've written a utility for performing the equivalent of Pmail's "Check consistency" but that operates on Unix format folders.

It can also convert them to normal (V2.x) mail folders preserving the status and colour of messages and their position in the Folders window.

An overview can be seen at http://www.chainganger.co.uk/Pmail/Peg.htm and you can also download from that page.

Bob

But..... It's currently not setup for more than one user. Therefore I need the info on what to do after the fact.

If you have only one user then it will never ask for a username, there is no reason to ask for a username when there is only one user.  Adding a user should be simple if this was a relatively new installation.  You should have a Addresses |  User management menu item that allows you to add a new user.  If you do not then it's a bit more difficult.

These are the procedures for converting from single user to multiuser.  This process assumes that you used the default settings when installing WinPmail in single user mode, therefore the basic directory is c:\pmail and the mail directory is c:\pmail\mail. 

1:  Go to the MSDOS prompt and create a directory for your current mail files and username.  I assume you are using a username of THOMAS.  

    MD c:\pmail\mail\THOMAS

2:  Move your current mail files from the c:\pmail\mail directory to the c:\pmail\mail\THOMAS directory.  

    MOVE c:\pmail\mail\*.* c:\pmail\mail\THOMAS

3:  Edit your pmail.ini file and change all instances of c:\pmail\mail to c:\pmail\mail\THOMAS.  If you have saved your username in win.ini, edit the win.ini file and remove the username line. 

4:  Delete the file c:\pmail\pmail.cfg.  This will remove your current configuration and force WinPmail to go the install process. 

5:  Double click on the WinPmail icon.  Since the pmail.cfg is missing, this will cause WinPmail to go through the install process.  Select the multiuser option.  

6:  You will be asked to about the users.  Add the username THOMAS and any other users you wish.  Make sure you give administrator privileges to at least one username so you will be able to administer to users.  Select close. 

7:  You will be asked to select a username, use THOMAS.  This should now open WinPmail using you old mail information.  You will now have an additional menu item under Address that will allow you to administer your users from WinPmail. 

8:  You now can create an icon for each user with the -i <username> commandline option to enable starting WinPmail without having to enter the username each time. 

This is not graphics related, but I also have issues when forwarding HTML mail in Pmail v4.41

 I get loads and loads of "&#160;" all across the screen. These are often placed in "From", "To" and "Subject" headers.

Is this a bug with Pmail or the HTML rendering..?

 Thanks. Stephen S.

Yes, that's checked but makes no difference.

I've now made url links work by unchecking it and putting in the address of the browser (/usr/bin/firefox)

I've tried doing the same for attachments (Options / Content viewers) by specifying the program for each attachment type.  The correct program starts, but unfortunately the link passed doesn't resolve:

e.g. "/home/paul/c:\windows\temp\wpm1234.doc doesn't exist" 

> Hi Pmail Forum,
>
> Thanks in advance for your help. I Love Pmail for years but I do
> have an issue.
>
> I have a vendor in my business who sends me email updates on what is
> new from them. In the body of their email (over half
> dozen emails over time all say the same thing from them), this is
> what it says ( I did a cut&paste.... )
>
> "This message is in MIME format. Since your mail reader does not
> understand this format, some or all of this message may
> not be legible."  And that is all I can see in the body of incoming
> email from them, nothing else.

Might be that you are setup to view plain text messages only.  When you open the message try hitting the "View" button to change from the plain text to the rich text mode. Also try the following format options.

1.  Tools | Options | Messages and replies check "Use MIME
    features"

2.  Tools | Options | Message formatting uncheck everything under
    "Formatting and use of styling in messages"

If this does not help then provide us with a copy of the actual message for analysis.  We need the whole message as originally received.

Thank you! This worked a treat.

BWHAHAHAAA !!!

It just happened again, but this time I knew better, thanks to your advice.

Waited 10 seconds, sent the mail again, and Ta-Da,,,, there it went.

Thanks a ton. Pegasus is fantastic.

Use File / Selective mail download to see the date/from/subject/size of each message and decide if you want to download them.

Thanks for your help ill have a look

Cheers

Stew.

I think I may have a bigger problem then as the NAS runs Linux...

It does not really make any difference what the NAS runs (the first ones were Netware) since the program will actually be running on the windows box.  The NAS is just for file storage just like any other drive.  You are installing to the NAS server from a windows system.  If all of the systems use the same drive letter for the NAS drive then you can make this work a lot easier on the Vista systems as well.

No, that's not a good solution.  I presume the account you're using has limited rights, correct?

To what settings are you referring?  The settingss under Tools -> Options?

[quote user="edogroen"]

Hello,

Pegasus Mail crashed all the time at start up. I have tried many options:

- checking the HIERARCH.PM file, not sure how it should look like but I don't see anything strange.

- moved all new mail files from the folder

- moved all other resent files from the folder

- reinstalling version 4.41

The first problem was that it crashed every time at start up from my user. I found out that I could start another user and switch to my own user. Now that trick doesn't work anymore.

After moving the files as described above Pegasus works on start up and you can use it, but as soon as you switch to another program it crashes. It also seems to crash when switching to another screen in pmail. The last try was to close all screens, but when pmail loses the focus it crashed again.

I run Pegasus Mail 4.41 on Windows XP. Pmail and the mail folder are on a network disk (it worked fine like that for about a year already).

I've been looking at this for some time now and really have no real answer for you.   Since it only happens for your user and not for the others it looks like there is something wrong with the user configuration.  I would exit WinPMail, delete (or move/rename) the following files and try again. 

pmail.ini, desktop.pm*, state.pmj, folstate.pm 

When you next run the program you will be starting as a new user.  All you configuration will have to be re-done, all identities lost.  The POP3 and SMTP setups will be gone as well but you will be able to use the "add" to restore them.

Please help.

[/quote]

[quote user="irelam"]

Did you run Pconfig.exe to check the locations for folders?

[quote user="Thomas R. Stephenson"]

That trailing "\" can cause a crash since it points to nothing.  This should either be d:\pmail\mailor d:\pmail\mail\~8 depending on whether you are multi-user or single-user. 

Ok this looks like single-user and so the path should be d:\pmail\mail.

[/quote]

Thanks, this put me on the right track.

I deleted the paths in pconfig and retyped them. This fixed the crash. Maybe there was a hidden corrupt character.

I also had to get rid of the trailing slash, as you suggested, to get rid of some warnings at startup.

I use Pegasus Mail on XP and Vista to access the mailboxes stored on the nas.  I want to be able to get a webmail like interface running on the nas (ideally php, as a webserver and php are available for the nas) to allow off-site access the pmm files.  It would not really need to be a full webmail client, and r/o access to the folders would be enough.

> Yesterday, that all changed.  Now I can only receive (POP3) emails,
> but my sending is blocked no matter which of the three security
> protocol buttons I choose.  I can ping the mail server; nothing
> wrong with the hardware link.

What we really need to see is a session log showing exactly what is happening between Pegasus Mail and the host.  I suspect from your mail that you need to be using STARTTLS with your username and password and then also use SMTP authentication.

>
> Three different error messages, "Never" brings "must start TTLS
> first."
>
> Use STARTTLS brings "user not authenticated."
>
> Via direct SSL brings no explanation except "network error."
>
> I've spent three long calls to my ISP support, which is Bell
> Telephone in Canada, emails ending in @sympatico.ca
>
> As English isn't the first language of the overseas support people,
> it's a little hard to communicate, but as far as I can tell, their
> system made a "security change" and who knows what that was, but it
> does block Pegasus sending.
>
> Sad to report, Windows Mail, the Vista incarnation of what used to
> be called "Outlook," DOES work.
>
> It appears that there is some additional security protocol feature in
> Windows Mail that doesn't exist in Pegasus.  (Sad sad day for the
> emailing world!)

Probably it because of something that outlook does not do, CRAM-MD5, and this has been causing all sorts of problems when it's advertised and then not implemented.  You can use PB1 and tell the system to never use CRAM-MD5.  From the PB1 help:

Do not use CRAM-MD5 authentication even if it is advertised  This one's a bit technical, so please bear with us... The process of logging into the SMTP server to authenticate your identity can take a variety of forms: the server "advertises" the forms it understands, and Pegasus Mail looks through that list, choosing the most secure form it recognizes. Some forms are very "weak", in that they either transmit your credentials as clear text or in a form that can be easily broken, while other forms are "strong", in the sense that it is very difficult to work out your credentials simply by observing the exchange of data between the two programs. Unfortunately, one of the strongest forms of authentication, called CRAM-MD5, is commonly misconfigured on SMTP servers, even at quite reputable ISPs - the server will advertise that it supports it, but will actually fail any attempt to use it. Getting the ISP to realize that they are at fault is a lost cause in most cases - it's almost always easier simply to check this control, which tells Pegasus Mail never to use CRAM-MD5 for this server. You should be aware that you reduce the security of your connection by checking this control: CRAM-MD5 is the only commonly-used authentication form that offers reasonable security, and by disabling it, you force Pegasus Mail to use less secure methods... But sometimes you may decide that being able to send mail is more important than being able to do it securely. The choice is yours.

[quote user="voxmagna"]

Thanks Thomas. I missed off something important on my post:

I always set PMAIL to defer sending mail which I do manually once my messages are in the queue.

So the issue is not my host, because the message with large attachments never goes out, It's still being transferred to PMAIL's cache or stops during it. It's in this 'lockup' state when the PC appears hung that things are going wrong. I can't unblock PMAIL if it's still writing out to its cache file and stopping the PMAIL service manually leaves the partial cache files in a mess from which I can't easily recover.

 It's easy to check, just attach a really big file to a pmail message and try sending it to yourself. If your PC doesn't hang forever like mine, then I know I have to be looking for something else. I'll look into the content control options. My original issue was it is too easy to drag and drop a very large image file by mistake into PMAILs attachment window, hit Send All Mail and get it screwed up.

How big a file are you talking about?  I send 5-6 MByte files on a regular basis using the built-in mailer.  It does take a bit to encode the attachment but it's about 30-40 seconds max (which seems like forever when you are setting there looking at the screen) and it always has no problems sending.  Now if the receiving host can't handle a message this size and bounces it then that's definitely going to cause a problem when it gets back to my mailbox.  I always verify what the receiving system can accept before sending huge files like this via email.

I always know which file is the one locking PMAIL from restarting, because it's the biggest and newest because PMAIL won't run and no more mail files can be created after the lockup. I can't I create new messages or read saved mail either.

Thanks for your help, I'll go see if I can set message size restrictions for outgoing messages to stop PMAIL hanging.

[/quote]