Re: Fresh install misses autostart of daemon and faxgetty
Bodo Meißner <[email protected]> Wed, 05 Dec 2018 13:26:29 +0100
| Newsgroups | gmane.comp.telephony.fax.hylafax.user |
|---|---|
| Message-ID | <[email protected]> |
Hello Carsten, what looks strange to me is the double charset/encoding specification both in the subject header and in the body. Carsten <[email protected]> wrote: [...] > For some strange reason, the subject in the sent report is still > displayed in UTF-8 code. Not sure, if this is related to hylafax, > but here is the source code of the received notification: > "... > Return-Path: <[hylafax admin]> > Delivered-To: [sender of fax] > Received: by [postfix server] (Postfix, from userid 10) > id CE3FE44413; Wed, 5 Dec 2018 11:59:40 +0100 (CET) > MIME-Version: 1.0 > Content-Type: Multipart/Mixed; Boundary="NextPart13551" > Content-Transfer-Encoding: 7bit > To: [Sender of fax] > From: [hylafax admin] > Subject: =?ISO-8859-1?Q?=3D=3FUTF=2D8=3FB=3Fw4TDhMOEw4TDnMOcw5zDnMOWw5bDl?= "=?ISO-8859-1?Q?" specifies ISO-8859-1 charset with quoted-printable encoding. "?=" marks the end of the text in this charset/encoding The start of the text is "=3D=3FUTF=2D8=3FB=3F" which is the encoding of "=?UTF-8?B?" which would be a specification of UTF-8 charset with base64 encoding. There is only one "?=" at the end, not an additional encoded end marker which would be "=3F=3D". Similar specification in the body: > Content-Type: text/plain; charset=ISO-8859-1 > Content-Transfer-Encoding: quoted-printable > > =3D?UTF-8?B?w4TDhMOEw4TDnMOcw5zDnMOWw5bDlsOWw5bDpMOkw6TDpMO2w7bDtsO2?=3D an= > 069[faxnumber] wurde erfolgreich abgeschlossen. Here only the "=" needs encoding, so we basically have the encoded version of "=?UTF-8?B?w4TDhMOEw4TDnMOcw5zDnMOWw5bDlsOWw5bDpMOkw6TDpMO2w7bDtsO2?= an= 069[faxnumber] wurde erfolgreich abgeschlossen." with a matching pair of start/end markers. I don't know if it's allowed to use nested charset/encoding specification. I suggest to check the charset and encoding of the template files and the scripts involved in sending the mail. Maybe something in the preparation or processing of the mail tries to encode an already encoded text. IIRC the template mechanisms in HylaFAX and HylaFAX+ are based on different concepts. Did you mix template files and scripts from both variants? Bodo ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe [email protected] < /dev/null *To learn about commercial HylaFAX(tm) support, mail [email protected].*