From: Jens.Schmidt27@epost.de (Jens Schmidt)
Subject: Re: Can Gnus handle multiple ISPs?
Date: 27 May 2002 01:09:19 -0700 [thread overview]
Message-ID: <958686cf.0205270009.2406784d@posting.google.com> (raw)
In-Reply-To: <958686cf.0205250726.5867ff99@posting.google.com>
Thanks to all posters for their advice.
I should have added that the information I get from ISP A and ISP
B is disjoint: I get my office mail via IMAP from ISP A, my
private mail via POP from ISP B (and probably in future my news
from ISP C because the news server at our office sucks and I do not
want use Google when there is Gnus).
Is that scenario so unusual that nobody stumbled across it in the
past?
Jens
prev parent reply other threads:[~2002-05-27 8:09 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <958686cf.0205250726.5867ff99@posting.google.com>
2002-05-26 0:21 ` Reiner Steib
2002-05-26 19:32 ` Simon Josefsson
[not found] ` <958686cf.0205270006.a6bfc28@posting.google.com>
2002-05-27 15:07 ` Simon Josefsson
2002-05-28 8:09 ` Jens Schmidt
2002-05-28 15:28 ` Kai Großjohann
[not found] ` <bobu1ovsv2y.fsf@gis.net>
[not found] ` <m3g00fem8q.fsf@multivac.cwru.edu>
[not found] ` <bobn0unsgr1.fsf@gis.net>
2002-05-27 4:20 ` Paul Jarc
2002-05-27 5:21 ` Bob Babcock
2002-05-27 8:09 ` Jens Schmidt [this message]
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=958686cf.0205270009.2406784d@posting.google.com \
--to=jens.schmidt27@epost.de \
/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).