![]() |
> The job(user) can specify a maxdials/maxtries, but they are "capped" by > the settings of faxq. If you really don't want faxq to cap settings, > set them to -1 in the faxq config. Then clients can set them to > whatever they want, and they don't get capped by faxq (well, capped by > the size of an u_int on whatever platform you're on). > > See faxd/faxQueueApp.c++:2391
I've looked into FaxSend.c++:462 (in Hylafax+ v. 4.3.0.3) and noticed the following: -snip- if (fax.ntries > 2) { if (fax.notice != "") fax.notice.append("; "); fax.notice.append( "Giving up after 3 attempts to send same page"); traceServer("SEND: %s \"%s\", dirnum %d", (const char*) fax.notice, (const char*) freq.item, freq.dirnum); fax.status = send_failed; } -snip-
Shouldn't the the check be (fax.ntries >= fax.maxtries) or something else taken from the config file?
____________________ 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*