forum.lissyara.su

Код: Выделить всё

This delivery report was generated by the program amavisd-new at host
primer.ru. Our internal reference code for your message is
89834-10/7AI2uE3h9FOw

INVALID HEADER: INVALID 8-BIT CHARACTERS IN HEADER SECTION

  Non-encoded 8-bit data (char D0 hex): Subject:
    \320\243\320\262\320\265\320\264\320\276\320\274\320\273\320\265[...]

Return-Path: <>
From: 
Message-ID: <>
Subject: ???^2?????????????????? ?? ???\200??????????????
  (?????????\200?°????????) - [no subject]

WHAT IS AN INVALID CHARACTER IN A MAIL HEADER SECTION?

  The RFC 2822 standard specifies rules for forming internet messages.
  It does not allow the use of characters with codes above 127 to be
  used directly (non-encoded) in a mail header section.

  If such characters (e.g. with diacritics) from ISO Latin or other
  alphabets need to be included in a header section, these characters
  need to be properly encoded according to RFC 2047. Such encoding is
  often done transparently by mail reader (MUA), but if automatic
  encoding is not available (e.g. by some older MUA) it is a user's
  responsibility to avoid using such characters in a header section,
  or to encode them manually. Typically the offending header fields
  in this category are 'Subject', 'Organization', and comment fields
  in e-mail addresses of 'From', 'To' or 'Cc' header fields.

  Sometimes such invalid header fields are inserted automatically
  by some MUA, MTA, content checker, or other mail handling service.
  If this is the case, that service needs to be fixed or properly
  configured. Typically the offending header fields in this category
  are 'Date', 'Received', 'X-Mailer', 'X-Priority', 'X-Scanned', etc.

  If you don't know how to fix or avoid the problem, please report it
  to _your_ postmaster or system manager.