QUOTE(stobal @ Feb 25 2006, 12:08 PM)
My mails are frequently blocked and hence my mailserver listed as spammer, only because I'm using languages with letters other than ASCII 128 (as I see as the reason).
X-VISP-Spam-Score: 4.7 (++++)
X-VISP-Spam-Report: This message has been scanned on "daiquiri.visp.de"
to identify if it is considered spam or not.
Contact the support hotline for details.
Content analysis details: (4.7 points, 5.0 required)
pts rule name description
---- ---------------------- --------------------------------------------------
3.4 SUBJ_ILLEGAL_CHARS Subject: has too many raw illegal characters
1.3 RCVD_IN_BL_SPAMCOP_NET RBL: Received via a relay in bl.spamcop.net
[Blocked - see <http://www.spamcop.net/bl.shtml?194.97.107.189>]
X-VISP-Spam-Max-Score: +++++
You've got it a little backwards....Your server has sent spam and been added to the BL because of it, hence your messages are being bounced back to you (or simply dropped, depending on the setup of the receiving system).
The foreign characters in the subject is one of the reasons that this system is using to decide what is spam. The owner of the receiving server can use whatever criteria they want for accepting email. By strict interpretation of the RFC's (
http://www.faqs.org/rfcs/rfc2822.html ), your special character is not allowed in the subject field.
2.2. Header Fields
Header fields are lines composed of a field name, followed by a colon
(":"), followed by a field body, and terminated by CRLF. A field
name MUST be composed of printable US-ASCII characters (i.e.,
characters that have values between 33 and 126, inclusive), except
colon. A field body may be composed of any US-ASCII characters,
except for CR and LF. However, a field body may contain CRLF when
used in header "folding" and "unfolding" as described in section
2.2.3. All field bodies MUST conform to the syntax described in
sections 3 and 4 of this standard.
And the subject is specifically defined as:
3.6.5. Informational fields
The informational fields are all optional. The "Keywords:" field
contains a comma-separated list of one or more words or
quoted-strings. The "Subject:" and "Comments:" fields are
unstructured fields as defined in section 2.2.1, and therefore may
contain text or folding white space.
2.2.1. Unstructured Header Field Bodies
Some field bodies in this standard are defined simply as
"unstructured" (which is specified below as any US-ASCII characters,
except for CR and LF) with no further restrictions. These are
referred to as unstructured field bodies. Semantically, unstructured
field bodies are simply to be treated as a single line of characters
with no further processing (except for header "folding" and
"unfolding" as described in section 2.2.3).
More directly to this message board, your server is also listed in spamcop's BL (as seen following the link provided):
Causes of listing
System has sent mail to SpamCop spam traps in the past week (spam traps are secret, no reports or evidence are provided by SpamCop)
SpamCop users have reported system as a source of spam less than 10 times in the past week
and:
Report History:
--------------------------------------------------------------------------------
Submitted: Thursday, February 23, 2006 7:14:26 AM -0500:
Spitteler[at]reptilienauge.de
1668753718 ( 194.97.107.189 ) To: spamcop[at]imaphost.com
1668753710 ( 194.97.107.189 ) To: tech-c[at]freenet-ag.de
--------------------------------------------------------------------------------
Submitted: Thursday, February 23, 2006 7:14:06 AM -0500:
Spitteler[at]reptilienauge.de
1668753480 ( 194.97.107.189 ) To: spamcop[at]imaphost.com
1668753473 ( 194.97.107.189 ) To: tech-c[at]freenet-ag.de
Your ISP needs to work a little harder to stop the spam coming from their servers and affecting your use of their service. Please complain to them.