![]() |
Thanks Martin, you are right, in my case it was an issue of running "faxsetup" after upgrade from 4.1.8 to 4.2.0 on Gentoo. I even found notes in log files after upgrades: * Hylafax now depends on sharutils instead of metamail for mime * handling, however, you can continue to use the latter if you * like (emerge metamail manually). * Now run faxsetup and (if necessary) faxaddmodem. -- #Joseph [snip] > First off, as requested when you joined the list > (http://www.hylafax.org/mailing-lists.php) > > "when corresponding about this software please always specify: > > * what version you have (check here > <http://www.hylafax.org/version.php> if you are unsure of your > software version), > * what system you're running on, (if Linux then please include the > distribution) and, > * if the problem is modem-related, identify the modem and the > firmware revision." > > > > > Anyway, if you are on Hylafax 4.2.0, it is probably the base64 issue. > See the list archives from November 16, 2004: > > http://www.hylafax.org/archive/2004-11/msg00283.php > > I think I've also noticed that if you run faxsetup after upgrading from > 4.1.8 to 4.2.0 (as you're supposed to) I think it re-writes the > ENCODING=base64 line in setup.cache. So if I'm not mistaken, this is > not strictly a bug, it could be called "user error". > > Cheers. > ____________________ HylaFAX(tm) Users Mailing List _______________________ To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*