From: Simon Josefsson <jas@extundo.com>
Cc: ding@gnus.org
Subject: Re: IMAP error when posting
Date: Wed, 02 Oct 2002 00:57:04 +0200 [thread overview]
Message-ID: <iluptutvkcf.fsf@latte.josefsson.org> (raw)
In-Reply-To: <87ptuujbua.fsf@crybaby.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 01 Oct 2002 19:41:33 +0200")
Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>
>> Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:
>>
>>> (setq imap-shell-program
>>> '("ssh -e none grossjoh@austin.cs.uni-dortmund.de netcat %s 143"))
>>>
>>> Maybe it is better to use port forwarding. Hm. Can I tell Gnus to
>>> execute a shell script for the connection, prior to actually
>>> connecting? The shell script could set up the port forwarding.
>>
>> I've now tried port forwarding, but it is "administratively
>> prohibited" :-(
>>
>> But the above command works in principle.
>
> Only in principle, though: copying into groups with Gcc or Newsgroups
> or B c fails, probably an eol issue.
imap.el evaluates (setq imap-client-eol "\n") inside imap-shell-open,
so you must set it back to \r\n if you need that.
> I now changed the configuration of sshd to allow port forwarding, and
> now I'm a happy camper.
Yes, port forwarding is much more reliable.
next prev parent reply other threads:[~2002-10-01 22:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-01 8:12 Kai Großjohann
2002-10-01 12:42 ` Simon Josefsson
2002-10-01 14:07 ` Kai Großjohann
2002-10-01 14:28 ` Kai Großjohann
2002-10-01 15:10 ` Simon Josefsson
2002-10-01 14:57 ` Simon Josefsson
2002-10-01 15:02 ` Kai Großjohann
2002-10-01 15:07 ` Kai Großjohann
2002-10-01 15:37 ` Kai Großjohann
2002-10-01 17:41 ` Kai Großjohann
2002-10-01 22:57 ` Simon Josefsson [this message]
2002-10-02 20:17 ` Kai Großjohann
2002-10-02 21:47 ` Simon Josefsson
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=iluptutvkcf.fsf@latte.josefsson.org \
--to=jas@extundo.com \
--cc=ding@gnus.org \
/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).