67780 - XSENDER with POP3 is not really used

Status: VERIFIED DUPLICATE of bug 67779

(MailNews Core :: Networking: POP, defect)

Description

[Marian Eichholz]

Story: The POP3 protocol class requests an XSENDER and gets one by the server.

/1/ The server capabilities are initially hard wired to TRUE. This may be
offending for some systems that do not implement the unofficial XSENDER extension.

/2/ The nsPop3Protocol sets the MSG_FLAG_SENDER_AUTHED (0x200)
X-Mozilla-Status flag, but I found no location in the UI code, where this
flag is used.

/3/ There is an interface (m_nsIPop3Sink->SetSenderAuthedFlag()), but it is
called only once to *clear* the member flag, when the From-Header appears.

/4/ After all, the authenticated sender in the XSENDER reply is not used
(stored and retrieved) at all. It is stored into m_senderInfo but not passed
to the nsPop3Sink object.

After all, the concept of XSENDER seems to be somewhat useless at this
point.

Comment 1

[Marian Eichholz]

This dupe was caused by the form resend feature of Mozilla 0.7.
Please comment on the original report #67779.
Status changed to INVALID.
My apologies.



*** This bug has been marked as a duplicate of 67779 ***

Comment 2

[Fabian Guisset]

No prob.
VERIFIED duplicate.