Re: [hylafax-users] sendfax "Can not open file"

[Duncan Turnbull <duncan@xxxxxxxxxxxxxx>]

I probably wasn't clear.

Hylafax is seeing "target" as the number to dial and user@... as the
reference to the file to send. Its the user part of user@123456789 that goes
onto the cover sheet. The parameter for -d needs to be a single value with
no spaces.

So it thinks you have told it to send the files user@123456789 and
fax-test.ps to the number target

Thus when it tries to open user@123456789 as the 1st file to send then it
can't and you get a cannot open file error

Cheers Duncan


> From: Trevor Jenkins <trevor.jenkins@xxxxxxxxxxxxxx>
> Date: Thu, 14 Jul 2005 09:44:18 +0000 (GMT)
> To: HylaFAX Users <hylafax-users@xxxxxxxxxxx>
> Subject: Re: [hylafax-users] sendfax "Can not open file"
> 
> On Thu, 14 Jul 2005, Duncan Turnbull <duncan@xxxxxxxxxxxxxx> wrote:
> 
>> I think its likely that the destination number is being read as "target" and
>> thinking the user@... is the file it should be sending to the number
>> "target"
> 
> Let me repeat this again it is not always the target that is included in
> the error messages. It doesn't seem to matter which options are included
> on the line sendfax randomly picks some portion of option arguments for
> the bogus error message -d just happens to be there for the near minimal
> test case.
> 
>> Why do you have target in your destination number?
> 
> According to the man page for sendfax the user part of the target is put
> on the cover page. Rather important when sending to a large corporate so
> they know which of their many employees the fax is intended for.
> 
>> ... I have had this error
>> before with sending and not having a single piece of text for the
>> destination.
> 
> But I know there is content in any and all of the files I tried. Even went
> so far as to use a complete file name all the way to /
> 
> If you're explanation were corect then the error messages are really
> screwed. It should report the name of the file causing the error not some
> random peice of text extracted from unrelated command line options.
> 
>> 
>> Cheers Duncan
>> 
>> 
>>> From: Trevor Jenkins <trevor.jenkins@xxxxxxxxxxxxxx>
>>> Date: Thu, 14 Jul 2005 08:59:15 +0000 (GMT)
>>> To: HylaFAX Users <hylafax-users@xxxxxxxxxxx>
>>> Subject: Re: [hylafax-users] sendfax "Can not open file"
>>> 
>>> On Thu, 14 Jul 2005, Pedro <procadas@xxxxxxxxx> wrote:
>>> 
>>>> --- Trevor Jenkins <trevor.jenkins@xxxxxxxxxxxxxx> wrote:
>>>> 
>>>>> When I try to use sendfax from the command line the fax is not queued
>>>>> for transmission. No matter what the options and file name given the
>>>>> program returns immediately with the error message "Can not open
>>>>> file". There is a prefix to the message, viz some part of one of the
>>>>> options. For the command
>>>>> 
>>>>> sendfax -s a4 -r "Test Transmission" -c "Test Transmission" -d "target
>>>>> user@01234567890" fax-test.ps
>>>>> 
>>>>> The full error reported is
>>>>> 
>>>>> Transmission" Can not open file
>>>>> 
>>>>> removing options until only the minimal command
>>>>> 
>>>>> sendfax -s a4 -d "target user@01234567890" fax-test.ps
>>>>> 
>>>>> is left and the error message is
>>>>> 
>>>>> user@01234567890" Can not open file
>>>>> 
>>>>> Me thinks something is screwed but as HylaFAX is clearly not returning
>>>>> the correct filename or error message it is impossible to know what.
>>>>> 
>>>> 
>>>> Nothing wrong with hylafax. Clearly, the sendfax
>>>> command doesn't know where/what user@01234567890 file
>>>> is.
>>> 
>>> There IS something wrong with HylaFX. If you bothered to read all the
>>> details then you'd see that it isn't just the -d option's data that
>>> may get included in the error message.
>>> 
>>>> 
>>>>> The file fax-test.pdf exists. I've tried it with a
>>>>> text file version. Same
>>>>> results.
>>>> 
>>>> .pdf or .ps? But it doesn't matter, if you insist
>>>> using "" to pass arguments to sendfax where they are
>>>> not expected.
>>> 
>>> I beg to differ. The man page for sendfax clearly has quotes for many of
>>> the options i used in my test.
>>> 
>>> Regards, Trevor
>>> 
>>> <>< Re: deemed!
>>> 
>>> 
>>> ____________________ 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*
>>> 
>>> 
>> 
>> 
>> 
>> ____________________ 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*
>> 
> 
> Regards, Trevor
> 
> <>< Re: deemed!
> 
> 
> ____________________ 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*
> 
> 



____________________ 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*