• 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.

Watchdog small wrong date parse error

GunFood

Basic Pleskian
Hello,

i got some watchdog error messages while playing around with my mysql server (which is ok), but I've seen a parsing error:

Date: %Mon, 09 Jul 2012 15:21:00 +0200

So horde is unable to display the time and date in webmail. maybe a small fix would be great.

Thanks

Gun-Food
 

Attachments

  • Untitled.png
    Untitled.png
    4.5 KB · Views: 6
Have you set your own timezone in /etc/php.ini and in Tools & Settings -> System Time?
 
/etc/php.ini
Code:
[Date]
; Defines the default timezone used by the date functions
date.timezone = Europe/Berlin

Control panel is set to (GMT +2:00) Europe/Berlin
Time sync active (if important)

So I think no special settings.
I'm on CentOS 5.8 if needed.
 
@IgorG This bug is still present in Plesk 18.0.30 MU#1:
The mail headers of Watchdog emails contain this header:
Date: %Mon, 09 Jul 2012 15:21:00 +0200

The problem is the % sign, which should not be there when following the SMTP RFC.

I did not find out which component is in charge of sending the Watchdog messages. However, since a local monit instance that I run at home does not generate this bug, I would assume that it the problem linked to a Plesk component.
 
Back
Top