Re: [hylafax-users] hylafax, TAP pagers and control characters

[Paul Haldane <Paul.Haldane@xxxxxxxxxxxxxxx>]

Aidan Van Dyk wrote:
> * Paul Haldane <Paul.Haldane@xxxxxxxxxxxxxxx> [050125 09:53]:
>
> > [using Hylafax 4.2.1 on Solaris 7]
> >
> > The paging service we're just started using (vodafone in the UK) won't 
> > accept messages via their dialup TAP service which contain a newline in 
> > the body of the message - fails with INVALID MESSAGE ...
> >
> > <-- <25:\002XXXXXXXX\015hello\012\015\00347;\015>
> > --> <32:ID XXXXXXXXX/INVALID MESSAGE >
> >
> > That's the result of doing ...
> >
> > echo hello | sendpage -p v1
>
> How about:
>   echo -n hello | sendpage -p v1
...

There seems to be an issue with communication between the client and the 
server if you try that - it comes back with the message with the request 
id but never actually runs the job - as far as I can tell the body of 
the message is never accepted by the Hylafax server.

Of course there are lots of ways to work round this problem (for example 
sendpage -p v1 `cat /etc/motd` works fine).  _However_ I'd rather not 
have to tweak the scripts which use sendpage if this can be fixed at the 
server end.  If the protocol says that the TAP client shouldn't send 
unescaped linefeeds as part of the message then it really shouldn't - 
even if many (most?) TAP servers don't seem to care :->

Paul

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