From: Jack Twilley <jmt+usenet@nycap.rr.com>
Subject: Re: movemail problem
Date: Wed, 11 Nov 1998 16:44:03 GMT [thread overview]
Message-ID: <m37lx241td.fsf@dt01q0n13.nycap.rr.com> (raw)
In-Reply-To: <vxkogqe2nks.fsf@pocari-sweat.jprc.com>
>>>>> "Karl" == Karl Kleinpaste <karl@jprc.com> writes:
Karl> Offhand, it looks like you've got a movemail that was compiled
Karl> without POP support. But you'll do better to use edebug-defun
Karl> on nnmail-move-inbox and watch the exact movemail command line
Karl> that's being generated.
That's a great idea. Can you tell me how to do that? :-)
Jack.
.
next prev parent reply other threads:[~1998-11-11 16:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <m3btme42hk.fsf@dt01q0n13.nycap.rr.com>
1998-11-11 16:36 ` Karl Kleinpaste
1998-11-11 16:44 ` Jack Twilley [this message]
1998-11-11 16:57 ` Karl Kleinpaste
1998-11-11 16:32 Jack Twilley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m37lx241td.fsf@dt01q0n13.nycap.rr.com \
--to=jmt+usenet@nycap.rr.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).