Community Discussions and Support
Changing pop3 and smtp hosts

I need to change the email server for both pop3 and smtp hosts for a group of email identities. They all use the same server. I open Receiving Pop3 or Sending SMTp for any one and click on edit, PMail crashes. Shouldn't I be able to edit the changes in place rather than adding a whole new host?


I need to change the email server for both pop3 and smtp hosts for a group of email identities. They all use the same server. I open Receiving Pop3 or Sending SMTp for any one and click on edit, PMail crashes. Shouldn't I be able to edit the changes in place rather than adding a whole new host?

Try creating a new POP3 and SMTP definitions instead and replace the old. You can have as many definitions as you want. Click Add and then New to enter the parameters for the new server either for POP3 and SMTP. After that, the new server will be available in POP3 and SMTP hosts listbox.
Don't forget to Disable "old" server in both POP3 and SMTP or it will still being used/polled.


Try creating a new POP3 and SMTP definitions instead and replace the old. You can have as many definitions as you want. Click **Add** and then **New** to enter the parameters for the new server either for POP3 and SMTP. After that, the new server will be available in POP3 and SMTP hosts listbox. Don't forget to **Disable** "old" server in both POP3 and SMTP or it will still being used/polled.

-- Euler

Pegasus Mail 4.81.1154 Windows 7 Ultimate
IERenderer: 2.7.2.2 AttachMenu: 1.0.2.0
PMDebug: 2.5.8.37 BearHTML 4.9.9.6

Pegasus Mail should not crash when attempting such an edit. I don't have an explanation into why this is occurring. That said, I believe it is easier to create new and then disable or delete the old rather than edit an existing one as completely as it sounds like you need to. I hope attempting to create a new one doesn't also cause a crash.


Pegasus Mail should not crash when attempting such an edit. I don't have an explanation into why this is occurring. That said, I believe it is easier to create new and then disable or delete the old rather than edit an existing one as completely as it sounds like you need to. I hope attempting to create a new one doesn't also cause a crash.

Yes, I see that. And I guess you're right. Thanks for your help.
Tariya


Yes, I see that. And I guess you're right. Thanks for your help. Tariya

Just as an option.
With Pegasus Mail Closed.
Should backup directory just to be safe.
Change to your Mail directory
Usually would be C:\PMAIL\MAIL or C:\PMAIL\MAIL\Admin or another directory.
But could be different depending on setup.


The files that have the definitions end with .PND
POP.PND and SMT.PND.


Copy them to another location for backup just to be save.
They are simple text files so can look at them with type command or a text editor like notepad.
Don't use a program like word that would change them from text.


Would first just look at each file to make sure none are corrupted.
use type on each of the PND files to see the back text.


If the look fine, after backing up, you could try manually change the lines you need.
Host, Port, User Name. Probable just the Host line would need changing?


Also, make sure they haven't been marked as read-only.


Note: The password line is encrypted, so don't change it, and don't post it.
So change that line if asking questions on contents.


Like others, don't know why it would cause crash, unless file is corrupted or flagged read-only, or something else has a lock on the files. (anti-virus?)


On my system, I have 6 PND files, 3 pairs for 3 identities (POP and SMT for each).
You might just have one pair or even more.


Again, copy the originals so that if change makes it worst, you can always put them back.
I have a PND subdirectory, where I occassionally make copies.


Then could try running Pegasus and see if changes allow POP3 and SMTP to work.


Just as an option. With Pegasus Mail Closed. Should backup directory just to be safe. Change to your Mail directory Usually would be C:\PMAIL\MAIL or C:\PMAIL\MAIL\Admin or another directory. But could be different depending on setup. The files that have the definitions end with .PND POP*.PND and SMT*.PND. Copy them to another location for backup just to be save. They are simple text files so can look at them with type command or a text editor like notepad. Don't use a program like word that would change them from text. Would first just look at each file to make sure none are corrupted. use type on each of the PND files to see the back text. If the look fine, after backing up, you could try manually change the lines you need. Host, Port, User Name. Probable just the Host line would need changing? Also, make sure they haven't been marked as read-only. Note: The password line is encrypted, so don't change it, and don't post it. So change that line if asking questions on contents. Like others, don't know why it would cause crash, unless file is corrupted or flagged read-only, or something else has a lock on the files. (anti-virus?) On my system, I have 6 PND files, 3 pairs for 3 identities (POP and SMT for each). You might just have one pair or even more. Again, copy the originals so that if change makes it worst, you can always put them back. I have a PND subdirectory, where I occassionally make copies. Then could try running Pegasus and see if changes allow POP3 and SMTP to work.

mikes@guam.net

Yes, I see that. And I guess you're right. Thanks for your help.


@Tariya, I am back because two things dawned on me.

  1. You said that that you "need to change the email server for both pop3 and smtp hosts". If that is all you are changing, then an edit would work.

  2. Ir the email server changes are server name only (you are not changing providers), then an edit would be better because the record that Pegasus Mail maintains of downloaded messages is associated with the POP3 host file. Creating a new host will break that record. This is desired if changing providers, but not when just changing a server name. The crash issue appears to be preventing you from doing this so a manual edit of the .PND as mentioned my @msetzerii may be the only option there. Hopefully you have rebooted the PC in an attempt to resolve the crash issue.


[quote="pid:57298, uid:28577"]Yes, I see that. And I guess you're right. Thanks for your help.[/quote] @Tariya, I am back because two things dawned on me. 1. You said that that you "need to change the email server for both pop3 and smtp hosts". If that is all you are changing, then an edit would work. 2. Ir the email server changes are server name only (you are not changing providers), then an edit would be better because the record that Pegasus Mail maintains of downloaded messages is associated with the POP3 host file. Creating a new host will break that record. This is desired if changing providers, but not when just changing a server name. The crash issue appears to be preventing you from doing this so a manual edit of the .PND as mentioned my @msetzerii may be the only option there. Hopefully you have rebooted the PC in an attempt to resolve the crash issue.

Cannot edit the existing definition (both pop3 and smtp) so we created new definitions. The new smtp definition shows in the list of definitions. If I go to delete any smtp definition, Pegasus crashes. In pop3 it lists the new definition three times. When I go to delete any one of these three definitions, Pegasus crashes. I'm coming to the conclusion there is a gremlin living in my pair.ini.


Cannot edit the existing definition (both pop3 and smtp) so we created new definitions. The new smtp definition shows in the list of definitions. If I go to delete any smtp definition, Pegasus crashes. In pop3 it lists the new definition three times. When I go to delete any one of these three definitions, Pegasus crashes. I'm coming to the conclusion there is a gremlin living in my pair.ini.

I agree. If I were to start troubleshooting this I would start with the PMAIL.INIi file. Rebuilding it is relatively painless when there are no additional identities but it gets increasing tedious with each additional identity because you must create and configure each one. This is said from the point of view of taking the existing PMAIL.INI file out of the picture, letting Pegasus Mail create a new one, and then reconfiguring Pegasus Mail. I have had very limited success with manually locating and fixing problems in the .ini so I don't recommend it.


My process is to


  • close Pegasus Mail
  • rename PMAIL.INI to PMAIL_INI_SAVED.TXT
  • start Pegasus Mail
  • reconfigure Pegasus Mail (Tools > Options & Tools > Internet Options)
  • refer to the old .ini file, opened in Notepad, when I had a question about my previous settings.

I agree. If I were to start troubleshooting this I would start with the PMAIL.INIi file. Rebuilding it is relatively painless when there are no additional identities but it gets increasing tedious with each additional identity because you must create and configure each one. This is said from the point of view of taking the existing PMAIL.INI file out of the picture, letting Pegasus Mail create a new one, and then reconfiguring Pegasus Mail. I have had very limited success with manually locating and fixing problems in the .ini so I don't recommend it. My process is to - close Pegasus Mail - rename PMAIL.INI to PMAIL_INI_SAVED.TXT - start Pegasus Mail - reconfigure Pegasus Mail (Tools > Options & Tools > Internet Options) - refer to the old .ini file, opened in Notepad, when I had a question about my previous settings.

I agree with your recommendation. I don't think I can handle a new .ini file. There are a boatload of .pnd files in the current .ini, going all the way back to 2003. What seems to be working now... I've created new pop3 and smtp definitions and if I disable them I can delete them without a crash. So I simply added them and disabled them. When we make the account move tomorrow to a different host (same provider), I'll just disable the current definitions and enable the new. If there are no typos in the password, that should work. (I wish David would provide a way to check the passwords underneath those damn dots. Too easy to make a mistake.) Lighting a candle!


I agree with your recommendation. I don't think I can handle a new .ini file. There are a boatload of .pnd files in the current .ini, going all the way back to 2003. What seems to be working now... I've created new pop3 and smtp definitions and if I disable them I can delete them without a crash. So I simply added them and disabled them. When we make the account move tomorrow to a different host (same provider), I'll just disable the current definitions and enable the new. If there are no typos in the password, that should work. (I wish David would provide a way to check the passwords underneath those damn dots. Too easy to make a mistake.) Lighting a candle!

I wish David would provide a way to check the passwords underneath those damn dots. Too easy to make a mistake.

There are several applications to face this task. Here are two of them:


  • GetWindowText is a very small Windows program with which you can read window texts and contents super easy!
  • Passware Asterisk Key Instant recovery of passwords hidden behind asterisks.

I have others but these two shall do.


[quote="pid:57309, uid:28577"]I wish David would provide a way to check the passwords underneath those damn dots. Too easy to make a mistake.[/quote] There are several applications to face this task. Here are two of them: - [GetWindowText](https://www.softwareok.com/?seite=Microsoft/GetWindowText/) is a very small Windows program with which you can read window texts and contents super easy! - [Passware Asterisk Key](https://www.passware.com/asterisk/) Instant recovery of passwords hidden behind asterisks. I have others but these two shall do.

-- Euler

Pegasus Mail 4.81.1154 Windows 7 Ultimate
IERenderer: 2.7.2.2 AttachMenu: 1.0.2.0
PMDebug: 2.5.8.37 BearHTML 4.9.9.6

edited Jan 11 at 9:39 pm

Well, it's done. Migrated the account to a new platform. Everything seemed to be okay except a couple of hitches with Pegasus. I think we solved them, at least temporarily. Do you think I should run the .81 installer again just as an update to maybe replace any file corruption?


And thanks euler for the little tools. Very handy to have.


Well, it's done. Migrated the account to a new platform. Everything seemed to be okay except a couple of hitches with Pegasus. I think we solved them, at least temporarily. Do you think I should run the .81 installer again just as an update to maybe replace any file corruption? And thanks euler for the little tools. Very handy to have.

And thanks euler for the little tools. Very handy to have.

You're welcome. I'm glad it helped. smile


[quote="pid:57311, uid:28577"]And thanks euler for the little tools. Very handy to have.[/quote] You're welcome. I'm glad it helped. :)

-- Euler

Pegasus Mail 4.81.1154 Windows 7 Ultimate
IERenderer: 2.7.2.2 AttachMenu: 1.0.2.0
PMDebug: 2.5.8.37 BearHTML 4.9.9.6

Do you think I should run the .81 installer again just as an update to maybe replace any file corruption?


If all you did was change the server of your POP3 and SMTP services then I don't see any reason to run the installer. Doing so should be harmless so do it if it would put your mind at ease. Backup first.


[quote="pid:57311, uid:28577"]Do you think I should run the .81 installer again just as an update to maybe replace any file corruption?[/quote] If all you did was change the server of your POP3 and SMTP services then I don't see any reason to run the installer. Doing so should be harmless so do it if it would put your mind at ease. Backup first.
live preview
enter atleast 10 characters
WARNING: You mentioned %MENTIONS%, but they cannot see this message and will not be notified
Saving...
Saved
With selected deselect posts show selected posts
All posts under this topic will be deleted ?
Pending draft ... Click to resume editing
Discard draft