That's a problem with the rights in NDS. Group BECOME should have full access to the mailboxes of the project accounts. As I remember, group BECOME must be in same context than the users. The users (or/via group) must be able to see the project accounts in NDS. And at least they have to enter loginnames of project accounts as full distiguished names, because they reside in another context now.

bye

Please copy to output of Help, About, Info button display and post so we can see how and where installed and where new mail is located.

Is there any Anti Virus or file checking program running on the system and how is it set up? Does it work as proxy and put itself between Pegasus Mail and connection to mail server and/or the SMTP server? Are you running in standalone mode or are you running winpm-32 from a server install? Pegasus Mail can not read or write data any faster than read/write from drive location so the speed of connection is a limiting factor. Also speed and availability to exchange data with printer driver is factor also and if that is slow to read/write it will slow down mail accordingly. Is defined default  printer local to your machine or across network? 

First install v4.63 by running the distribution archive exe on the new machine and using the default offered c:\pmail location as the destination. You may configure and test.

Then later copy only the desired data files or message or address book file pairs plus any *.cnm files (new mail messages) to the c:\pmail\mail\admin on the new machine install. Leave all other files behind or if using compressed archive from old machine extract only the files needed. Make sure any files copied or moved are not marked R (read only) attribute at OS level and if so remove that attribute on the new machine location,

http://www.vandenbogaerde.net/pegasusmail/pf_pmfiles.html

is reference to files, names and locations. 

If you need old connection information best  plan is to print out the old .pmd file contents to use for reference in setting via the GUI on the new machine install.

Direct copy of pmail and below from old machine could only succeed *if* old machine install was in c:\pmail location and even that would only get you part way there. You would still need to run the v4.63 installer to set  proper registry entries and other things and mailto protocol etc.. on the new machine.

I'm not sure if this is the same problem but it seems that this explanation from Nick may shed some lights in. The text below is from PM-WIN@LISTSERV.UA.EDU archives.

[quote]Several "gurus" have looked at this several times.

The problem is obvious.

_Arguably_ RFC-correct multi-part messages with more than (from memory)
two levels of nesting and constructed in one of two (or more) legally
possible ways (that is where the arguments will start!  8-) ) are NOT
seen by PMail to have "closed" the "last level" of one of the MIME
level structures, when in fact, it has.  My _guess_ is that PMail then
scans through the rest of the digest looking for what it considers the
"missing" MIME part closure header.  It seems that the  parser is dead-
set that the next "MIME part header thing" it should see is this
"missing" part and thus it _ignores_ all the other MIME component part
start and end headers that exist from the point the PMail parser
errors, thus does not "see" any messages in the digest _after_ the
message in which this parsing error occurs.  As the digest summary
message -- the one that looks something like:

   There are 13 messages totaling 1058 lines in this issue.

   Topics of the day:

     1. smtp relay host
     ...
     6. PMAIL Digest - 4 Jan 2012 to 5 Jan 2012 (#2012-6)

-- is always the first message in the digest and (so far) always
produced in a format that cannot trigger this bug (it is a single-part,
text/plain-only Content-Type message) you can always see the correct
listing and count of the messages that the BAMA digester put into the
digest, but then may only see from 1-N (where N is the number from the
"There are 13 messages ..." sentence in the example above) messages
listed.  If you drop into "raw view" while reading the digest _and_ in
the message list viewer, you can see that all messages promised from
the digest summary are present, but as just described, PMail will not
actually list any of them (nor provide you any other way of seeing
them, other than "raw view") after the first message in the digest that
has this "imagined" MIME non-conformance issue.

In the last 4 or 5 years (maybe longer -- anyone keeping count?) this
has been noticed, replicated, analysed, and described on this list
multiple times, but never addressed in any updates.

It may well NOT be an easy fix, as the MIME component parser is
probably fairly crucial to a _lot_ of PMail internals and changing it
now may produce a whole lot of hurt (if nothing else, the beta testers
will presumably have to re-do a huge amount of message conformance
testing).



Regards,

Nick FitzGerald
[/quote]

Hope it helps. [:)]

Hi all ,

The problem has been fixed when i did an update to the last release of Bearhtml (4.6.9.0) and IERenderer (2.4.7.4.)

I wish to thank all of you for your help and patience... I don't know how could i fix  that problem without your help.

Happy  to be one of Pmail community.

[<:o)]

PS: from now i will also try to help other forum users if i can.

Thank you. Your suggestions - with some advice from a neightbour - have helped me out and I am OK again. But it does remind me that I should take these technical matters more seriously. Delay in reply due to need to get through Christmas and a big birthday before getting down to it again.

Charles

The PMIcal 1.11 opens now all (previously problematic) files.

Thank you.

I moved all the .pmm and .pmi files into the new installation.   Some of the folder names were garbled.  With those and all others I did a right click, index folder.  Then most of the emails showed as unknown so I deleted them.  The copyself.pmm didn't seem corrupted and it looks like all the emails were there after the reindex.  The ones I need for the court case were ok.

Thank you both for your suggestions. It's in the Inbox that she is having the

problem. What I've been having her do in the mean time is moving the

messages she wants to delete into a temporary folder - which she is then

able to delete.

I just discovered that the problem is in

the button on the toolbar. If she uses the delete key, the message

deletes. If she clicks on the delete button on the toolbar (which is her

habit) nothing happens. So it looks like the toolbar is somehow broken.

Is there any easy fix for that?

[quote user="bodhi926"]REALLY? gee maybe thats why i dont have outgoing mail, i have tried their settings and connected to a telnet server on port 25 also,  so i am a bit confused  apparently i am posting in the wrong section from what another user told me, didnt realize there was a difference between pmail and mercury.[/quote]

You've certainly confused me.

If you have a problem with Mercury transfer your post to that section.

• that did it..thanks to everyone....should I have discovered that on my own...?
  

Simple question indeed. The answer on the other hand... There are different approaches to this. Martin already suggested one. Another one would be to use public folders on a share. I think you should be able to find sufficient information on this in the Pegasus Help files. Yet another approach would be to use a service like Dropbox. That's where I save private mail that I receive at work that I also want to be able to access at home, for which I use the Pmail Add mailbox functionality in both my Pmail setups at home and at work. Many IMAP lovers will probably say "Why not use IMAP for this?" I don't have a very satisfactory answer to this, except that I'm just not such a fan of IMAP. I have a feeling that POP3 just gives me a little bit more control.

Don't forget also that double clicking on a Selective Mail Download list message gives you all the header data without doing anything else.   It was sometime before I found this trick.  Quite useful if you have any doubts about the "message source", it can be deleted at the server to avoid any spam, etc.   I find in fact that just the normal Subject Headings are enough in most cases to show what is undesirable or unwanted such as adverts from web sites that have been visited.

Rodney Fry

Just an update to my original query and the response from ms007.

I can now confirm also that on my Toshiba Satellite Pro L870-171 with an Intel CORE i5 2.5 GHz CPU using Win 8 Pro (64 bit) there was no problem in installing PMail v4.63.     I have set up PMail with my two ISP email addresses and it sends and receives messages correctly.  

As an aside this is after a local PC shop installed a Classic Shell  < http://classicshell.sourceforge.net/  >  for me as I found the WIn 8 interface unacceptable.   See for example "Downgrading form Windows 8 to 7: What you need to know" in PCWorld at < http://www.pcworld.com/article/2015107/downgrading-from-windows-8-to-7-what-you-need-to-know.html >

Rodney Fry

Could it be due to Owner Rights? If user name different (the secid string will be different no matter what) then you may need to 'take ownership' of the *.cnm files. Check against newer mails as to ownership and then go to the files that can not be deleted and change/add your current owner userid.

The easiest way is just copy. Shut down Pegasus Mail and copy ?:\Pmail folder and sub-folders to desired destination drive. It's easy as that.

 OTOH you may try a backup software that will do a lot more like compressing, incremental or differential copying, etc. There are several freely available in the Net.

Anyway, remember to always shut down Pegasus Mail before backup.

If check time is aimed to 14 minutes, set "Tools » Internet options » Receiving (POP3) » Check for new POP3 mail every:" to 840 seconds. If 15 minutes to 900 seconds.

Thanks for the help...

 I solve my problem, it was just a TLS configuration...

 Regards,

Jonathan Schirmer 

I asked the open-ended question, as the OP may find their answer in the process;
e.g., a Content Control definition is disabled. Or perhaps they are employing blacklisting
another manner, such as a filtering rule, like: If ListScan "@BLACK.PML" Delete "".

He mentioned the use of Mercury. I'm sure this task would be best addressed
via SMTP transaction-level filtering.

What's the complete errormessage?

Who's your provider?

 Did you forward or bounce?

You can send new mails but not forward?

bye   Olaf