Re: Fresh install misses autostart of daemon and faxgetty

Am 04.12.18 um 23:08 schrieb Lee Howard:
> On 12/01/2018 01:48 PM, Carsten wrote:
>>
>> Am 01.12.18 um 18:11 schrieb Lee Howard:
>>> HylaFAX is highly configurable.=C2=A0 Unless you take care to mimic t=
he
>>> configuration and build that was done in your package-based installat=
ion
>>> there is a good chance that you'll find something is configured
>>> differently.
>>
>> Hi Lee and List,
>>
>> "highly configurable" mostly means "We havn't made any thoughts about
>> other environments than our DEV. So look for Yourself to get it on"
>>
>=20
> In this case it mostly means that the Debian package maintainers took
> considerable liberties to the standard HylaFAX installation in order to
> accommodate Debian packaging guidelines and add various features of
> convenience without working them in upstream.
>=20
> Compare that with the Fedora package which is, by comparison, quite pla=
in.
>=20
> That said, there is always room for improvement, and development
> contributions or meaningful constructive criticism besides sarcasm are
> always appreciated.
>=20
>> At this point I have to add some informations regarding the needs of
>> switching to the current version of hylafax.
>> I have had a bunch of trouble with german special characters sending a
>> fax (UTF-8 support).
>=20
> This was a bug.=C2=A0 However, I'm not sure how you were not encounteri=
ng
> these problems before since these bugs should have also been in your ol=
d
> version of faxmail.
>=20
> The bugs should be fixed with this commit:
>=20
> https://sourceforge.net/p/hylafax/HylaFAX+/2480/
>=20
> Thanks,
>=20
> Lee.

Hi Lee, List,
apologize for if somebody felt hurt about the little sarcasm.

Thanks to the trunk -I had to figure out, how to get it onto my machine,=20
in the sent document (Mail converted to PDF) it is now displayed correct.

For some strange reason, the subject in the sent report is still=20
displayed in UTF-8 code. Not sure, if this is related to hylafax, but=20
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=3D"NextPart13551"
Content-Transfer-Encoding: 7bit
To: [Sender of fax]
From: [hylafax admin]
Subject: =3D?ISO-8859-1?Q?=3D3D=3D3FUTF=3D2D8=3D3FB=3D3Fw4TDhMOEw4TDnMOcw=
5zDnMOWw5bDl?=3D
  =3D?ISO-8859-1?Q?sOWw5bDpMOkw6TDpMO2w7bDtsO2=3D3F=3D3D=3D20an=3D2006966=
814897005?=3D
  =3D?ISO-8859-1?Q?=3D20abgeschlossen?=3D
Message-Id: <[email protected]>
Date: Wed,  5 Dec 2018 11:59:38 +0100 (CET)

This is a multi-part message in MIME format.

--NextPart13551
Mime-Version: 1.0
Content-Type: text/plain; charset=3DISO-8859-1
Content-Transfer-Encoding: quoted-printable

=3D3D?UTF-8?B?w4TDhMOEw4TDnMOcw5zDnMOWw5bDlsOWw5bDpMOkw6TDpMO2w7bDtsO2?=3D=
3D an=3D
  069[faxnumber] wurde erfolgreich abgeschlossen.
..."

Any idea?
I have done a full "configure/make/make install" with the new trunk and=20
just updated the daemon file as documented before.

There is one "new" issue, but this is a new topic, I will address later=20
in a separate thread

br
Carsten

>=20
>=20
> ____________________ HylaFAX(tm) Users Mailing List ___________________=
____
>    To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg=
2.cgi
>   On UNIX: mail -s unsubscribe [email protected] < /dev=
/null
>    *To learn about commercial HylaFAX(tm) support, mail [email protected].=
*
>=20


____________________ HylaFAX(tm) Users Mailing List _____________________=
__
  To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.c=
gi
 On UNIX: mail -s unsubscribe [email protected] < /dev/nu=
ll
  *To learn about commercial HylaFAX(tm) support, mail [email protected].*