• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • Debian 11 has reached its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.81 is the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

Very serious problem with e-mail accounts!

F

frej

Guest
SPECIFICATIONS:
Plesk 7.5.1
Red Hat Enterprise 3
Webmail client – SquirrelMail version 1.4.3a-7.EL3

PROBLEM:
1.)
When USER-A login to www.domain.com/webmail – username: [email protected] everything is OK, USER-A is able to login to read and compose messages.

2.)
When USER-A login to www.domain.com/webmail - username: test
everything is OK, BUT, when USER-A tries to compose a message and send it, this message is sent from USER-B’s account.

I have only seen this problem with one user/account on the server, but I think it is a bit disturbing, especially if it where to happened to other users/accounts.

Have any one come across this problem before?


Thank you!
Regards
Frej
 
With Squirrelmail you should always log in with the full email address as the username or you will have problems... that's been my experience anyway.
 
thanks,

Yeah I know, but it seems customers forget this sometimes .. :)
 
Here's what I did...

I edited the login.php file in squirrelmail to add text that users should use their full email address. I also added some javascript to ensure that they entered the domain part (i.e. @domain.com) in the username field.

It's a pain, but it works.
 
Back
Top