![]() |
SPAM: -------------------- Start SpamAssassin results ---------------------- SPAM: This mail is probably spam. The original message has been altered SPAM: so you can recognise or block similar unwanted mail in future. SPAM: See http://spamassassin.org/tag/ for more details. SPAM: SPAM: Content analysis details: (5.1 hits, 5 required) SPAM: MSGID_CHARS_SPAM (2.1 points) Message-Id has characters indicating spam SPAM: MSGID_CHARS_WEIRD (0.1 points) Message-Id has characters often found in spam SPAM: DOUBLE_CAPSWORD (1.1 points) BODY: A word in all caps repeated on the line SPAM: UPPERCASE_25_50 (1.9 points) BODY: message body is 25-50% uppercase SPAM: NO_MX_FOR_FROM (1.8 points) No MX records for the From: domain SPAM: RCVD_IN_OSIRUSOFT_COM (2.0 points) RBL: Received via a relay in relays.osirusoft.com SPAM: [RBL check: found 22.28.253.212.relays.osirusoft.com., type: 127.0.0.3] SPAM: AWL (-3.9 points) AWL: Auto-whitelist adjustment SPAM: SPAM: -------------------- End of SpamAssassin results --------------------- SPAM: -------------------- Start SpamAssassin results ---------------------- SPAM: This mail is probably spam. The original message has been altered SPAM: so you can recognise or block similar unwanted mail in future. SPAM: See http://spamassassin.org/tag/ for more details. SPAM: SPAM: Content analysis details: (5 hits, 5 required) SPAM: MSGID_CHARS_SPAM (2.1 points) Message-Id has characters indicating spam SPAM: MSGID_CHARS_WEIRD (0.1 points) Message-Id has characters often found in spam SPAM: DOUBLE_CAPSWORD (1.1 points) BODY: A word in all caps repeated on the line SPAM: UPPERCASE_25_50 (1.9 points) BODY: message body is 25-50% uppercase SPAM: NO_MX_FOR_FROM (1.8 points) No MX records for the From: domain SPAM: RCVD_IN_OSIRUSOFT_COM (2.0 points) RBL: Received via a relay in relays.osirusoft.com SPAM: [RBL check: found 22.28.253.212.relays.osirusoft.com., type: 127.0.0.3] SPAM: AWL (-4.0 points) AWL: Auto-whitelist adjustment SPAM: SPAM: -------------------- End of SpamAssassin results --------------------- Hi I have a faxserver with Eicon DivaServer PRI. I am trying to catch the calling and the CALLED number. After setting the ModemRestCmds to "AT#CID=7" I got the numbers but some how hylafax does not recognize them ( actually I must say LUCKLY it does not recognize them so instead of just the CID I have also the DAD ( called number) ..) I got the following faxrcvd activation line which combines the calling and the called number in 5th and 6th parameters. Is this designed so and can I relay on this? ---- from fax receive log file. RECV FAX: bin/faxrcvd "recvq/fax00008.tif" "ttyds02" "00000014" "" "RING CID: 02122920744 DAD: 3348600" "RING CID: 02122920744 DAD: 3348600" ---- From the system log ( I have session and server tracing set to 0xFFF Aug 12 12:04:17 localhost FaxGetty[1525]: STATE CHANGE: RUNNING -> LISTENING Aug 12 12:04:17 localhost FaxGetty[1525]: MODEM input buffering enabled Aug 12 12:04:17 localhost FaxGetty[1525]: --> [33:RING CID: 2122920744 DAD: 3348600] Aug 12 12:04:17 localhost FaxGetty[1525]: ANSWER: CID NUMBER "RING CID: 2122920744 DAD: 3348600" NAME "RING CID: 2122920744 DAD: 3348600" Aug 12 12:04:23 localhost FaxGetty[1525]: --> [33:RING CID: 2122920744 DAD: 3348600] Aug 12 12:04:23 localhost FaxGetty[1525]: ANSWER: CID NUMBER "RING CID: 2122920744 DAD: 3348600" NAME "RING CID: 2122920744 DAD: 3348600" Aug 12 12:04:29 localhost FaxGetty[1525]: --> [33:RING CID: 2122920744 DAD: 3348600] Aug 12 12:04:29 localhost FaxGetty[1525]: ANSWER: CID NUMBER "RING CID: 2122920744 DAD: 3348600" NAME "RING CID: 2122920744 DAD: 3348600" Aug 12 12:04:29 localhost FaxGetty[1525]: STATE CHANGE: LISTENING -> ANSWERING ____________________ 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 *To learn about commercial HylaFAX(tm) support, mail sales@hylafax.org.*