Subject: Pine 4.44 and Domino 5.0.11

From: David Bradford <[email-masked]>
Date: Thu, 22 Aug 2002 16:43:46 -0700 (Pacific Daylight Time)

My users are having lots of problems using Pine 4.44 to access our
Notes/Domino mail server via IMAP. Domino server is 5.0.11 on Linux
2.4.18-3. Before reaching the Notes server, the mail is delivered to an
account on an ISP. I am transferring the mail from the remote ISP (POP3,
my only protocol option) to the local Domino SMTP listener using fetchmail
5.9.

It seems if messages have no attachments, the messages are viewable
without problems in Pine. If messages are multipart or contain
attachments, we get the error "Message size does not match expected size,
continuing..." in Pine. Some messages trigger a series of errors including
"Junk at end of message", "missing multipart subtype", etc. and some
messages crash Pine altogether. This happens in both UNIX Pine and
PC-Pine 4.44.

Can anyone shed some light on what I can do to resolve these problems?

-- 
David Bradford
Information Services Director, LPA, Inc.
Home: (503) 203-1043
Cell: (503) 341-9519

-- 
-----------------------------------------------------------------
 For information about this mailing list, and its archives, see: 
 http://www.washington.edu/pine/pine-info/
-----------------------------------------------------------------

---

From: daniel lance herrick <[email-masked]>
Date: Fri, 23 Aug 2002 10:25:54 -0400 (EDT)

fetchmail has two protocol options that talk to
the sendmail on the server and, so, get the
envelope data as well as the message itself with
its headers.

To serve "my users" you really want the envelope
information. (What happens when one mail message
is addressed to two of your users? What happens
when one of your users subscribes to an e-mail
list that does not put his address in the
headers? What happens when you get things set up
so such an e-mail list is properly delivered to
the subscriber and then another of your users
decides to subscribe to the same e-mail list
without telling you?) POP3 is designed to serve
only one user per account and it loses the
envelope information before you see it.

Your life will become much easier when you give up
and switch to an ISP who is running a unix variant
and knows how the mail works. (When the second is
true, the first will be true, and POP3 will not be
"my only protocol option".) However, the troubles
you are complaining of do not have to happen when
the protocol is POP3.

(I really suspect that if you work as hard as you
can on solving the problems you complain about
below, and also, casually, start shopping for an
ISP, you will end up switched to a new ISP before
you succeed in solving the difficulties at the old
ISP.)

That out of the way, which component is acting up?

Reconfigure fetchmail for an hour or two to not
delete the e-mail it fetches. Then use pine to
pick up that mail directly from the POP
server (after fetchmail has already fetched
it into your system). Does pine pick it up
cleanly? Or is it mangled with only the POP3
server and pine involved? (point the finger at the
isp)

Can you find a way to route some test e-mail from
the POP3 server through fetchmail to procmail for
local delivery? Is that mail mangled when you look
at it with pine?

How does the e-mail get from fetchmail to the
Notes/Domino server? Is Domino listening on port
25 on the local machine and fetchmail just drops
it there? If so, it is almost impossible to have
fetchmail misconfigured. Do you have fetchmail
running Domino to feed it the messages? Is there
something strange about the switches you need to
have on the Domino command line to get the mail
into it cleanly?

dan