• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Atmail Oddities….

Gene Steinberg

Regular Pleskian
Using the 1.0.4 version that came with Plesk 10.1.1, I get this at the top of the Settings screen on all domains;

Notice: Undefined index: debug_sql in /var/www/atmail/libs/Atmail/SQL.php on line 50

When I sent a message, it remains on the screen, even though it has been sent.

Solutions, suggestions?

Peace,
Gene
 
The problematic message has HTML format and contains the following line:

--HTML--
<p style="margin: 5.95pt 0cm 0.0001pt; line-height: 50%;"><span
class="SpellE"><b><span style="font-size: 10pt; line-height:
50%; font-family: Arial;">Pol.Ind</span></b></span><b><span
style="font-size: 10pt; line-height: 50%; font-family:
Arial;">. El <span class="SpellE">Oliveral</span> C/”H” <span
class="SpellE">esq.</span> C/”K”</span></b></p>

When atmail generates XML from it and sends to the browser it incorrectly converts HTML symbol
” (right quote) to an invalid Unicode sequence.

We are going to file the bug to atmail developers. Meanwhile, use one of the browsers that ignore the invalid symbols in XML as a workaround. So the problem is on Atmail side and it is reported.
 
Also this problem can be related to PHP version. If you have updated PHP from atomic repository - it can lead to problems with Atmail operation.
 
In /var/www/atmail/libs/Atmail/SQL.php, line 50 comment out this line:

$this->debug = $pref['debug_sql'];

That solves the issue. This bug is known by Parallels, but they dont seem to care enough to fix it. BEcause of that, at each Atmail upgrade from Parallels the bug resurfaces and you have to comment out line 50 again
 
This was really helpful and solved the issue for me. Parallels: please make this change in future releases.
 
I just started getting this error a few days ago (or my clients did)

The comment out works, but then i remembered that i had to set display error reporting on in php an also startup error reporting, for the whole server. (it dont work when i do it on a single domain :-( ) a few days ago.

I don't know if that is why it suddenly displays the error? Probably... Just a thought. It seems to send email all right even though it pops up the error message.

So a quick question. The commenting out, is that security risk? I mean does this line do some security check i need to worry about?
 
Last edited:
I have configured atmail and archivevault but unable to get mails in the archivevault.
 
Back
Top