Spam detection software, running on the system "mail.iptel.org", has
identified this incoming email as possible spam. The original message
has been attached to this so you can view it (if it isn't spam) or label
similar future email. If you have any questions, see
the administrator of that system for details.
Content preview: Hi. I have a question. I use x_lite do client,and ser
server do route. if user1 is 1001 and user2 is 1002, assumes i used 1001
to dial 999991002, I thinking in the ser.conf, first to remove the
prefix(99999),then route to 1002. if used asterisk the idea is ok but I
don't know ser whether to achieve? [...]
Content analysis details: (9.8 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
-0.0 SPF_HELO_PASS SPF: HELO matches SPF record
4.1 FROM_ILLEGAL_CHARS From: has too many raw illegal characters
-0.0 SPF_PASS SPF: sender matches SPF record
0.5 HTML_40_50 BODY: Message is 40% to 50% HTML
0.0 HTML_MESSAGE BODY: HTML included in message
0.0 BAYES_50 BODY: Bayesian spam probability is 40 to 60%
[score: 0.5035]
0.0 MIME_HTML_ONLY BODY: Message only has text/html MIME parts
0.2 DNS_FROM_RFC_ABUSE RBL: Envelope sender in
abuse.rfc-ignorant.org
2.2 RCVD_IN_WHOIS_INVALID RBL: CompleteWhois: sender on invalid IP block
[202.105.45.47 listed in
combined-HIB.dnsiplists.completewhois.com]
1.7 DNS_FROM_RFC_POST RBL: Envelope sender in
postmaster.rfc-ignorant.org
1.1 HTML_MIME_NO_HTML_TAG HTML-only message, but there is no HTML tag
The original message was not completely plain text, and may be unsafe to
open with some email clients; in particular, it may contain a virus,
or confirm that your address can receive spam. If you wish to view
it, it may be safer to save it to a file and open it with an editor.