Re: [hylafax-users] Generating lousy performance

[Lee Howard <faxguy@deanox.com>]

On 2002.05.22 19:15 Lou Katz wrote:

> Now, unlike e-mail spam, fax spam ties up the sender's resources
> for as long as it take to negotiate a fax session and send the turd,
> typically 1-2 minutes. What if my 'fax machine' turned out to be
> really really crappy - requesting resends every few scanlines?
> How long could I tie up a sender - minutes? hours? And maybe, just
> as the sender was finishing, I could issue a paper-jam or out-of-paper
> response?

Faxing doesn't work that way when dealing with scanlines, and although 
there are a few loops in the T.30 flowcharts which could be utilized in 
this fashion, most fax senders will not let that go on for long.  For 
example, most senders will disconnect after enough RTN (retransmit page) 
requests.

So the most you could do in this regard would be to force your system to 
negotiate at 2400 baud and send RTN to every PPM (post-page message).  
You'd use Class2DCCQueryCmd in Class 2 to do the former.  There is no 
configuration to do the latter, and in Class 1 there is neither.  
Although... you could probably alter ModemRecvFillOrder to force reception 
to actually be faulty, thus forcing RTN.
  If you're in the US there are laws designed to protect you from 
unsolicited faxes.

http://ftp.fcc.gov/Bureaus/Common_Carrier/Factsheets/unsolici.pdf

I've never persued any such legal action, but I suspect that if you were 
to implement CID or TSI screening or unsubscribe from their list somehow 
you'd save yourself a lot of trouble.

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@hylafax.org < /dev/null