General discussion of the Hylafax fax program

Lee Howard | 1 Feb 15:57

Re: chopped pages

Jonathan Filbert wrote:
> Could anyone help me figure out what is happening here? Pages received 
> are often chopped. Setting MaxConsecutiveBadLines: 0 
> and PercentGoodLines: 0 has helped tremendously, but incoming pages 
> are still chopped with far greater frequency than I would prefer. None 
> of our "physical" fax machines ever have this issue - they have been 
> 100% reliable on the same lines as hylafax.

So by disabling copy-quality checking you have "helped tremendously"?  
That only has an effect on non-ECM faxes.  You normally wouldn't get 
enough non-ECM faxes to even notice the effect of disabling copy-quality 
checking... and normally the consequence of disabling copy-quality 
checking would merely be that you can get some non-ECM faxes where there 
are illegible pages and where the sender does not retransmit the page in 
the same fax.  The fact that you've noticed an improvement by disabling 
copy-quality checking leads me to believe that 1) you're getting an 
unusually large number of non-ECM faxes, and 2) there is some kind of 
issue with your modem or fax line which results in the modem 
demodulating poorly.

> We normally receive faxes fine from this sender, however I just added 
> Class1HasRHConnectBug: yes in attempt to fix the FCS error/modem 
> command error which appear very frequently in log files. 

As I think that your modem is using a Conexant chipset I don't think 
that "Class1RHConnectBug: yes" should be used.  I only know of this bug 
occurring on Lucent/Agere/LSI chipsets.  I doubt that you're doing much 
harm by having this configuration, but I also don't think that it is 
doing you any good.

(Continue reading)

headers

malcolm.serpis | 1 Feb 14:31

Compatible Modems for use with Hylafax Server

Hi,

I am not new to using Hylafax. I have used it for many years at various sites.

Typically it works well but compatible modems always seem to be an issue.

Presently I am trying to use a Dynalink 1456vqe serial modem. Whilst it seems to operate

reasonably, at times the modem will hang or not complete the job with errors such as

No response to PPS. When it hangs a restart of Hylafax server seems to correct it until the next time.

I tried using the TP560 config as per the hylafax config template but now I am using config below.

I am using the latest Hylafax Server 6.0.5 (installed from source)

OS is Ubuntu 10.04.3 LTS

I would like to get this error resolved so the solution is reliable but moreso would like to get an idea

of which modems in Australia are compatible with Hylafax. There are not many serial modems available.

I have tried internal modems with no success and have not tried any usb modems as yet.

Any advice would be appreciated.

Thanks,

Malcolm

Modem config in use:

ModemType:              Class1
ModemRate:              19200
ModemFlowControl:       xonxoff
Class1Cmd:              AT+FCLASS=1     # command to enter class 1
Class1PPMWaitCmd:       AT+FTS=7        # command to stop and wait before PPM
Class1TCFWaitCmd:       AT+FTS=7        # command to stop and wait before TCF
Class1EOPWaitCmd:       AT+FTS=9        # command to stop and wait before EOP
Class1SwitchingCmd:     AT+FRS=7        # silence between HDLC recv and trans
Class1RecvAbortOK:      200             # wait 200ms for abort response
Class1FrameOverhead:    4               # 4 byte overhead in recvd HDLC frames
Class1RecvIdentTimer:   40000           # 35+5secs waiting for ident frames
Class1TCFMaxNonZero:    10              # max 10% of data may be non-zero
Class1TCFMinRun:        1000            # min run is 2/3rds of TCF duration
Class1TCFResponseDelay: 75   # 75ms delay between recv TCF & response
Class1SendMsgDelay: 75   # 75ms delay after training
Class1SwitchingDelay: 150   # 150ms delay in switching transmission direction
Class1TrainingRecovery: 1500   # 1.5sec delay after training failure
Class1SwitchingCmd:     "<delay\0727>" # assumption: +FRS not supported

Log errors like below:

Feb 01 12:24:31.15: [19885]: SESSION BEGIN 000000516 612xxx
Feb 01 12:24:31.15: [19885]: HylaFAX (tm) Version 6.0.5
Feb 01 12:24:31.15: [19885]: SEND FAX: JOB 207 DEST 02xxx COMMID 000000516 DEVICE '/dev/ttyUSB0' FROM 'ACRFAX <ACRFAX <at> xxx.xxx>' USER nobody
Feb 01 12:24:31.15: [19885]: <-- [12:AT+FCLASS=1\r]
Feb 01 12:24:31.25: [19885]: --> [2:OK]
Feb 01 12:24:31.26: [19885]: DIAL 0288399099
Feb 01 12:24:31.26: [19885]: <-- [15:ATDT02xxxx\r]
Feb 01 12:24:49.34: [19885]: --> [7:CONNECT]
Feb 01 12:24:50.44: [19885]: --> [2:OK]
Feb 01 12:24:50.44: [19885]: REMOTE NSF "00 00 11 80 00 8A 48 00 01 08 80 80 80 00"
Feb 01 12:24:50.44: [19885]: NSF remote fax equipment: Canon Laser Class 2060
Feb 01 12:24:50.44: [19885]: <-- [9:AT+FRH=3\r]
Feb 01 12:24:50.46: [19885]: --> [7:CONNECT]
Feb 01 12:24:51.15: [19885]: --> [2:OK]
Feb 01 12:24:51.15: [19885]: REMOTE CSI "+61 2 xxxx"
Feb 01 12:24:51.15: [19885]: <-- [9:AT+FRH=3\r]
Feb 01 12:24:51.16: [19885]: --> [7:CONNECT]
Feb 01 12:24:51.58: [19885]: --> [2:OK]
Feb 01 12:24:51.58: [19885]: REMOTE best rate 33600 bit/s
Feb 01 12:24:51.58: [19885]: REMOTE max A3 page width (303 mm)
Feb 01 12:24:51.58: [19885]: REMOTE max unlimited page length
Feb 01 12:24:51.58: [19885]: REMOTE best vres R16 x 15.4 line/mm
Feb 01 12:24:51.58: [19885]: REMOTE format support: MH, MR, MMR, JBIG
Feb 01 12:24:51.58: [19885]: REMOTE supports T.30 Annex A, 256-byte ECM
Feb 01 12:24:51.58: [19885]: REMOTE best 0 ms/scanline
Feb 01 12:24:51.58: [19885]: USE 14400 bit/s
Feb 01 12:24:51.58: [19885]: USE error correction mode
Feb 01 12:24:51.58: [19885]: SEND file "docq/doc364.pdf;c0"
Feb 01 12:24:51.58: [19885]: USE A4 page width (215 mm)
Feb 01 12:24:51.58: [19885]: USE unlimited page length
Feb 01 12:24:51.58: [19885]: USE 3.85 line/mm
Feb 01 12:24:51.58: [19885]: USE 2-D MMR
Feb 01 12:24:51.58: [19885]: USE 0 ms/scanline
Feb 01 12:24:51.58: [19885]: SEND training at v.17 14400 bit/s
Feb 01 12:24:51.58: [19885]: DELAY 70 ms
Feb 01 12:24:51.66: [19885]: <-- [9:AT+FTH=3\r]
Feb 01 12:24:51.70: [19885]: --> [7:CONNECT]
Feb 01 12:24:51.70: [19885]: <-- data [23]
Feb 01 12:24:51.70: [19885]: <-- data [2]
Feb 01 12:24:51.73: [19885]: --> [7:CONNECT]
Feb 01 12:24:51.73: [19885]: <-- data [7]
Feb 01 12:24:51.73: [19885]: <-- data [2]
Feb 01 12:24:53.93: [19885]: --> [2:OK]
Feb 01 12:24:53.93: [19885]: <-- [9:AT+FTS=7\r]
Feb 01 12:24:53.94: [19885]: --> [2:OK]
Feb 01 12:24:53.94: [19885]: <-- [11:AT+FTM=145\r]
Feb 01 12:24:55.61: [19885]: --> [7:CONNECT]
Feb 01 12:24:55.61: [19885]: <-- data [1024]
Feb 01 12:24:55.61: [19885]: <-- data [1024]
Feb 01 12:24:56.02: [19885]: <-- data [652]
Feb 01 12:24:56.36: [19885]: <-- data [2]
Feb 01 12:24:57.17: [19885]: --> [2:OK]
Feb 01 12:24:57.17: [19885]: <-- [9:AT+FRH=3\r]
Feb 01 12:24:57.69: [19885]: --> [7:CONNECT]
Feb 01 12:24:58.80: [19885]: --> [2:OK]
Feb 01 12:24:58.80: [19885]: TRAINING succeeded
Feb 01 12:24:58.80: [19885]: SEND begin page
Feb 01 12:24:58.82: [19885]: SEND send frame number 0
Feb 01 12:24:58.82: [19885]: SEND send frame number 1
Feb 01 12:24:58.82: [19885]: SEND send frame number 2
Feb 01 12:24:58.82: [19885]: SEND send frame number 3
Feb 01 12:24:58.82: [19885]: SEND send frame number 4
Feb 01 12:24:58.82: [19885]: SEND send frame number 5
Feb 01 12:24:58.82: [19885]: SEND send frame number 6
Feb 01 12:24:58.83: [19885]: SEND send frame number 7
Feb 01 12:24:58.83: [19885]: SEND send frame number 8
Feb 01 12:24:58.83: [19885]: SEND send frame number 9
Feb 01 12:24:58.83: [19885]: SEND send frame number 10
Feb 01 12:24:58.83: [19885]: SEND send frame number 11
Feb 01 12:24:58.83: [19885]: SEND send frame number 12
Feb 01 12:24:58.83: [19885]: SEND send frame number 13
Feb 01 12:24:58.83: [19885]: SEND send frame number 14
Feb 01 12:24:58.83: [19885]: SEND send frame number 15
Feb 01 12:24:58.83: [19885]: SEND send frame number 16
Feb 01 12:24:58.83: [19885]: SEND send frame number 17
Feb 01 12:24:58.83: [19885]: SEND send frame number 18
Feb 01 12:24:58.83: [19885]: SEND send frame number 19
Feb 01 12:24:58.83: [19885]: SEND send frame number 20
Feb 01 12:24:58.83: [19885]: SEND send frame number 21
Feb 01 12:24:58.83: [19885]: SEND send frame number 22
Feb 01 12:24:58.83: [19885]: SEND send frame number 23
Feb 01 12:24:58.83: [19885]: SEND send frame number 24
Feb 01 12:24:58.83: [19885]: SEND send frame number 25
Feb 01 12:24:58.83: [19885]: SEND send frame number 26
Feb 01 12:24:58.83: [19885]: SEND send frame number 27
Feb 01 12:24:58.83: [19885]: SEND send frame number 28
Feb 01 12:24:58.83: [19885]: SEND send frame number 29
Feb 01 12:24:58.83: [19885]: SEND send frame number 30
Feb 01 12:24:58.83: [19885]: SEND send frame number 31
Feb 01 12:24:58.83: [19885]: SEND send frame number 32
Feb 01 12:24:58.83: [19885]: SEND send frame number 33
Feb 01 12:24:58.83: [19885]: SEND send frame number 34
Feb 01 12:24:58.83: [19885]: SEND send frame number 35
Feb 01 12:24:58.83: [19885]: SEND send frame number 36
Feb 01 12:24:58.83: [19885]: SEND send frame number 37
Feb 01 12:24:58.83: [19885]: SEND send frame number 38
Feb 01 12:24:58.83: [19885]: SEND send frame number 39
Feb 01 12:24:58.83: [19885]: SEND send frame number 40
Feb 01 12:24:58.83: [19885]: SEND send frame number 41
Feb 01 12:24:58.83: [19885]: SEND send frame number 42
Feb 01 12:24:58.83: [19885]: SEND send frame number 43
Feb 01 12:24:58.83: [19885]: SEND send frame number 44
Feb 01 12:24:58.83: [19885]: SEND send frame number 45
Feb 01 12:24:58.83: [19885]: SEND send frame number 46
Feb 01 12:24:58.83: [19885]: SEND send frame number 47
Feb 01 12:24:58.83: [19885]: SEND send frame number 48
Feb 01 12:24:58.83: [19885]: SEND send frame number 49
Feb 01 12:24:58.83: [19885]: SEND send frame number 50
Feb 01 12:24:58.83: [19885]: SEND send frame number 51
Feb 01 12:24:58.83: [19885]: SEND send frame number 52
Feb 01 12:24:58.83: [19885]: SEND send frame number 53
Feb 01 12:24:58.83: [19885]: SEND send frame number 54
Feb 01 12:24:58.83: [19885]: SEND send frame number 55
Feb 01 12:24:58.83: [19885]: SEND send frame number 56
Feb 01 12:24:58.83: [19885]: SEND send frame number 57
Feb 01 12:24:58.83: [19885]: SEND send frame number 58
Feb 01 12:24:58.83: [19885]: SEND send frame number 59
Feb 01 12:24:58.83: [19885]: SEND send frame number 60
Feb 01 12:24:58.83: [19885]: SEND send frame number 61
Feb 01 12:24:58.83: [19885]: SEND send frame number 62
Feb 01 12:24:58.83: [19885]: SEND send frame number 63
Feb 01 12:24:58.83: [19885]: SEND send frame number 64
Feb 01 12:24:58.83: [19885]: SEND send frame number 65
Feb 01 12:24:58.83: [19885]: SEND send frame number 66
Feb 01 12:24:58.83: [19885]: SEND send frame number 67
Feb 01 12:24:58.83: [19885]: SEND send frame number 68
Feb 01 12:24:58.83: [19885]: SEND send frame number 69
Feb 01 12:24:58.83: [19885]: SEND send frame number 70
Feb 01 12:24:58.83: [19885]: SEND send frame number 71
Feb 01 12:24:58.83: [19885]: SEND send frame number 72
Feb 01 12:24:58.84: [19885]: SEND send frame number 73
Feb 01 12:24:58.84: [19885]: SEND send frame number 74
Feb 01 12:24:58.84: [19885]: DELAY 70 ms
Feb 01 12:24:58.91: [19885]: <-- [11:AT+FTM=146\r]
Feb 01 12:24:59.41: [19885]: --> [7:CONNECT]
Feb 01 12:24:59.41: [19885]: <-- data [1032]
Feb 01 12:24:59.41: [19885]: <-- data [1029]
Feb 01 12:24:59.81: [19885]: <-- data [1034]
Feb 01 12:25:00.35: [19885]: <-- data [1031]
Feb 01 12:25:00.89: [19885]: <-- data [1047]
Feb 01 12:25:01.43: [19885]: <-- data [1037]
Feb 01 12:25:02.00: [19885]: <-- data [1033]
Feb 01 12:25:02.54: [19885]: <-- data [1038]
Feb 01 12:25:03.07: [19885]: <-- data [1034]
Feb 01 12:25:03.61: [19885]: <-- data [1039]
Feb 01 12:25:04.15: [19885]: <-- data [1036]
Feb 01 12:25:04.69: [19885]: <-- data [1033]
Feb 01 12:25:05.26: [19885]: <-- data [1031]
Feb 01 12:25:05.80: [19885]: <-- data [1039]
Feb 01 12:25:06.34: [19885]: <-- data [1041]
Feb 01 12:25:06.88: [19885]: <-- data [1040]
Feb 01 12:25:07.41: [19885]: <-- data [1049]
Feb 01 12:25:07.99: [19885]: <-- data [1052]
Feb 01 12:25:08.52: [19885]: <-- data [1036]
Feb 01 12:25:09.06: [19885]: <-- data [1037]
Feb 01 12:25:09.63: [19885]: <-- data [29]
Feb 01 12:25:09.63: [19885]: <-- data [2]
Feb 01 12:25:11.08: [19885]: --> [2:OK]
Feb 01 12:25:11.08: [19885]: <-- [9:AT+FTS=7\r]
Feb 01 12:25:11.09: [19885]: --> [2:OK]
Feb 01 12:25:11.09: [19885]: <-- [9:AT+FTH=3\r]
Feb 01 12:25:11.14: [19885]: --> [7:CONNECT]
Feb 01 12:25:11.14: [19885]: <-- data [7]
Feb 01 12:25:11.14: [19885]: <-- data [2]
Feb 01 12:25:12.56: [19885]: --> [2:OK]
Feb 01 12:25:12.56: [19885]: SEND send PPS (partial page signal)
Feb 01 12:25:12.56: [19885]: SEND send MPS (more pages, same document)
Feb 01 12:25:12.56: [19885]: <-- [9:AT+FRH=3\r]
Feb 01 12:25:12.81: [19885]: --> [7:CONNECT]
Feb 01 12:25:17.49: [19885]: --> [2:OK]
Feb 01 12:25:17.49: [19885]: HDLC frame too short (0 bytes)
Feb 01 12:25:17.49: [19885]: <-- [9:AT+FTH=3\r]
Feb 01 12:25:17.55: [19885]: --> [7:CONNECT]
Feb 01 12:25:17.55: [19885]: <-- data [7]
Feb 01 12:25:17.55: [19885]: <-- data [2]
Feb 01 12:25:18.97: [19885]: --> [2:OK]
Feb 01 12:25:18.97: [19885]: SEND send PPS (partial page signal)
Feb 01 12:25:18.97: [19885]: SEND send MPS (more pages, same document)
Feb 01 12:25:18.97: [19885]: <-- [9:AT+FRH=3\r]
Feb 01 12:25:19.23: [19885]: --> [7:CONNECT]
Feb 01 12:25:20.61: [19885]: --> [2:OK]
Feb 01 12:25:20.61: [19885]: HDLC frame too short (0 bytes)
Feb 01 12:25:20.61: [19885]: <-- [9:AT+FTH=3\r]
Feb 01 12:25:20.66: [19885]: --> [7:CONNECT]
Feb 01 12:25:20.66: [19885]: <-- data [7]
Feb 01 12:25:20.66: [19885]: <-- data [2]
Feb 01 12:25:22.09: [19885]: --> [2:OK]
Feb 01 12:25:22.09: [19885]: SEND send PPS (partial page signal)
Feb 01 12:25:22.09: [19885]: SEND send MPS (more pages, same document)
Feb 01 12:25:22.09: [19885]: <-- [9:AT+FRH=3\r]
Feb 01 12:25:22.35: [19885]: --> [7:CONNECT]
Feb 01 12:25:23.76: [19885]: --> [2:OK]
Feb 01 12:25:23.76: [19885]: HDLC frame too short (0 bytes)
Feb 01 12:25:23.76: [19885]: No response to PPS repeated 3 times.
Feb 01 12:25:23.76: [19885]: SEND end page
Feb 01 12:25:23.76: [19885]: DELAY 70 ms
Feb 01 12:25:23.83: [19885]: <-- [9:AT+FTH=3\r]
Feb 01 12:25:23.88: [19885]: --> [7:CONNECT]
Feb 01 12:25:23.88: [19885]: <-- data [3]
Feb 01 12:25:23.88: [19885]: <-- data [2]
Feb 01 12:25:25.20: [19885]: --> [2:OK]
Feb 01 12:25:26.20: [19885]: <-- [5:ATH0\r]
Feb 01 12:25:26.30: [19885]: --> [10:NO CARRIER]
Feb 01 12:25:26.30: [19885]: MODEM No carrier
Feb 01 12:25:26.43: [19885]: SESSION END

headers

Vincent Medina | 1 Feb 23:07

UID purpose

I am trying to understand what the userid number purpose is.

Can anyone please enlighten me.

Faxadduser – p password –u UserID Username –a Admin Pass

headers

Jay Lam | 2 Feb 17:15

hylafax 5.5.1 error install...dependency on libldap2

To all Hylafax users:

O/S: Debian Squeeze

Install: Hylafax+ 5.5.1

I get an error message when installing hylafax+.  I get an libldap2 is
not installed.  There is no libldap2.  I have installed libldap-2.4-2
and libldap2-dev.

Here is my output:

root <at> hylafax-plus:/tmp# dpkg -i hylafax_5.5.1-1_i386.deb
Selecting previously deselected package hylafax.
(Reading database ... 23694 files and directories currently installed.)
Unpacking hylafax (from hylafax_5.5.1-1_i386.deb) ...
dpkg: dependency problems prevent configuration of hylafax:
 hylafax depends on libldap2; however:
  Package libldap2 is not installed.
dpkg: error processing hylafax (--install):
 dependency problems - leaving unconfigured
Processing triggers for man-db ...
Errors were encountered while processing:
 hylafax

root <at> hylafax-plus:/tmp# dpkg --get-selections | grep ldap
libldap-2.4-2                    install
libldap2-dev                    install
root <at> hylafax-plus:/tmp#

On 12-01-30 12:44 PM, Lee Howard wrote:
> Jay Lam wrote:
>> To all Hylafax users:
>>
>> Scenario: Faxes cannot be received.  Hylafax listens for distinctive
>> rings, answers fax, receives data, but modem times out.
>>
>> Hylafax Version: 6.0.5
>>
>> Fax Modem: Multitech Agere OCM V.92 MT9234ZPX-PCIE Internal Data/Fax
>> Modem Version 1.02d which supports fax classes: 0,1,1.0,2,2.0,2.1,8
>>
>> Set Fax Class: 1.0
>
> HylaFAX+ 5.5.1 has a default prototype config file for that modem. 
> So, I'd suggest using HylaFAX+, re-running faxaddmodem, and seeing
> where you end up from there.
>
> http://hylafax.sourceforge.net
>
> Thanks,
>
> Lee.

____________________ 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 <at> hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales <at> ifax.com.*

headers

Lee Howard | 3 Feb 00:50

Re: Compatible Modems for use with Hylafax Server

malcolm.serpis <at> altronics.com.au wrote:
>
> Typically it works well but compatible modems always seem to be an issue.
>

I'm not sure that it has to do with modem compatibility with HylaFAX, 
but rather modem reliability for fax.  You can spend many years testing 
out one modem or another trying to find an off-the-shelf modem from your 
local retailer that will work well for fax, but the truth is that none 
of them probably do.

> I would like to get this error resolved so the solution is reliable 
> but moreso would like to get an idea
>
> of which modems in Australia are compatible with Hylafax. There are 
> not many serial modems available.
>
.....
>
> Class1SwitchingCmd:     "<delay\0727>"  # assumption: +FRS not supported
>

Any time you have to do this in your config file (so Topic and USR 
modems) means that you're not really going to be able to have a fine 
control of the silence duration on the line as required by the fax spec 
(ITU T.30).  Therefore, the software is required to simply impose a 
pause in operation with the hope that the modem was not making noises or 
that the other end wasn't making noises.  So for reliability you really 
don't want a modem that makes you do this kind of configuration.

> Feb 01 12:25:12.56: [19885]: <-- [9:AT+FRH=3\r]
> Feb 01 12:25:12.81: [19885]: --> [7:CONNECT]
> Feb 01 12:25:17.49: [19885]: --> [2:OK]
> Feb 01 12:25:17.49: [19885]: HDLC frame too short (0 bytes)
>

And that is just blatant misbehavior on the part of the modem.

Really, you can just look through the hylafax-users mailing list for a 
few weeks and see multiple e-mails about modem recommendations.  But my 
recommendations are always Mainpine IQ Express (which may not be 
available in Australia), Multitech MT5634/MT5656/MT5600/MT9234, or to 
use Asterisk with IAXmodem and some DAHDI-compatible hardware.

Thanks,

Lee.

____________________ 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 <at> hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales <at> ifax.com.*

headers

Lee Howard | 3 Feb 15:49

Re: UID purpose

Vincent Medina wrote:
>
> I am trying to understand what the userid number purpose is.
>
> Can anyone please enlighten me.
>
> Faxadduser – p password –u UserID Username –a Admin Pass
>

 From the hosts.hfaxd man page:

uid The numerical user ID to assign to clients that use the entry for 
access.
hfaxd uses the uid to control access to server resources such as jobs and
documents (the value is used to set the group ID of files created by a 
client).

Multiple clients/users may share the same uid or unique IDs may be
created for each client. User IDs may be any number in the range [0..60002]
with 60002 used, by convention, for entries that do not have a uid 
specified.

Consequently, this uid can come into play for features such as 
JobProtection and RecvqProtection. See: 
http://hylafax.sourceforge.net/man/hfaxd.php

Thanks,

Lee.

____________________ 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 <at> hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales <at> ifax.com.*

headers

Javivi | 3 Feb 13:58

Embed image in notify email

Hi, Are there any way to embed the PDF fax in the body of notify email?

Thanks

headers

Javivi | 3 Feb 14:16

Embed image in notify email

Hi, Are there any way to embed the PDF fax in the body of notify email?

Thanks

headers

Vincent Medina | 3 Feb 18:20

Re: UID purpose

If I do not assign a userID and only a username will outbound faxes and
incoming be specifically for the individual? i.e. the client will not have
access to them in the logs? Is this best practice? Or should I create
userid's to group departments and create userid's unique to individuals? 

Let's say:

100 <at> acct_jane
100 <at> acct_joe
100 <at> acct_bill

They will have access to all faxes related to userid 100

101 <at> sales_dick
101 <at> sales_mark
101 <at> sales_aldo

They will have access to all faxes related to userid 101 but not 100

102 <at> private_kevin (No other user... so this user is private)

103 <at> private_pat (Same as above)

Is my thinking correct here?

TIA

-----Original Message-----
From: hylafax-users-bounce <at> hylafax.org
[mailto:hylafax-users-bounce <at> hylafax.org] On Behalf Of Lee Howard
Sent: Friday, February 03, 2012 9:49 AM
To: Vincent Medina
Cc: hylafax-users <at> hylafax.org
Subject: Re: [hylafax-users] UID purpose

Vincent Medina wrote:
>
> I am trying to understand what the userid number purpose is.
>
> Can anyone please enlighten me.
>
> Faxadduser - p password -u UserID Username -a Admin Pass
>

 From the hosts.hfaxd man page:

uid The numerical user ID to assign to clients that use the entry for 
access.
hfaxd uses the uid to control access to server resources such as jobs and
documents (the value is used to set the group ID of files created by a 
client).

Multiple clients/users may share the same uid or unique IDs may be
created for each client. User IDs may be any number in the range [0..60002]
with 60002 used, by convention, for entries that do not have a uid 
specified.

Consequently, this uid can come into play for features such as 
JobProtection and RecvqProtection. See: 
http://hylafax.sourceforge.net/man/hfaxd.php

Thanks,

Lee.

____________________ 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 <at> hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales <at> ifax.com.*

____________________ 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 <at> hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales <at> ifax.com.*

headers

Lee Howard | 3 Feb 18:31

Re: hylafax 5.5.1 error install...dependency on libldap2

Jay Lam wrote:
> To all Hylafax users:
>
> O/S: Debian Squeeze
>
> Install: Hylafax+ 5.5.1
>
> I get an error message when installing hylafax+.  I get an libldap2 is
> not installed.  There is no libldap2.  I have installed libldap-2.4-2
> and libldap2-dev.
>   

You're probably trying to install the deb built for 4.0 which uses 
slightly different names.  Try this one:

https://sourceforge.net/projects/hylafax/files/hylafax%20Debian%20Squeeze%206.0.4/

Thanks,

Lee.

____________________ 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 <at> hylafax.org < /dev/null
  *To learn about commercial HylaFAX(tm) support, mail sales <at> ifax.com.*

37	May 2012
75	April 2012
83	March 2012
93	February 2012
37	January 2012
62	December 2011
98	November 2011
102	October 2011
80	September 2011
63	August 2011
109	July 2011
173	June 2011
94	May 2011
164	April 2011
146	March 2011
60	February 2011
148	January 2011
175	December 2010
156	November 2010
149	October 2010
237	September 2010
145	August 2010
101	July 2010
153	June 2010
201	May 2010
175	April 2010
203	March 2010
275	February 2010
181	January 2010
167	December 2009
196	November 2009
353	October 2009
207	September 2009
186	August 2009
242	July 2009
294	June 2009
220	May 2009
218	April 2009
195	March 2009
250	February 2009
159	January 2009
216	December 2008
231	November 2008
283	October 2008
253	September 2008
262	August 2008
230	July 2008
216	June 2008
207	May 2008
287	April 2008
307	March 2008
400	February 2008
556	January 2008
341	December 2007
338	November 2007
389	October 2007
373	September 2007
459	August 2007
356	July 2007
326	June 2007
361	May 2007
374	April 2007
536	March 2007
500	February 2007
412	January 2007
324	December 2006
352	November 2006
452	October 2006
446	September 2006
436	August 2006
443	July 2006
571	June 2006
560	May 2006
409	April 2006
397	March 2006
398	February 2006
467	January 2006
307	December 2005
490	November 2005
363	October 2005
422	September 2005
400	August 2005
366	July 2005
520	June 2005
377	May 2005
425	April 2005
483	March 2005
528	February 2005
424	January 2005
353	December 2004
501	November 2004
428	October 2004
397	September 2004
447	August 2004
405	July 2004
422	June 2004
446	May 2004
386	April 2004
613	March 2004
422	February 2004
316	January 2004
409	December 2003
336	November 2003
439	October 2003
409	September 2003
355	August 2003
465	July 2003
400	June 2003
492	May 2003
375	April 2003
375	March 2003
394	February 2003
358	January 2003
225	December 2002
354	November 2002
511	October 2002
20	September 2002
2	December 2001

Mon	Tue	Wed	Thu	Fri	Sat	Sun

		1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29