You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you have umlauts in the report messages defined by conf.php variables the conf file needs to be ansi encoded or will be displayed with wrong formatting in mail clients . Eg.
define('QUARANTINE_REPORT_FROM_NAME', 'MailWatch für MailScanner');
define('QUARANTINE_REPORT_SUBJECT', 'E-Mail Quarantäne-Bericht');
define('QUARANTINE_SUBJECT', 'Nachricht aus Quarantäne freigegeben');
define('QUARANTINE_MSG_BODY', 'Dies ist eine automatisierte Mail.
Die ursprüngliche E-Mail befindet sich im Anhang dieser Mail.
Mit freundlichen Grüßen,
Eure IT');
will result in the following mail body if the conf file encoding is utf-8
Dies ist eine automatisierte Mail.
Die ursprüngliche E-Mail befindet sich im Anhang dieser Mail.
Mit freundlichen GrüÃYen,
Eure IT
Thats because the mail encoding defined by the mail headers are "ISO-8859-1" in mailscanner/lib/pear/Mail/mime.php
The text was updated successfully, but these errors were encountered:
Yes working now with utf-8 encoding.
Problem could be that ANSI/ISO-8859-1 encoding is not working anymore so that people who adjusted the conf file in the past to be ANSI encoded will get the character garbage when they will update MailWatch
Right. I'm going to implement https://github.com/neitanod/forceutf8 for this case to convert safely to utf8, once this library is in place it can be used in other sections of the actual code that deal with unknown encoding (e.g.: email subject or headers)
If you have umlauts in the report messages defined by conf.php variables the conf file needs to be ansi encoded or will be displayed with wrong formatting in mail clients . Eg.
will result in the following mail body if the conf file encoding is utf-8
Thats because the mail encoding defined by the mail headers are "ISO-8859-1" in mailscanner/lib/pear/Mail/mime.php
The text was updated successfully, but these errors were encountered: