At 11:23 AM -0400 7/6/01, Josh Hillman wrote:
> When issuing a
> ./configure --disable-status
> during installation of QPopper 4.0.3, the resulting binary is different from
> using a plain "./configure" however the X-UIDL header still shows up in
> messages that have been popped. It doesn't make any difference whether the
> mail client leaves the messages on the server or pulls them. Any message
> handled by QPopper have the X-UIDL header followed by "garbage" text
> (assuming the garbage part is normal).
> The "--disable-status" and X-UIDL info is referenced on page 41 and 58 of
> the Qpopper Administrator's Guide--Qpopper Version 4.0.
>
> We need to prevent that header from showing up in messages because
> Software.com's WebEdge 2.6.9a (webmail) has problems with messages that
> contain it. The webmail cannot delete those messages, nor can it correctly
> reply to those messages.
The no-status option (which can also be set at run-time) prevents
Qpopper from storing the header in the spool. Qpopper still
generates the information and includes it in the message sent to the
client because many clients depend on it. It seems pretty broken to
me for a client to behave poorly when seeing a header such as this,
instead of just ignoring it. What if someone happens to include such
a header in an email? Qpopper ignores it and uses it's own values,
but if the POP server didn't filter it out it would break your
webmail. That seems bad.
You can manually patch Qpopper to not send the header, but you are
probably better off getting the webmail software fixed to ignore the
header.
