- Go to the file: c:\pvpgn\etc\config.xml
- Change all instances of web1 to web2.
- Save the document.
- For this update to take effect, restart the PVPgn services.
- Adam Webmail should now be operational as it was previously.
- Please contact us at email@example.com if you continue to have issues following this.
- Adam Webmail was not working.
- Must Read: Adam Webmail
The enclosed file is a copy of the November 21st, 2004 firstname.lastname@example.org email chain. A reader gave this email was given to us by a reader, and we were astonished to learn that it is still being discussed. It’s placed here for completeness’ sake, to demonstrate how long some issues can go unresolved.
“Adam Webmail not working,” reads the initial pvpgn-users post. The problem was solved by modifying a configuration file and restarting the PVPgn services according to the poster. If this failed, the sign was advised to contact PVPgn at email@example.com.
The message’s original poster did not expand on what transpired next, so it’s unknown whether the issue was ultimately fixed. It’s possible that either the solution didn’t work or no one instructed him how to do it right. S/he most likely tried various things to get Adam Webmail to work again, which explains why the topic has been so long.
- What caused this issue in the first place?
- What went wrong with Adam’s Webmail?
- What’s the problem with the original poster?
- And why are people still encountering this issue?
The solution can be found in some adjustments made following the original pvpgn-users post. “Adam Webmail not working. -” read the next entry. I’m seeing the identical issue on another of my servers, which appears. Tied to the updating of multiple plugins.”
“The webmail plugin has been updated, and some changes have had to be made,” someone said.
Do the following:
- Unload the plugin from your server
- Change all instances of web1 to web2 in c:PVPgnetcconfig.xml (should be 3 or 4)
- Restart your server and reload the plugin.”
It’s clear that the issue isn’t limited to just one Adam Webmail plugin (web1) but affects all of them. Changes made to the “webmail” plugin after being updated newer version were found to be the cause.
The thread’s following few entries were brief and likely intended only to certify that this method did address the problem. The following intriguing entry came from someone who stated that they had manually entered their friends’ email addresses and passwords into Adam Webmail and were now having problems because others could log in as them:
“I figured it out… we added people, but didn’t modify config.xml so that we can log in as them, but they can’t log in as us…
- Go to the webmail section in config.xml.
- There, you will find something like this:
Replace it with:
- Save your work and restart PVPgn.”
This user went on to say that the issue only happened with “web1.2.8,” but that they were able to fix it with “web1.2.9.” S/he then stated that s/he would file a bug report with the Adam Webmail writers and recommend an upgrade to version 1.3, which would improve this feature of web-based email.
The issue is still being debated today. The solution, on the other hand, is now much more straightforward:
- Go to Adam Webmail and sign in.
- Go to “Settings”
- In the new window that appears, click on the relevant account name in the top left corner.
- Replace “ADAM Login/Password” with anything else to make each login attempt random (including capital letters, lowercase letters, numbers, and symbols).
After that, the Adam Webmail server will display a “bad login” notice, preventing anyone else from logging in as one of your friends. If someone tries to get into your account using their email address, the same highly secure login notice will appear instead of allowing them to proceed.