Re: [hylafax-users] truncation of embedded sender info?

[Curtis Rempel <Curtis.Rempel@corp.shaw.ca>]

Yes, that is exactly the behavior I am observing: truncation at 20
characters.

It's not that big of a deal, but I thought if it was configurable, I'd
change it.

Does anybody else know if this is intentional or a protocol limit?

Curtis

-----Original Message-----
From: Lee Howard [mailto:faxguy@deanox.com]
Sent: May 16, 2001 4:23 PM
To: Curtis Rempel; 'hylafax-users@hylafax.org'
Subject: Re: [hylafax-users] truncation of embedded sender info?


At 03:59 PM 5/16/01 -0600, Curtis Rempel wrote:
>I'm running 4.1b3 on both sending and receiving systems.  The incoming fax
>is delivered via email as a tiff image without problem.
>
>The only glitch is that the sender info is truncated in the subject and
body
>of the email.  From the script, this info is yanked from the tiff image
>using faxinfo.  A manual edit of the tiff file confirms that faxinfo is
>doing its job properly as what appears in the tiff file is what faxinfo
>reports.  So, I guess that the sending system is somehow truncating this
>field when it is embedded.  The tiff attachment opens correctly and
displays
>the proper full length sender info at the top of each page, it's just that
>the email subject/body parts have truncated sender info.
>
>Is there a length restriction to this field when it is embedded on the
>sending system?  I've tried to figure out where exactly in the chain of
>events this happens but haven't got very far yet.

I think I know what you're describing, and the limit is with faxgetty, not
the sending system.  faxinfo is only reporting the first 20-chars of the
sender's ID string because that's all that faxgetty can handle for a TSID
string.  If this is intentional or because of a protocol limit, I don't
know.

Lee.


____________________ HylaFAX(tm) Users Mailing List _______________________
 To unsub: mail -s unsubscribe hylafax-users-request@hylafax.org < /dev/null