In <[log in to unmask]> [log in to unmask] writes:
> Martin's message was sent in MIME format and contained a strange
> MIME boundary:
> boundary="----
> =_0_MIME_Boundary_21967.328ca51c.imtvhj30.dcuh029.dcu.ps.net"
>
> In case your mailer didn't show that, that is four dashes, space,
> "=_0_(etc)". An embedded space, in other words. The mailer was
> identfied in the headers as:
>
> X-Mailer: Worldtalk (4.0.2-p6)/MIME
>
> Listserv "folded" this line at the embedded space, yielding the full
> MIME header line of:
>
> Content-Type: multipart/mixed; boundary="----
>
> =_0_MIME_Boundary_21967.328ca51c.imtvhj30.dcuh029.dcu.ps.net"
>
> I read the message with Netscape 3.0 Gold, and I got a blank message
> body (headers, no text) but using View...Source I could see the text.
> Some of you may have seen the same thing. Some of you, however, never
> got the message in the first place, as I received over a dozen bounces
> from various places indicating a fatal SMTP error code 553:
>
> 553 header syntax error, line "
> =_0_MIME_Boundary_21967.328ca51c.imtvhj30.dcuh029.dcu.ps.net"": No such
> file or directory
>
> I checked each and every one of the bounced sites and found that
> all of them were running HP sendmail of various versions, some of
> which were:
>
> (1.39.109.11/15.6)
> (1.39.111.2/16.2)
> (1.40.112.8/16.2.3)
> I don't know if Listserv, Worldtalk, Netscape, or HP Sendmail is
> broken/non-conforming/whatever, but I thought those of you affected
> might want to be aware of the problem. And I have no idea how many
> other mailers/mail readers may have been affected.
>
> Jeff Kell <[log in to unmask]>
I have to admit this one caught us as well. When viewed with the latest
version of NetMail, I too saw an empty message. It didn't bounce the message
at least :-). NetMail also gives you an "out"- turn MIME off in the user
interface, then the message displays.
The line-break in the middle of a MIME boundary *is* legal as it turns
out; when I initially saw it I thought the listserv had 'broken' the message,
but the folks at Lsoft were right, and we, Netscape, and Sendmail are
wrong (though bouncing the message is a rather nasty thing to do).
(Since listserv apparently broke up the boundary, Worldtalk didn't have
anything to do with it - their initial boundary was fine.)
There was alot of confusion about this in the earlier MIME RFCs, though as
I perused the latest rev, they included a specific example of breaking
MIME boundaries and that apparently the whitespace/crlf are to be treated
as a single space.
[needless to say, we'll fix NetMail to accomodate this as well]
Chris "it's a bug, not a feature! (tm)" Bartram
______________________/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_
Chris Bartram Sales (US): 800 Net-Mail Fax:+1 703 451-3720
______ +1 703 569-9189 mailto:[log in to unmask]
/__ | \__________ Sales (Europe):+44(1480)414131 Fax:+44(1480)414134
/ / | / ________ Sales (Pacific Rim):+61 3 489 8216 (same for fax)
| /_ |< ______ Tech Support:+1 703 569-9189 Fax:+1 703 451-3720
\ __)| \ ___ mailto:[log in to unmask] Me: mailto:[log in to unmask]
\______/Associates, 6901 Old Keene Mill Rd Suite 500 Springfield VA 22150
_________________Inc._/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_/\_
Gopher: gopher.3k.com Anon-FTP: ftp.3k.com WWW: http://www.3k.com/
|
