natashak
06-28-06, 10:47 PM
We purchased the Subscribe2 Pro product for email blasts to our clients and interested parties, but one of these emails sent us an "undeliverable mail" error back. We've been using this program since last year and haven't needed support until now, when Miva no longer offer it for this product in particular. None of us quite understand what it relates to, but what we really need to know is if anyone knows if it's possible to manually edit the header info within the program itself? Or what might trigger the error otherwise?
If it helps, the error we received is listed below. Any help would be greatly appreciated!
INVALID HEADER (INVALID CHARACTERS OR SPACE GAP)
MIME error: error: part did not end with expected boundary
This nondelivery report was generated by the amavisd-new program
at host indyvss2. Our internal reference code for your message
is 24076-01-90.
WHAT IS AN INVALID CHARACTER IN MAIL HEADER?
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 mail header (it also prohibits NUL and bare CR).
If characters (e.g. with diacritics) from ISO Latin or other alphabets
need to be included in the header, these characters need to be properly
encoded according to RFC 2047. This encoding is often done transparently
by mail reader (MUA), but if automatic encoding is not available (e.g.
by some older MUA) it is the user's responsibility to avoid the use
of such characters in mail header, or to encode them manually. Typically
the offending header fields in this category are 'Subject',
'Organization',
and comment fields in e-mail addresses of the 'From', 'To' and 'Cc'.
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.
If it helps, the error we received is listed below. Any help would be greatly appreciated!
INVALID HEADER (INVALID CHARACTERS OR SPACE GAP)
MIME error: error: part did not end with expected boundary
This nondelivery report was generated by the amavisd-new program
at host indyvss2. Our internal reference code for your message
is 24076-01-90.
WHAT IS AN INVALID CHARACTER IN MAIL HEADER?
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 mail header (it also prohibits NUL and bare CR).
If characters (e.g. with diacritics) from ISO Latin or other alphabets
need to be included in the header, these characters need to be properly
encoded according to RFC 2047. This encoding is often done transparently
by mail reader (MUA), but if automatic encoding is not available (e.g.
by some older MUA) it is the user's responsibility to avoid the use
of such characters in mail header, or to encode them manually. Typically
the offending header fields in this category are 'Subject',
'Organization',
and comment fields in e-mail addresses of the 'From', 'To' and 'Cc'.
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.