Closed Bug 69510 Opened 24 years ago Closed 24 years ago

mail is sent with bad X-UIDL field

Categories

(MailNews Core :: Networking: SMTP, defect)

DEC
OpenVMS
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: colin, Assigned: mscott)

Details

Using M0.8 on OpenVMS. I send mail with an attachment from Mozilla to a different user. That other user, when they try to download all of the message using Navigator 4.7 (they need to click on "download rest of message" because its above their normal size limit as set in their Nav prefs) they receive the following message: unable to connect to server and in the status bar they can see: Connect: Contacting host: ~4*#!@jW"!-@Z"!mE8!! Here's the headers from the message: Message-ID: <3A929712.6050205@theblakes.com> Date: Tue, 20 Feb 2001 11:10:58 -0500 From: "Colin's Alpha" <test@theblakes.com> User-Agent: Mozilla/5.0 (X11; U; OpenVMS 0 COMPAQ_AlphaStation_DS20E_666_M; en-U S; 0.8) Gecko/20010214 X-Accept-Language: en MIME-Version: 1.0 To: colin@theblakes.com Subject: Force stack size to min 128K Content-Type: multipart/mixed; boundary="------------010405000900050201080704" X-UIDL: ~4*#!@jW"!-@Z"!mE8!! Status: U Notice that the X-UIDL string matches the funky server name that Nav 4.7 was trying to connect to. This only happens if I'm SENDING a message with an attachment. If I instead REPLY with the attachment, all is well (I presume because the X-UIDL field gets something sensible written into it).
I've been doing some more playing around. I don't think this is anything to do with OpenVMS or Mozilla. Many different mail clients send a "jibberish" X-UIDL header. When seems to upset Navigator 4.7 is when (a) the message larger than the user's configured "don't automatically download messages larger than this" size, AND, (b) the X-UIDL string contains an ampersand ("@") character. I'm off to search the Navigator knowledge base if I can find it....
I just read RFC1725. The UIDL field is part of the POP3 protocol and is defined by the POP3 server. Therefore this is absolutely and positively nothing to do with Mozilla. It must be a Navigator 4.7 bug. Closing. Sorry for the noise.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
verified, but this bug really should have been closed with the "invalid" selection.
Status: RESOLVED → VERIFIED
Product: MailNews → Core
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.