Can you merge Pines?
Beartooth
I run two machines, mostly, with one of them serving mainly to back up the
other; and two more mainly just for looking at weather reports, and
anything else that need not interact with the apps I use constantly -- but
even those two of course do have pine on them; all of them, and also the
pine account on my wife's machine, which she doesn't use (She runs pine
on a remote ISP.), are configured to access the same ISP. (All five are
behind the same router. And I can ssh between them, if I want to bad
enough, by moving to the target and commanding for the nonce "service
iptables stop" ; I don't have a really proper LAN.)
So it happens at times, when I'm busy working on something on a machine
other than my usual one, that I jump into its pine account for some reason
-- often, in fact, to pass some little thing back and forth that I don't
want to do with scp. So I often also save a newly arrived message on
whatever machine it's on; I've made sure that pine doesn't delete from
server, and I don't drop a message out of my inbox till I'm sure I'm
through with it.
But that means that, for instance, no two of the GPS folders on five
different machines are related simply as set and proper subset. So I can't
simply scp all of my pine folders -- or even any one -- from one to
another without losing things.
I would like to clean up every few months, if there's a reasonably easy
way to do it, and reach stages where all my pine folders (not the same
list on each machine, but around a hundred folders) are the same.
Is there a way??
--
Beartooth Staffwright, Hunter by Birth,
Not Quite Clueless Fedora Power User
by God's Grace, Linux's and the Net's
Stephen Chadfield
[snip]
> I would like to clean up every few months, if there's a reasonably easy
> way to do it, and reach stages where all my pine folders (not the same
> list on each machine, but around a hundred folders) are the same.
>
> Is there a way??
Use IMAP. Pine is an IMAP client, you know.
--
Stephen Chadfield
http://www.chadfield.com/
Beartooth
> Beartooth <bear...@adelphia.net> wrote:
>
> [snip]
>
>> I would like to clean up every few months, if there's a reasonably easy
>> way to do it, and reach stages where all my pine folders (not the same
>> list on each machine, but around a hundred folders) are the same.
>>
>> Is there a way??
>
> Use IMAP. Pine is an IMAP client, you know.
Would someone please explain that in English, or refer me to a site with a
recipe? I *use* IMAP for preference -- very strong preference (though I
also run it against an ISP which is benighted enough to offer only pop3);
I don't *run* it (unless FC4 does without telling me), and have never
gotten around to learning anything more about it -- and more that I have
to learning vi or emacs, since I have pico.
NM Public
> On Tue, 14 Mar 2006 01:14:13 +0000, Stephen Chadfield wrote:
>> Beartooth <bear...@adelphia.net> wrote:
>>
>>> I would like to clean up every few months, if there's a
>>> reasonably easy way to do it, and reach stages where all my
>>> pine folders (not the same list on each machine, but around a
>>> hundred folders) are the same.
>>>
>>> Is there a way??
>>
>> Use IMAP. Pine is an IMAP client, you know.
>
> Would someone please explain that in English, or refer me to a
> site with a recipe? I *use* IMAP for preference -- very strong
> preference (though I also run it against an ISP which is
> benighted enough to offer only pop3); I don't *run* it (unless
> FC4 does without telling me), and have never gotten around to
> learning anything more about it -- and more that I have to
> learning vi or emacs, since I have pico.
Here's what I recommend (and do myself).
1. Get an IMAP service provider that offers at least 1 gig of
IMAP-accessible space, server-side filtering, backups &
restores, and a webmail that can do global searching of your
IMAP space.
2. Keep all your email on your IMAP service provider's system.
3. Set up Pine on all your systems, both your local desktop
systems and your remote systems, so that it accesses and manages
your mail on your IMAP service provider's system.
4. Set up your pinerc(s) and address book(s) so they reside on
your IMAP service provider's system.
5. Set up an alias or shortcut on every system where you run Pine
that looks something like this:
pine -p {your.imap.provider}remote-pinerc
Once you've done all this, you will be able to access and manage
all your mail from all your systems without needing to worry
about your mailboxes getting out of sync or spread around on
different machines. THIS is what IMAP is all about.
If you need more than a gig to store your mail, shop around. Disk
space is essentially free and infinite now. For example, my Verio
Signature account now includes 10 gigabytes (i.e., 10240000
bytes). If Verio is offering this, that means everyone will be
soon.
I hope this makes sense and I hope you can join the wonderful
world of IMAP!
Nancy
--
Nancy McGough ~ <http://www.ii.com> ~ <http://deflexion.com>
Beartooth
> On 2006-03-15, I Beartooth [bear...@adelphia.net] wrote inter alia :
>> Would someone please explain that in English, or refer me to a site
>> with a recipe? I *use* IMAP for preference [...]
>
> Here's what I recommend (and do myself).
[Aside: I'm honored to see Nancy her own self on this thread, and I hope
the following is not clear off topic; there may be several of us in the
same boat. And she will know if anybody does. -- btth]
> 1. Get an IMAP service provider that offers at least 1 gig of
> IMAP-accessible space, server-side filtering, backups & restores, and a
> webmail that can do global searching of your IMAP space.
OK, I have most of that, and can probably have the rest if I ask; I may
have it now and not know it. I know that Ddave (who owns the IMAP machine)
runs squirrelmail on his web interface; I use that at times against the
account there. I've asked him about server-side filtering and backups &
restores.
> 2. Keep all your email on your IMAP service provider's system.
I'd love to! I keep most of it there now. (Details below.)
> 3. Set up Pine on all your systems, both your local desktop systems and
> your remote systems, so that it accesses and manages your mail on your
> IMAP service provider's system.
Question: in what sense accesses and manages? I have two email accounts,
both of which I access from five machines. My good ISP, from whom I do get
IMAP and on whose linux machine I run Pine and do most of my email, is
remote -- three thousand-odd miles.
(Lest I cause confusion: heretically enough, I don't use Pine to read
comp.mail.pine -- or any other newsfeed. Despite my attachment to Pine for
email, I prefer to run Pan as my newsreader.)
The only broadband connection available where I live (and the account I
get my newsfeeds from, and thus use for c.m.p) is the POP3 one on cable --
which is also my only access to usenet, the Web, downloads, etc.
I can't get rid of that; if I did, I'd have no broadband at all. I doubt
that I can configure it in any significant way, either -- or anything else
on any machine at Adelphia. (More below.)
> 4. Set up your pinerc(s) and address book(s) so they reside on your IMAP
> service provider's system.
The ones for the IMAP account are there now; the ones for the local
account were originally cloned from them. (They may have diverged a
little.)
> 5. Set up an alias or shortcut on every system where you run Pine that
> looks something like this:
>
> pine -p {your.imap.provider}remote-pinerc
>
>
> Once you've done all this, you will be able to access and manage all
> your mail from all your systems without needing to worry about your
> mailboxes getting out of sync or spread around on different machines.
> THIS is what IMAP is all about.
Here's where I get confused. As things are now, each of the machines in
this house accesses the one same POP3 account directly -- using Pine in a
Gnome terminal -- and also accesses the one same IMAP account directly,
over a remote (ssh) connection. (One machine here does both about 99% of
the time, and the others do only occasionally -- mostly when I'm forced to
reboot the main machine to XP for something I can't yet run under linux.)
The trouble of course is with the POP3 account. Accessing the same
instance of Pine from several locations is indeed a great blessing.
Believe me, I do understand that part, and delight in it.
I *think* you're saying that I should arrange for the remote IMAP machine,
rather than any of my own machines directly, to access my POP3 account,
and then I would access it through the remote connection, instead of
directly, as I do now.
Is that right??
I would get my adelphia mail *through* the remote IMAP, and leave the
extant IMAP alone except for telling it about the additional mailserver.
Right??
And I would still keep both addresses, and know when I was working
in which?? (That detail is important, unfortunately.)
> If you need more than a gig to store your mail, shop around. Disk space
> is essentially free and infinite now. For example, my Verio Signature
> account now includes 10 gigabytes (i.e., 10240000 bytes). If Verio is
> offering this, that means everyone will be soon.
>
> I hope this makes sense and I hope you can join the wonderful world of
> IMAP!
>
> Nancy
Item 5 is the one I mainly want to follow up with questions :
> 5. Set up an alias or shortcut on every system where you run Pine that
> looks something like this:
>
> pine -p {your.imap.provider}remote-pinerc
>
[...]
Let me see if I have this straight. Is that a bash alias? I know where I
can get advice on those if I need it. Or is it some kind of alias inside
something else? And is it on each of my own machines? Or do I have to get
Adelphia The Eternally Accursed (which probably doesn't own a linux drive)
to put an alias on its machine somehow?
I think you're going to tell me I don't have to configure a thing at
Adelphia, or even tell them about it -- they wouldn't want to be bothered,
because it would make literally *no* difference to them? It sounds almost
too good to be true.
I hope this post isn't too mixed up; I really am finding yours, Nancy, a
such a revelation that I can hardly get my head around it, if it does mean
what I take it to. But I'm not at all surprised at the source.
NM Public
post your pinerc file(s), either here or on the Net somewhere
(and then post the URL here). I will use the information in it to
make a suggestion for how you can become an all IMAP all the time
person. This will probably involve using:
* a Pine maildrop folder to periodically automatically move your
POP3 mail to your IMAP server
* making sure that your IMAP server is your Pine "primary folder
collection"
* describe how to move your pinerc and address book to your IMAP
server
* give you a pine alias that you should put on all your machines
(local and remote) to launch pine
I use dial-up access too and it is not a problem. Pine is
excellent at dealing with IMAP over a slow connection.
Be aware that you will no longer have access to your mail when
you are disconnected. If this will not work for you, then let me
know now.
Thank you,
Beartooth
> Before I try to answer your questions Beartooth, could you please post
> your pinerc file(s), either here or on the Net somewhere (and then post
> the URL here). I will use the information in it to make a suggestion for
> how you can become an all IMAP all the time person.
I don't have a web site, and that seems a mighty long file; do you really
want the whole thing, or are there sizeable parts of it that I can excise?
> This will probably involve using:
>
> * a Pine maildrop folder to periodically automatically move your
> POP3 mail to your IMAP server
> * making sure that your IMAP server is your Pine "primary folder
> collection"
> * describe how to move your pinerc and address book to your IMAP
> server
> * give you a pine alias that you should put on all your machines
> (local and remote) to launch pine
I'm sure all the jargon is in your excellent FAQ; I'll start looking it
up.
> I use dial-up access too and it is not a problem. Pine is excellent at
> dealing with IMAP over a slow connection.
Pine is, yes, but I'm not.
It was probably a mistaken oversimplification on my part to describe
Ddave's machines at Lserv as my ISP; he runs a business, but not an ISP
business.
He lets me have an account there, behind his spam filters, out of the
goodness of his heart, because we first met on the old spam-L, 99% of
whose traffic was and remains beyond me, at a time when I had vast
bandwith. I could often forward spams to the list so fast that the far
more knowledgeable subscribers could alert the spammers' ISPs, and get
them shut down, while they were still spamming. We all took considerable
glee in that.
When I first retired, and discovered how inferior anything you could run
on Windows was (even PC-Pine imnsho), I soon found a second ISP,
radix.net, that ran linux; so I could telnet into it and run pine there.
(I'm the guy who took up linux, going on ten years ago, primarily to run
pine.) Then when my wife also retired and we moved, I found no such ISP
where we live now.
Meanwhile, telnet had become unsafe. So my only access to my real email is
over ssh: I couldn't use a phone modem even if I were willing (and I'm
not; even Adelphia is better than dialup, and I use the difference heavily).
> Be aware that you will no longer have access to your mail when you are
> disconnected. If this will not work for you, then let me know now.
<sigh> That sounds like a point that struck me in the night. There are
times when I get cut off from Lserv altogether, usually by some fault of
adelphia's, but sometimes by a problem on the other end. When that
happens, my recourse is to email Ddave from my adelphia account; so I need
to be able to keep my access to it, even if I seldom use it.
I bet that puts the kibosh on the whole thing, doesn't it?
--
Beartooth Staffwright, Hunter by Birth,
Not Quite Clueless Fedora Power User
by God's Grace, Linux's, and the Net's
NM Public
>
>> Be aware that you will no longer have access to your mail when
>> you are disconnected. If this will not work for you, then let
>> me know now.
>
> <sigh> That sounds like a point that struck me in the night.
> There are times when I get cut off from Lserv altogether,
> usually by some fault of adelphia's, but sometimes by a problem
> on the other end. When that happens, my recourse is to email
> Ddave from my adelphia account; so I need to be able to keep my
> access to it, even if I seldom use it.
>
> I bet that puts the kibosh on the whole thing, doesn't it?
Not necessarily. Which of the following are true:
1. [ ] Beartooth runs pine on his local computer.
2. [ ] Beartooth uses ssh to run pine on Dave's remote computer.
3. [ ] Beartooth uses ssh to run pine on X's remote computer.
From what you've written, I'm pretty sure that #2 is the case,
but what about #1 and #3 (where X is some other (non-Dave) remote
computer)? Please check all of the above that are true (e.g., for
me I would check all 3 of these (*)).
I'm trying to understand how you use Pine right now. This will
help me to understand if it makes sense for you to do what I was
thinking would be useful for you.
Also, can you ask Dave these 2 questions:
* What IMAP server is he running (e.g. Courier, Cyrus, Dovecot,
or UW)?
* What is the IMAP hierarchy separator (usually either '.', '/',
or '\')?
This will help me to help you set up the IMAP-accessible
configuration files.
Bye for now,
Nancy
(*) where 'Dave' is replaced by my friend 'John'!
NM Public
>
> Also, can you ask Dave these 2 questions:
>
> * What IMAP server is he running (e.g. Courier, Cyrus, Dovecot, or UW)?
>
> * What is the IMAP hierarchy separator (usually either '.', '/', or '\')?
Beartooth - In addition to the above 2 questions, can you also
ask Ddave this:
* How much hard disk space can you, Beartooth, use on Ddave's
system to store IMAP mailboxes?
Thanks,
Nancy
Beartooth
> Sur 2006-03-16, Beartooth skribis:
>> I bet that puts the kibosh on the whole thing, doesn't it?
>
>
> Not necessarily. Which of the following are true:
>
> 1. [ ] Beartooth runs pine on his local computer. 2. [ ] Beartooth uses
> ssh to run pine on Dave's remote computer. 3. [ ] Beartooth uses ssh to
> run pine on X's remote computer.
>
> From what you've written, I'm pretty sure that #2 is the case, but what
> about #1 and #3 (where X is some other (non-Dave) remote computer)? Please
> check all of the above that are true (e.g., for me I would check all 3 of
> these (*)).
> (*) where 'Dave' is replaced by my friend 'John'!
#1 and #2, but not #3 -- and fwiw, #2 is also true of my wife. On rare
occasions, I call up my remote on a browser; I know that Ddave uses
squirrelmail, but not whether it runs on the same machine as my pine
account, or just connects to that.
> I'm trying to understand how you use Pine right now. This will help me to
> understand if it makes sense for you to do what I was thinking would be
> useful for you.
>
> Also, can you ask Dave these 2 questions:
>
> * What IMAP server is he running (e.g. Courier, Cyrus, Dovecot,
> or UW)?
>
> * What is the IMAP hierarchy separator (usually either '.', '/',
> or '\')?
>
> This will help me to help you set up the IMAP-accessible configuration
> files.
I'll forward your next, with the third added, to him. Thanks!
Beartooth Stafwright
> Sur 2006-03-20, NM Public skribis:
>>
>> Also, can you ask Dave these 2 questions:
[snip]
Dovecot is the IMAP server and my disk space is unlimited. Dave also
says, "Sounds like you are looking at using pine on titan as your master.
If you have trouble, have her send me the config and I'll set it up for
you." (I seem to've forgotten to ask about the separator.)
--
Beartooth Staffwright, Wordcrafty Squirreler, Neo-
Redneck Retiree, Not Quite Clueless Power User
NM Public
> On Mon, 20 Mar 2006 10:59:33 +0000, NM Public wrote:
> [snip]
>
> Dovecot is the IMAP server and my disk space is unlimited. Dave
> also says, "Sounds like you are looking at using pine on titan
> as your master. If you have trouble, have her send me the
> config and I'll set it up for you." (I seem to've forgotten to
> ask about the separator.)
Before I can walk you through setting up a remote address book
and remote config file, I need to know the exact way that you
access your IMAP server from Pine. To help me figure that out,
please open your pinerc file with a text editor, such as 'pico
-w' and copy & paste the folder-collections variable into a reply
to this message. You can obfuscate the server name by using
something like 'imap.server.name' instead of the actual server
name.
Thanks!
Beartooth Stafwright
> Before I can walk you through setting up a remote address book and remote
> config file, I need to know the exact way that you access your IMAP server
> from Pine. To help me figure that out, please open your pinerc file with a
> text editor, such as 'pico -w' and copy & paste the folder-collections
> variable into a reply to this message. You can obfuscate the server name
> by using something like 'imap.server.name' instead of the actual server
> name.
incoming-folders=VCDL {imap.server.name/novalidate-cert}VCDL,
ARTEMIS {imap.server.name/novalidate-cert}ARTEMIS,
ACFG ACFG,
virus-a VA,
bblx bblx
folder-collections=Mail mail/[]
[.... lots not set]
read-message-folder=Apending
[.sig I change frequently]
address-book=.addressbook
I hope that's all the right stuff!
Nancy McGough
>
>> Before I can walk you through setting up a remote address book
>> and remote config file, I need to know the exact way that you
>> access your IMAP server from Pine. To help me figure that out,
>> please open your pinerc file with a text editor, such as 'pico
>> -w' and copy & paste the folder-collections variable into a
>> reply to this message. You can obfuscate the server name by
>> using something like 'imap.server.name' instead of the actual
>> server name.
>
> incoming-folders=VCDL {imap.server.name/novalidate-cert}VCDL,
> ARTEMIS {imap.server.name/novalidate-cert}ARTEMIS,
> ACFG ACFG,
> virus-a VA,
> bblx bblx
>
> folder-collections=Mail mail/[]
>
>
> [.sig I change frequently]
>
> address-book=.addressbook
Excellent, this is all very helpful Beartooth. OK, I'm going to
first walk you through setting up an IMAP-accessible address book
that you will be able to use from all your pines on all your
machines. After we set this up, we'll move on to the pinerc and
the folder-collections. Note that I have done this many times and
it is almost always a PITA so be prepared for that! But, once it
is set up, it is a dream!
1] Go to your system that has your most up-to-date .addressbook.
2] Back up your .addressbook using something like this:
cp -i ~/.addressbook ~/.addressbook-2006-04-08
3] Copy your address book to your IMAP server using this command:
pine -copy_abook ~/.addressbook \{imap.server.name/novalidate-cert\}zz-abook
Make sure you replace 'imap.server.name' with your IMAP server's
name.
4] Test that this IMAP-accessible address book works by starting
pine with this command-line argument
pine -address-book=\{imap.server.name/novalidate-cert\}zz-abook
After you do this, please post and tell use what happened. There
are lots of possible problems in these steps. If it works, we'll
continue. If not, I'll help you troubleshoot.
More later,
Good luck!
Nancy
Beartooth Stafwright
> Excellent, this is all very helpful Beartooth. OK, I'm going to first
> walk you through setting up an IMAP-accessible address book that you
> will be able to use from all your pines on all your machines. After we
> set this up, we'll move on to the pinerc and the folder-collections.
> Note that I have done this many times and it is almost always a PITA so
> be prepared for that! But, once it is set up, it is a dream!
>
Well, the most up to date anything is of course on the IMAP Pine account
on Ddave's machine, the one we're calling imap.server.name in public; so I
forwarded your whole post (rest snipped here) to him, with a couple of
comments, for him to sign off on before I do any of it.
I'm not in doubt that he will; and since he doesn't run Pine himself, he's
not too likely to introduce any refinements or make sure I understand what
I'm doing in advance (as he often does when I want to make some other use
of his machine; he's a very helpful guy, and I hope I meet him some day);
but imnsho punctilio is never really wasted, as Hal Clement might've said
... <grin>
Stay tuned.
Beartooth Stafwright
>.... so I forwarded your whole post (rest snipped here) to him, with a
> couple of comments, for him to sign off on before I do any of it.
> ... he's a very helpful guy,
> Stay tuned.
WhuddItellya? Here's his reply : "I've made a complete backup of your
directory in case something goes wrong. Go ahead and give it a shot and
see if you can get it working the way you want."
NM Public
>
> WhuddItellya? Here's his reply : "I've made a complete backup
> of your directory in case something goes wrong. Go ahead and
> give it a shot and see if you can get it working the way you
> want."
Wow, he is truly a very helpful guy -- you are very lucky to have
someone like that helping you out!
Let us know how stage one of your conversion to the
all-imap-all-the-time way of doing things goes. When you report
back, please also include a list of all the machines which you
use to access your mail and what operating system they use,
e.g.,:
desktop1 linux
desktop2 ms-windows
desktop3 linux
remote-ddave freebsd
remote-freeshell netbsd
etc.
Good luck,
You will (hopefully) be free of email lockin soon!
Beartooth Stafwright
> Excellent, this is all very helpful Beartooth. OK, I'm going to first walk
> you through setting up an IMAP-accessible address book that you will be
> able to use from all your pines on all your machines. After we set this
> up, we'll move on to the pinerc and the folder-collections. Note that I
> have done this many times and it is almost always a PITA so be prepared
> for that! But, once it is set up, it is a dream!
>
>
> 1] Go to your system that has your most up-to-date .addressbook.
>
> 2] Back up your .addressbook using something like this:
>
> cp -i ~/.addressbook ~/.addressbook-2006-04-08
Done.
> 3] Copy your address book to your IMAP server using this command:
>
> pine -copy_abook ~/.addressbook
> \{imap.server.name/novalidate-cert\}zz-abook
>
> Make sure you replace 'imap.server.name' with your IMAP server's name.
First snag (probably first PITA) :
That shows as two lines in my reader; I presume it's all one in fact.
So I tried it with a space between k and \ -- on my own machine (which is
still called localhost; gotta fix that some day ...), and without hitting
enter. But it interpreted the space as an enter command, apparently, and
gave me a long error message.
So I pasted one half and then the other, without any space, into
imap.server.name (which I'm going to start calling simply titan), and then
hit enter. It gave me a long error message -- the same one, I think.
Then I tried just c&p on "pine -copy_abook ~/.addressbook" (without
"") into titan ; hit enter ; and got what I think is still the same
message. Here it is :
[karhunhammas@titan ~]$ pine -copy_abook ~/.addressbook
Argument Error: missing argument for option "-copy_abook"
Usage: pine -copy_abook <local_abook> <remote_abook>
Argument Error: conflicting action: "/home/karhunhammas/.addressbook"
Possible Starting Arguments for Pine program:
Argument Meaning
<addrs>... Go directly into composer sending to given address
List multiple addresses with a single space between them.
Standard input redirection is allowed with addresses.
Note: Places addresses in the "To" field only.
-attach <file> Go directly into composer with given file
-attachlist <file-list>
-attach_and_delete <file>
Go to composer, attach file, delete when finished
Note: Attach options can't be used if -f, -F
added to Attachment list. Attachlist must be the last
option on the command line
-bail Exit if pinerc file doesn't already exist
-f <folder> Folder - give folder name to open
-c <number> Context - which context to apply to -f arg
-F <file> File - give file name to open and page through and
forward as email.
-h Help - give this list of options
-k Keys - Force use of function keys
-z Suspend - allow use of ^Z suspension
-r Restricted - can only send mail to oneself
-sort <sort> Sort - Specify sort order of folder:
subject, arrival, date, from, size, /reverse
-i Index - Go directly to index, bypassing main menu
-I <keystroke_list> Initial keystrokes to be executed
-n <number> Entry in index to begin on
-o ReadOnly - Open first folder read-only
-conf Configuration - Print out fresh global configuration. The
values of your global configuration affect all Pine users
on your system unless they have overridden the values in their
pinerc files.
-pinerc <file> Configuration - Put fresh pinerc configuration in <file>
-p <pinerc> Use alternate .pinerc file
-P <pine.conf> Use alternate pine.conf file
-passfile <fully_qualified_filename> Set the password file to something other
than the default
-nowrite_passfile Read from a passfile if there is one, but never offer to write a password to the passfile
-x <config> Use configuration exceptions in <config>.
Exceptions are used to override your default pinerc
settings for a particular platform, can be a local file or
a remote folder.
-v Version - show version information
-version Version - show version information
-supported List supported options
-url <url> Open the given URL
Note: Can't be used if -f, -F
Standard input redirection is not allowed with URLs.
For mailto URLs, 'body='text should be used in place of
input redirection.
-create_lu <abook_file> <ab_sort_type> create .lu from script
-copy_pinerc <local_pinerc> <remote_pinerc> copy local pinerc to remote
-copy_abook <local_abook> <remote_abook> copy local addressbook to remote
-convert_sigs -p <pinerc> convert signatures to literal signatures
-<option>=<value> Assign <value> to the pinerc option <option>
e.g. -signature-file=sig1
e.g. -color-style=no-color
e.g. -feature-list=enable-sigdashes
Note: feature-list is additive.
You may leave off the "feature-list=" part of that,
e.g. -enable-sigdashes
You have new mail in /var/spool/mail/karhunhammas
[karhunhammas@titan ~]$
(Karhunhammas, btw, is Finnish for "bear's tooth" -- I used to catalog
Finnish materials into the Library of Congress, where I first got
online, before I retired ...)
Wherever that great long error message comes from, it looks cram-full
of useful info. I'd like to take the time, some day, to try to get my head
around it. Anybody know offhand how to access it without making the error??
NM Public
That command is all on one line and you should NOT try to copy &
paste it because you seem to be copying an invisible linefeed.
Instead type the command BY HAND and make sure you
1] precede each curly brace with a backslash
2] replace imap.server.name with your IMAP server's name
I know it is a pain to type this type of command but it is
essential for debugging purposes. If you get another error, copy
and paste the EXACT command that you typed and the EXACT error
message and post it here.
Good luck,
Nancy
PS - Yes, this is the first PITA; more to come no doubt!
Beartooth Stafwright
> Sur 2006-04-11, Beartooth Stafwright skribis:
>>>
>>> pine -copy_abook ~/.addressbook
>>> \{imap.server.name/novalidate-cert\}zz-abook
>
> That command is all on one line and you should NOT try to copy & paste it
> because you seem to be copying an invisible linefeed. Instead type the
> command BY HAND and make sure you
>
> 1] precede each curly brace with a backslash 2] replace imap.server.name
> with your IMAP server's name
OK I tried. I still got an error. But this time, if I hit the up error, I
do at least get the whole line, and no error so long as I don't follow the
arrow with the enter key.
So I *think* the problem (or at least one problem) is that I can't be sure
where there are spaces between characters. That is a common problem for
me, and the reason I do use c&p to the max, ordinarily.
It looks from here like there's a space between pine and -copy, and
another between the first abook and the ~
I deleted that space, and tried again. Still got the error. The only space
left was between pine and -copy. So I took that out, too, and made it all
one solid command, with no spaces anywhere; that at least gave me a
different error.
> I know it is a pain to type this type of command but it is essential for
> debugging purposes. If you get another error, copy and paste the EXACT
> command that you typed and the EXACT error message and post it here.
[karhunhammas@titan ~]$ pine-copy_abook~/.addressbook\{titan.lserv.com/novalidate-cert\{zz-abook
-bash: pine-copy_abook~/.addressbook{titan.lserv.com/novalidate-cert{zz-abook: No such file or directory
[karhunhammas@titan ~]$
On my screen, one line ends with abook; the next begins with -bash.
And I find it very easy to believe both that there will be more, and that
it's worth it, especially on your say-so. Besides, I'm stubborn. <grin>
NM Public
>
I'm stubborn too so, as long as you're also patient, we will
succeed! New Strategy: Instead of using Pine command-line
arguments, we're going to use Pine's built-in Z
(RemoteConfigSetup) command. In other words, we are starting
over. Forget everything we've already tried and do this:
0] Back up your pinerc by typing
cp -i ~/.pinerc ~/.pinerc-2006-04-12
1] Start pine
2] Type MSZ (which means Main> Setup> RemoteConfigSetup)
3] Accept all the default suggestions EXCEPT make sure that the
server name is your IMAP server name, e.g., for the address book,
you'll use something like this:
Server Name : titan.lserv.com/novalidate-cert
Folder Name : remote_addrbook
NickName : Remote Address Book
4] After you've completed the RemoteConfigSetup, quit Pine.
5] Open your ~/.pinerc and copy this setting:
address-book=
If there are multiple lines for the address-book setting, copy
all of them.
6] Post a reply to this message and tell us what happened when
you ran MSZ and include the current 'address-book' setting.
This is a slow process, but hopefully it will be worth it when
it's all over.
Nancy
NM Public
>
Beartooth, here is another thing for you to do:
0] back up your ~/.pinerc
1] edit your ~/.pinerc using, e.g.:
pico -w ~/.pinerc
2] go to the folder-collections variable and change it from what
you wrote above to this:
folder-collections=Titan {titan.lserv.com/novalidate-cert}[],
Local mail/[]
3] save and quit pico
4] run pine and go to your FOLDER LIST by typing
M L
5] you should see (at least) the 2 collections that were set in
Step 2. Make sure that both of these folder collections work.
I.e., display a list of folders when you press ENTER on this:
[Select Here to See Expanded List]
Let us know if this works,
Thanks,
NM Public
IMAP server. After you do that, which is the first stage of
Pine's MSZ command, you can skip the other stages. It is fine if
you do them though. We will clean everything up ultimately. For
now, we just need to make sure that you can use a remote address
book and most importantly that I figure out what IMAP server
specification works for your system!
HTH,
Nancy
Sur 2006-04-12, NM Public skribis:
Beartooth Stafwright
> Sur 2006-04-11, Beartooth Stafwright skribis:
>>
>> Besides, I'm stubborn. <grin>
>
> I'm stubborn too so, as long as you're also patient, we will succeed!
> New Strategy: Instead of using Pine command-line arguments, we're going
> to use Pine's built-in Z (RemoteConfigSetup) command.
The pinemasters never cease to amaze me. There were a couple things on
that screen (including the Z command) whose very existence I hadn't dreamt
of.
> In other words, we are starting over. Forget everything we've already
> tried and do this:
>
> 0] Back up your pinerc by typing
>
> cp -i ~/.pinerc ~/.pinerc-2006-04-12
>
> 1] Start pine
>
> 2] Type MSZ (which means Main> Setup> RemoteConfigSetup)
All done, no sweat.
> 3] Accept all the default suggestions EXCEPT make sure that the server
> name is your IMAP server name, e.g., for the address book, you'll use
> something like this:
>
> Server Name : titan.lserv.com/novalidate-cert Folder Name :
> remote_addrbook
> NickName : Remote Address Book
Done, no sweat.
> 4] After you've completed the RemoteConfigSetup, quit Pine.
It asked a couple questions -- one was about turning a .sig into whatever
it is that seems to mean a digital photo of an ink signature; I told that
no. Otherwise, I took the defaults.
> 5] Open your ~/.pinerc and copy this setting:
>
> address-book=
On the way to that I found a thing we haven't mentioned. Dunno if it's
relevant :
###################### Collections, Folders, and Files #####################
# List of incoming msg folders besides INBOX, e.g. ={host2}inbox,
{host3}inbox
# Syntax: optnl-label {optnl-imap-host-name}folder-path
incoming-folders=VCDL {titan.lserv.com/novalidate-cert}VCDL,
ARTEMIS {titan.lserv.com/novalidate-cert}ARTEMIS, ACFG ACFG,
virus-a VA,
bblx bblx
(I need to ask, some day, after this job's done, about folder pairs.)
Done. I now see :
# List of file or path names for personal addressbook(s). # Default:
~/.addressbook (Unix) or \PINE\ADDRBOOK (PC) # Syntax: optnl-label
path-name
address-book=.addressbook,
"Remote Address Book"
{titan.lserv.com/novalidate-cert}remote_addrbook
> If there are multiple lines for the address-book setting, copy all of
> them.
>
> 6] Post a reply to this message and tell us what happened when you ran
> MSZ and include the current 'address-book' setting.
>
> This is a slow process, but hopefully it will be worth it when it's all
> over.
So far, doing it this way seems a lot simpler and easier. I hope we're in
process of drafting a FAQ item ...
NM Public
> address-book=.addressbook,
> "Remote Address Book"
> {titan.lserv.com/novalidate-cert}remote_addrbook
Hooray! Excellente! Next step is to edit the above so it only
contains the "Remote Address Book", i.e., change the above to
this:
address-book="Titan" {titan.lserv.com/novalidate-cert}remote_addrbook
^
one or more spaces here
That is all on one line. I'm calling it "Titan" but you can call
it whatever you like -- use something that will remind you that
it's on Ddave's IMAP server.
After you have edited both this address-book variable and the
folder-collections variable, which I wrote about in a separate
message, start pine by typing:
pine
and make sure that you can use your address book, and all your
folder collections. Also test:
composing and sending
composing and postponing
saving a message
Let me know when you've tested all this,
Nancy
BTW - I am going to be off the Net for a little while but will
check back later. Good luck!
Beartooth Stafwright
> Sur 2006-04-08, Beartooth Stafwright skribis:
>>
>> folder-collections=Mail mail/[]
>
> Beartooth, here is another thing for you to do:
>
> 0] back up your ~/.pinerc
>
> 1] edit your ~/.pinerc using, e.g.:
>
> pico -w ~/.pinerc
>
> 2] go to the folder-collections variable and change it from what you wrote
> above to this:
>
> folder-collections=Titan {titan.lserv.com/novalidate-cert}[],
> Local mail/[]
OK; I assume that the apparent indentation above is an artifact, like the
right angle brackets for quotes, and not necessary; but I did make sure of
a new line. So I now have
# List of directories where saved-message folders may be. First one is
# the default for Saves. Example: Main {host1}mail/[], Desktop mail\[]
# Syntax: optnl-label {optnl-imap-hostname}optnl-directory-path[]
folder-collections=Titan {titan.lserv.com/novalidate-cert}[],
Local mail/[]
> 3] save and quit pico
Done.
> 4] run pine and go to your FOLDER LIST by typing
>
> M L
>
> 5] you should see (at least) the 2 collections that were set in Step 2.
> Make sure that both of these folder collections work. I.e., display a list
> of folders when you press ENTER on this:
>
> [Select Here to See Expanded List]
I don't see that at all; but maybe it's because I have this in my M>S>C
setup :
[ ] enable-lame-list-mode
[X] expanded-view-of-folders
[ ] quell-empty-directories
[ ] separate-folder-and-directory-entries
> Let us know if this works,
What I do see is below, followed by what seems to be my same list of
folders (with some blank space at the bottom and a line (which may
or may not be new; I have the folders names to minimize ever having
to go clear down) saying " [END of folder list]) :
--------------------------------------------------------------------
Folder-Collection <Incoming-Folders>
--------------------------------------------------------------------
INBOX VCDL ARTEMIS ACFG virus-a bblx
--------------------------------------------------------------------
Folder-Collection <Titan>
-------------------------------------------------------------------------------------
[and then the list I'm used to]
So have I goofed, or is it just the expanded-view-of-folders showing?
Beartooth Stafwright
> Sur 2006-04-12, Beartooth Stafwright skribis:
>> address-book=.addressbook,
>> "Remote Address Book"
>> {titan.lserv.com/novalidate-cert}remote_addrbook
>
> Hooray! Excellente! Next step is to edit the above so it only contains the
> "Remote Address Book", i.e., change the above to this:
>
> address-book="Titan" {titan.lserv.com/novalidate-cert}remote_addrbook
> ^
> one or more spaces here
>
> That is all on one line. I'm calling it "Titan" but you can call it
> whatever you like -- use something that will remind you that it's on
> Ddave's IMAP server.
>
> After you have edited both this address-book variable and the
> folder-collections variable, which I wrote about in a separate message,
> start pine by typing:
>
> pine
>
> and make sure that you can use your address book, and all your folder
> collections. Also test:
>
> composing and sending
> composing and postponing
> saving a message
>
> Let me know when you've tested all this,
It all works just fine.
> BTW - I am going to be off the Net for a little while but will check back
> later. Good luck!
Even that is good : I also have a couple errands. <grin>
Beartooth Stafwright
> PS - The instructions below are to get your address book on the IMAP
> server. After you do that, which is the first stage of Pine's MSZ command,
> you can skip the other stages. It is fine if you do them though. We will
> clean everything up ultimately.
OK, afaik, I did it all, with no problem.
> For now, we just need to make sure that
> you can use a remote address book and most importantly that I figure out
> what IMAP server specification works for your system!
Here I'm not sure I follow: how do I test using a remote addressbook? I
haven't yet that I know of ...
> Sur 2006-04-12, NM Public skribis:
>> Sur 2006-04-11, Beartooth Stafwright skribis:
>>>
>>> Besides, I'm stubborn. <grin>
>>
>> I'm stubborn too so, as long as you're also patient, we will succeed!
>> New Strategy: Instead of using Pine command-line arguments, we're going
>> to use Pine's built-in Z (RemoteConfigSetup) command. [snipperoo]
NM Public
>
> Local mail/[]
You need to put at least one space in front of 'Local mail/[]',
i.e.,:
folder-collections=Titan {titan.lserv.com/novalidate-cert}[],
Local mail/[]
^
make sure there is a space here!
Also, to make sure things work from any of the systems that you
run pine on, I suggest that you change:
titan.lserv.com/novalidate-cert
to:
titan.lserv.com/novalidate-cert/user=karhunhammas
^^^^^^^^^^^^^^^^^
where you replace 'karhunhammas' with your username on titan.
Let us know what happens when after you make these changes. It's
night here in London so I probably won't be on the Net much more
today.
Hasta manana!
Beartooth Stafwright
> Sur 2006-04-12, Beartooth Stafwright skribis:
>>
>> folder-collections=Titan {titan.lserv.com/novalidate-cert}[], Local
>> mail/[]
>
> You need to put at least one space in front of 'Local mail/[]', i.e.,:
>
> folder-collections=Titan {titan.lserv.com/novalidate-cert}[],
> Local mail/[]
> ^
> make sure there is a space here!
OK; I gave it three.
>
>
> Also, to make sure things work from any of the systems that you run pine
> on, I suggest that you change:
>
> titan.lserv.com/novalidate-cert
>
> to:
>
> titan.lserv.com/novalidate-cert/user=karhunhammas
> ^^^^^^^^^^^^^^^^^
>
> where you replace 'karhunhammas' with your username on titan.
OK. Since the line had "}[]," at the end, I put it in between cert and }
>
> Let us know what happens when after you make these changes. It's night
> here in London so I probably won't be on the Net much more today.
London, eh? Well, if you should ever have occasion to pass nigh Virginia
Tech (in Blacksburg, half an hour or so from Roanoke) you and anyone with
you are always welcome here. I owe you big time already, and both of us
enjoy extending our hospitality.
I made the changes without thinking to close pine first. It still seems to
work OK.
There is one problem, however. At the bottom of Folder-Collection <Titan>
I now also see Folder-Collection <Local> -- with what appear to be all the
same folders. But some in the Titan collection have no messages, even
though I know they should have a lot. Maybe that's part of normal cleanup;
I don't see a pattern yet ...
> Hasta manana!
I'll be here, with bells on.
NM Public
>>
>> folder-collections=Titan {titan.lserv.com/novalidate-cert}[],
>> Local mail/[]
>
> Virginia Tech (in Blacksburg, half an hour or so from Roanoke)
> you and anyone with you are always welcome here. I owe you big
> time already, and both of us enjoy extending our hospitality.
Thank you for the invitation Beartooth -- you certainly don't owe
me anything, especially since I've got you in a kind of broken
situation at the moment!
> There is one problem, however. At the bottom of
> Folder-Collection <Titan> I now also see Folder-Collection
> <Local> -- with what appear to be all the same folders. But
> some in the Titan collection have no messages, even though I
> know they should have a lot. Maybe that's part of normal
> cleanup; I don't see a pattern yet ...
>
>> Hasta manana!
>
> I'll be here, with bells on.
OK, get your bells on and let's see what progress we can make...
Can you quit pine and open your .pinerc and copy & paste the
folder-collections variable setting into a followup to this
message?
I'm glad to see that you seem to be as patient and stubborn as I
am!
Beartooth Stafwright
> OK, get your bells on and let's see what progress we can make...
>
> Can you quit pine and open your .pinerc and copy & paste the
> folder-collections variable setting into a followup to this message?
# List of directories where saved-message folders may be. First one is
# the default for Saves. Example: Main {host1}mail/[], Desktop mail\[]
# Syntax: optnl-label {optnl-imap-hostname}optnl-directory-path[]
folder-collections=Titan {titan.lserv.com/novalidate-cert/user=karhunhammas}[],
Local mail/[]
NM Public
Thank you. Try this: Quit Pine, edit your .pinerc and change the
folder-collections to this:
folder-collections=Titan {titan.lserv.com/novalidate-cert/user=karhunhammas}[]
# Local mail/[]
^
Note that this line is commented out.
Save and quit your editor, fire up pine, type 'ML' and see if the
Titan collection lists all your folders. If it does not, please
ask Ddave what username you should use to connect to his IMAP
server. It might be something like this:
We need to know this username so you can successfully connect to
the IMAP server from *anywhere*.
Thanks,
Beartooth Stafwright
> Sur 2006-04-13, Beartooth Stafwright skribis:
>> folder-collections=Titan
>> {titan.lserv.com/novalidate-cert/user=karhunhammas}[],
>> Local mail/[]
>
> Thank you. Try this: Quit Pine,
I told it q, and forgot to wait for it to purge my inbox and check; so I
guess it was only half closed.
> edit your .pinerc and change the
> folder-collections to this:
>
> folder-collections=Titan
> {titan.lserv.com/novalidate-cert/user=karhunhammas}[] # Local mail/[]
> ^
> Note that this line is commented out.
In my .pinerc display, a new line begins after the [] -- three spaces,
then Local main/[], then one space; I commented that line out.
> Save and quit your editor, fire up pine, type 'ML' and see if the Titan
> collection lists all your folders.
None are obviously missing, and the ones I use most seem to be where they
were before in the list. But there are at least three new ones:
remote_addrbook, remote_pinerc, and td/; I haven't looked at the messages,
but the folder indexes look like this :
PINE 4.64 MESSAGE INDEX <Titan> remote_addrbook Msg 4 of 4 NEW +
U 1 Apr 12 Pine Remote Data (735) Header Message for Remote Data
U 2 Apr 12 Pine Remote Data (380) Pine Remote Data Container
3 Apr 12 Pine Remote Data (94K) Pine Remote Data Container
N 4 Apr 13 Pine Remote Data (94K) Pine Remote Data Container
***** *****
PINE 4.64 MESSAGE INDEX <Titan> remote_pinerc Msg 2 of 2 NEW +
N 1 Apr 12 Pine Remote Data (708) Header Message for Remote Data
N 2 Apr 12 Pine Remote Data (32K) Pine Remote Data Container
***** *****
and (with a lot of space in the middle)
PINE 4.64 FOLDER LIST <Titan> remote_pinerc 2 Msgs +
-------------------------------------------------------------------------------------Folder-Collection <Incoming-Folders>
-------------------------------------------------------------------------------------
INBOX VCDL ARTEMIS ACFG virus-a bblx
-------------------------------------------------------------------------------------Folder-Collection <Titan>
Dir: td/
-------------------------------------------------------------------------------------
fc
[Now in directory: {titan.lserv.com/novalidate-cert/user=karhunhammas}td/]
Once I'm in td/, L no longer gets me back to the list; but I can put the
cursor on INBOX, open it, and do M then L to get back.
> If it does not, please ask Ddave what
> username you should use to connect to his IMAP server. It might be
> something like this:
>
> karhun...@domain.name
>
> We need to know this username so you can successfully connect to the IMAP
> server from *anywhere*.
So does the above answer this? Particularly that line :
[Now in directory: {titan.lserv.com/novalidate-cert/user=karhunhammas}td/] ??
Or do I need to ask? (It may take a day or two for him to get to it if I
do.)
NM Public
forward with this. One lesson I've learned so far is that the
Pine 'MSZ' (RemoteConfigSetup) user interface needs improvement.
Beartooth Stafwright wrote:
>
>> Save and quit your editor, fire up pine, type 'ML' and see if the Titan
>> collection lists all your folders.
>
> None are obviously missing, and the ones I use most seem to be where they
> were before in the list. But there are at least three new ones:
> remote_addrbook, remote_pinerc, and td/;
The 'remote_addrbook' and 'remote_pinerc' are the IMAP folders
that contain your address book and pinerc are stored -- I'm happy
to see that they are there! I don't know what 'td/' is, but let's
not worry about it for now.
The next step is to upload the latest version of your pinerc to
the 'remote_pinerc' folder. To do that, follow these steps.
1] Make sure you are on Ddave's system.
2] Start Pine and run MSZ.
3] I recommend that you accept all the defaults, including the
signature and the config suggestions.
4] After you upload the config, Pine will display a screen that
tells you what command you need to use to run Pine. It will look
something like this:
pine -p {server.name/flag}remote_pinerc
Copy this command and save it somewhere.
5] After Pine has finished doing MSZ, reply to this message and
paste the command that it told you in step #4.
Also, please tell me what shell you are using on Ddave's system,
e.g., bash or csh or tcsh.
I'll try not to take so long to reply this time.
Thank you and good luck :-),
Nancy
Infinite Ink: <http://www.ii.com>
Deflexion & Reflexion: <http://deflexion.com>
--
Sent with SeaMonkey Suite
Beartooth Stafwright
> OK, I'm back after a long weekend... Let's keep moving slowly forward
> with this. One lesson I've learned so far is that the Pine 'MSZ'
> (RemoteConfigSetup) user interface needs improvement.
[...]
> The 'remote_addrbook' and 'remote_pinerc' are the IMAP folders that
> contain your address book and pinerc are stored -- I'm happy to see that
> they are there! I don't know what 'td/' is, but let's not worry about it
> for now.
> The next step is to upload the latest version of your pinerc to the
> 'remote_pinerc' folder. To do that, follow these steps.
>
> 1] Make sure you are on Ddave's system.
>
> 2] Start Pine and run MSZ.
>
> 3] I recommend that you accept all the defaults, including the signature
> and the config suggestions.
OK, done. Very hesitantly, but done. (I have a large collection of
signature files and change them often -- and in the past have usually used
a different one locally than remotely, as one way among several to try to
stave off the chaos & confusion endemic to my undertakings ...)
> 4] After you upload the config, Pine will display a screen that tells
> you what command you need to use to run Pine. It will look something
> like this:
>
> pine -p {server.name/flag}remote_pinerc
>
> Copy this command and save it somewhere.
Done -- with a question : that screen says "to use pine from *this*
computer" (my emphasis) -- i.e., the remote one, i.e. Lserv. So I *think*
it means I'll ssh into it as before and *then* use the command -- i.e.,
on lserv, not on the home machines, presumably in the form of an alias
(which I think I can look up how to make). Right?
> 5] After Pine has finished doing MSZ, reply to this message and paste
> the command that it told you in step #4.
pine -p "{titan.lserv.com/novalidate-cert/user=karhunhammas}remote_pinerc"
> Also, please tell me what shell you are using on Ddave's system, e.g.,
> bash or csh or tcsh.
I *think* it's bash, as it is on my own. How do I check?
Note: Ddave has just answered my question about IMAP userid with one of
his own : "Are you trying to connect to IMAP remotely? If so, you may not
be able to until I open it on the firewall."
I replied, drawing attention to your comment :
> > > We need to know this username so you can successfully connect to the IMAP
> > > server from *anywhere*,
and interpreting it thus :
I think so -- but I'm not sure from where : my place, or adelphia, or
possibly literally anywhere, including for instance county public
libraries running M$ ... Is that what I should ask : define anywhere? I
certainly won't ask for any more openings in your firewall than I need.
> I'll try not to take so long to reply this time. Thank you and good luck
Not a problem: I was in no shape to deal with this anyway till today.
NM Public
>
> pine -p "{titan.lserv.com/novalidate-cert/user=karhunhammas}remote_pinerc"
>
>> Also, please tell me what shell you are using on Ddave's system, e.g.,
>> bash or csh or tcsh.
>
> I *think* it's bash, as it is on my own. How do I check?
Excellent! One way to check your shell is to type this:
chsh
which means 'change shell'. It will display your Shell and
possibly other information. Exit out of that 'chsh' screen
without making any changes.
We need to know your shell in order to correctly create an alias
for pine. Please let me know what shell you are using and if you
know how to create aliases on your Ddave account. (And if you
already use any pine alias(es)?)
> Note: Ddave has just answered my question about IMAP userid with one of
> his own : "Are you trying to connect to IMAP remotely? If so, you may not
> be able to until I open it on the firewall."
Yes, our ultimate goal is for you to be able to use his IMAP
server from outside his system. Is he willing to open his
firewall for you to do this?
For now, we'll focus on getting it working from your account on
his system. (BTW, we will deal with your pine signatures
eventually so don't stress out about those!)
> Not a problem: I was in no shape to deal with this anyway till today.
I'm sorry to hear about your gout and I hope you're feeling
better. Isn't gout a good excuse to eat lots of cherries,
blueberries, and strawberries every day?! I hope you like berries
and can eat lots of them every day! (IMHO berries are one of the
secrets to health in general...)
Bye for now,
Beartooth Stafwright
> Beartooth Stafwright wrote:
>>
>> pine -p
>> "{titan.lserv.com/novalidate-cert/user=karhunhammas}remote_pinerc"
>>
>>> Also, please tell me what shell you are using on Ddave's system, e.g.,
>>> bash or csh or tcsh.
>>
>> I *think* it's bash, as it is on my own. How do I check?
>
>
> Excellent! One way to check your shell is to type this:
>
> chsh
>
> which means 'change shell'. It will display your Shell and possibly other
> information. Exit out of that 'chsh' screen without making any changes.
I hope I haven't disimproved anything :
[karhunhammas@titan ~]$ chsh
Changing shell for karhunhammas.
Password:
^C did nothing, so I gave it the password. Then I tried it again, hoping
it'd be a toggle ...
You have mail in /var/spool/mail/karhunhammas
[karhunhammas@titan ~]$ chsh
Changing shell for karhunhammas.
Password:
New shell [/bin/bash]:
At that point I hit enter,
> We need to know your shell in order to correctly create an alias for pine.
> Please let me know what shell you are using and if you know how to create
> aliases on your Ddave account. (And if you already use any pine
> alias(es)?)
I've heard of aliases, but never used one afaik.
>
>> Note: Ddave has just answered my question about IMAP userid with one of
>> his own : "Are you trying to connect to IMAP remotely? If so, you may
>> not be able to until I open it on the firewall."
>
> Yes, our ultimate goal is for you to be able to use his IMAP server from
> outside his system. Is he willing to open his firewall for you to do this?
I take it he is, yes.
> For now, we'll focus on getting it working from your account on his
> system. (BTW, we will deal with your pine signatures eventually so don't
> stress out about those!)
>
>> Not a problem: I was in no shape to deal with this anyway till today.
>
> I'm sorry to hear about your gout and I hope you're feeling better. Isn't
> gout a good excuse to eat lots of cherries, blueberries, and strawberries
> every day?! I hope you like berries and can eat lots of them every day!
> (IMHO berries are one of the secrets to health in general...)
Much better thanks. I'm not much on fresh fruit -- can never remember to
eat it while it lasts -- but usually eat some dried after dinner. It's
much chewier that way ... <grin>
NM Public
>
> New shell [/bin/bash]:
>
> I've heard of aliases, but never used one afaik.
OK, now we're going to create a bash alias for pine.
1] To find out the absolute path to pine, type this:
which pine
This path will be used in Step #3.
2] To find out what aliases are currently in set up, type this:
alias
Let me know if any of your current aliases are pine aliases.
3] To edit your .bash_profile, type this:
pico -w ~/.bash_profile
Add this line to the file:
alias pine='/path/to/pine -p "{titan.lserv.com/novalidate-cert/user=karhunhammas}remote_pinerc"'
Note:
* this is all on one line
* replace /path/to/pine with the path from Step #1
* the outer single quotes and inner double quotes are essential!
4] Save and quit pico.
5] To set this alias, logout and then log back in. Then type:
alias
The pine alias you just created should be listed.
6] Now the big test: Type this:
pine
And let us know if it works!
> Much better thanks. I'm not much on fresh fruit -- can never
> remember to eat it while it lasts -- but usually eat some dried
> after dinner. It's much chewier that way ... <grin>
If you bought fresh organic berries here in London, you would
definitely remember to eat them because they are *VERY*
expensive. But worth it IMHO.
Good luck with this alias stuff, lots of potetial PITAs, but we
will prevail!
Beartooth Stafwright
> OK, now we're going to create a bash alias for pine.
>
> 1] To find out the absolute path to pine, type this:
>
> which pine
>
> This path will be used in Step #3.
[karhunhammas@titan ~]$ which pine
/usr/bin/pine
[karhunhammas@titan ~]$
> 2] To find out what aliases are currently in set up, type this:
>
> alias
>
> Let me know if any of your current aliases are pine aliases.
[karhunhammas@titan ~]$ alias
alias cp='cp -i'
alias l.='ls -d .* --color=tty'
alias la='ls -la'
alias ll='ls -l --color=tty'
alias ls='ls --color=tty'
alias mv='mv -i'
alias rm='rm -i'
alias vi='vim'
alias which='alias | /usr/bin/which --tty-only --read-alias --show-dot --show-tilde'
[karhunhammas@titan ~]$
Doesn't look it to me -- I don't see pine mentioned. I can't think when
I've used any of those, at least explicitly. Of course, I use ls, mv, and
rm quite often, without thinking about it ...
> 3] To edit your .bash_profile, type this:
>
> pico -w ~/.bash_profile
That gives me :
# .bash_profile
# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
# User specific environment and startup programs
PATH=$PATH:$HOME/bin
export PATH
unset USERNAME
> Add this line to the file:
To the file where? Below the line about startup programs? On the bottom?
In place of the PATH= line??
> alias pine='/path/to/pine -p
> "{titan.lserv.com/novalidate-cert/user=karhunhammas}remote_pinerc"'
>
> Note:
> * this is all on one line
> * replace /path/to/pine with the path from Step #1 * the outer single
> quotes and inner double quotes are essential!
Is there, as I think, a space between -p and the long expression? Or not?
> 4] Save and quit pico.
>
>
> 5] To set this alias, logout and then log back in. Then type:
Log out? You mean exit my ssh session?
I'm guessing it's likely less trouble in the long run to get the answers I
just asked for than to experiment, and have to clean up. In particular,
I shudder to think what a muddled .bash_profile might be able to do. So
I'll wait for them before I do aught else.
> Good luck with this alias stuff, lots of potetial PITAs, but we will
> prevail!
> Nancy
--
NM Public
>
>> Add this line to the file:
>
> To the file where? Below the line about startup programs? On the bottom?
> In place of the PATH= line??
Anywhere is fine, but since you asked, I suggest the bottom. Oh
yes, make a backup first by typing this:
cp -i ~/.bash_profile ~/.bash_profile-2006-04-18
>> alias pine='/path/to/pine -p "{titan.lserv.com/novalidate-cert/user=karhunhammas}remote_pinerc"'
>>
>> Note:
>> * this is all on one line
>> * replace /path/to/pine with the path from Step #1 * the outer single
>> quotes and inner double quotes are essential!
>
> Is there, as I think, a space between -p and the long expression? Or not?
Yes there is a space. Multiple space are ok too, but make sure
there's at least one space before and after the -p , i.e.,
pine -p "{titan
^^^ ^^^
note the spaces in this *fragment* of the line
>> 4] Save and quit pico.
>>
>>
>> 5] To set this alias, logout and then log back in. Then type:
>
> Log out? You mean exit my ssh session?
Yes, exit the ssh session and then reconnect. This will run your
~/.bash_profile and make sure that this alias will work whenever
you log in via ssh.
Beartooth Stafwright
> Anywhere is fine, but since you asked, I suggest the bottom. Oh yes, make
> a backup first by typing this:
>
> cp -i ~/.bash_profile ~/.bash_profile-2006-04-18
Done.
>>> alias pine='/path/to/pine -p
>>> "{titan.lserv.com/novalidate-cert/user=karhunhammas}remote_pinerc"'
>>>
>>> Note:
>>> * this is all on one line
>>> * replace /path/to/pine with the path from Step #1 * the outer single
>>> quotes and inner double quotes are essential!
>>
>> Is there, as I think, a space between -p and the long expression? Or
>> not?
>
> Yes there is a space. Multiple space are ok too, but make sure there's at
> least one space before and after the -p , i.e.,
>
> pine -p "{titan
> ^^^ ^^^
> note the spaces in this *fragment* of the line
>
>
>>> 4] Save and quit pico.
Done.
>>> 5] To set this alias, logout and then log back in. Then type:
>>
>> Log out? You mean exit my ssh session?
>
> Yes, exit the ssh session and then reconnect. This will run your
> ~/.bash_profile and make sure that this alias will work whenever you log
> in via ssh.
Done.
Proceeding now from directions in your immediately previous post.
5] To set this alias, logout and then log back in. Then type:
alias
The pine alias you just created should be listed.
Sure enough, right in the big middle :
[karhunhammas@titan ~]$ alias
alias cp='cp -i'
alias l.='ls -d .* --color=tty'
alias la='ls -la'
alias ll='ls -l --color=tty'
alias ls='ls --color=tty'
alias mv='mv -i'
alias pine='/usr/bin/pine -p "{titan.lserv.com/novalidate-cert/user=karhunhammas}remote_pinerc"'
alias rm='rm -i'
alias vi='vim'
alias which='alias | /usr/bin/which --tty-only --read-alias --show-dot --show-tilde'
[karhunhammas@titan ~]$
6] Now the big test: Type this:
pine
And let us know if it works!
It chewed on it a while, naturally enough; then I got :
[karhunhammas@titan ~]$ pine
+ HOST: titan.lserv.com USER: karhunhammas ENTER PASSWORD:
(NB: Titan is configured to demand my password at ssh, and again at the
command "pine" (and other times). I gave it the password -- after typing
the immediately above, which apparently exceeded the timeout.
[karhunhammas@titan ~]$ pine
+ HOST: titan.lserv.com USER: karhunhammas ENTER PASSWORD:
So I gave it again -- and I'm in! Champagne is indicated, n'est c'est pas?
M > L still looks normal; remote_addrbook and remote_pinerc are still
there. And normal things work: my most-used folders contain what they
should, the tab key works normally ... Definitely champagne.
NM Public
>
> + HOST: titan.lserv.com USER: karhunhammas ENTER PASSWORD:
>
> So I gave it again -- and I'm in! Champagne is indicated, n'est c'est pas?
>
> M > L still looks normal; remote_addrbook and remote_pinerc are still
> there. And normal things work: my most-used folders contain what they
> should, the tab key works normally ... Definitely champagne.
Hooray, definitely champagne!! OK, now it's time to move on to
your other systems, e.g., your desktop systems. What you need to
do is set up an alias on each of your desktop machines that is
the same as the alias that you set up on titan, EXCEPT:
1) the path/to/pine might be different
2) the alias syntax will be different if you are using a shell
other than bash
To determine each of these, type the following on each of your
desktop systems:
1) which pine
2) finger yourUID
One lesson I learned from all this is that it's better not to use
'chsh' to determine the shell -- 'finger' should work and not
allow accidental CHanging of the SHell! (Another option is
'printenv')
If you are using bash, you should be able to do exactly as you
did before. If you are using another shell, such as csh, let us
know.
Another thing to do:
* On each of your desktop machines type:
man pine
and see if '-passfile' is one of the listed arguments. If it is,
we will set up a passfile (password file) on your desktop
systems.
Hope you're enjoying the champagne!
NM Public
>
> * On each of your desktop machines type:
>
> man pine
>
> and see if '-passfile' is one of the listed arguments. If it is, we will set
> up a passfile (password file) on your desktop systems.
Oops, I meant
pine -h
Also, can you post what OS each of your desktop systems use?
Thanks!
Beartooth Stafwright
> Hooray, definitely champagne!! OK, now it's time to move on to your other
> systems, e.g., your desktop systems. What you need to do is set up an
> alias on each of your desktop machines that is the same as the alias that
> you set up on titan, EXCEPT:
>
> 1) the path/to/pine might be different
>
> 2) the alias syntax will be different if you are using a shell
> other than bash
>
> To determine each of these, type the following on each of your desktop
> systems:
>
> 1) which pine
/usr/bin/pine
> 2) finger yourUID
[....]
That turned to be amusing, and oddly appropriate to an old retired fart :
[btth@localhost ~]$ finger btth
Login: btth Name: beartooth
Directory: /home/btth Shell: /bin/bash
On since Thu Apr 13 14:31 (EDT) on :0 (messages off)
On since Thu Apr 13 14:31 (EDT) on pts/0 from :0.0
18 minutes 4 seconds idle
On since Thu Apr 13 14:40 (EDT) on pts/1 from :0.0
1 day 19 hours idle
On since Thu Apr 13 14:40 (EDT) on pts/2 from :0.0
On since Thu Apr 13 14:40 (EDT) on pts/3 from :0.0
21 hours 50 minutes idle
On since Thu Apr 13 14:40 (EDT) on pts/4 from :0.0
21 hours 31 minutes idle
On since Thu Apr 13 14:40 (EDT) on pts/5 from :0.0
2 hours 31 minutes idle
No mail.
No Plan.
[btth@localhost ~]$
So I am in a bash shell; but after being amused, are those "No mail. No
Plan." entries something to take account of in this process?
> Another thing to do:
>
> * On each of your desktop machines type:
>
> man pine
>
> and see if '-passfile' is one of the listed arguments. If it is, we will
> set up a passfile (password file) on your desktop systems.
I substituted pine -h, according to your follow-up, and got (among much
else) :
-passfile <fully_qualified_filename> Set the password file to something other
than the default
-nowrite_passfile Read from a passfile if there is one, but never offer to
write a password to the passfile
(I do have to give a password to pine, as well as on logging in, when I
use Ddave's machine; but not on any of my own.)
All of my desktops are running Fedora Core 5; Jo's (from which I
sometimes get into my own pine accounts) is still FC4, but I'll upgrade it
to FC5 as soon as she finishes the first draft of her book and I get that
safely onto a CD -- any day now; the laptop is running FC4.ppc, and is
lent out (and overdue back); I'll upgrade it to FC5.ppc as soon as I get
my hands on it again. (It's an apple G3 iBook -- with no apple code.)
> Hope you're enjoying the champagne!
That'll come this evening, thanks!
One more question, before we get to the point of testing this once it's
done. What is this hole Ddave would make (if he hasn't already) in his
firewall? I don't want to diminish his security, nor ask for any bigger
hole than I need.
NM Public
>
>> 2) finger yourUID
> [....]
> That turned to be amusing, and oddly appropriate to an old retired fart :
Guess I won't use that wording in the final write-up of all this
:-)!
> No mail.
> No Plan.
> [btth@localhost ~]$
>
> So I am in a bash shell; but after being amused, are those "No mail. No
> Plan." entries something to take account of in this process?
Nope. They are just telling you that there's nothing in your
local mail spool (/var/spool/mail/btth or something like that)
and that you don't have a ~/.plan file.
> I substituted pine -h, according to your follow-up, and got (among much
> else) :
>
> -passfile <fully_qualified_filename> Set the password file to something other
> than the default
> -nowrite_passfile Read from a passfile if there is one, but never offer to
> write a password to the passfile
>
> (I do have to give a password to pine, as well as on logging in, when I
> use Ddave's machine; but not on any of my own.)
You *are* going to start giving pine a password once you start
using '/usr/bin/pine -p "{titan..."' to launch pine. So that
means that it is excellente that you have a version of pine that
supports a passfile!
Now a question to the audience: Does anyone know what the
passfile name is on Fedora Core's pine? Is it '.pine.pwd' or
something else? Or, even better, is there a way to figure this
out with pine, e.g.:
pine -passfile -h
(I just made up that command, but something like that would be
very useful!)
>> Hope you're enjoying the champagne!
>
> That'll come this evening, thanks!
excellent. here's a bit of trivia: here in London when one buys
champagne it is always from champagne, france and very
expensive. what people call "champagne" in the u.s. is called
something else here (maybe "sparkling wine", more research is
needed...)
> One more question, before we get to the point of testing this
> once it's done. What is this hole Ddave would make (if he
> hasn't already) in his firewall? I don't want to diminish his
> security, nor ask for any bigger hole than I need.
He just needs to open up IMAP access. It's up to him how exactly
he does this. Ask him to tell you what ports (usually 143, 443,
993) and what encryption (none, TLS, SSL) are accepted.
now i'm off to do some champagne research at the local Odd Bins!
Beartooth Stafwright
Pine now won't let me change my signature block. I deleted the literal
signature, but the cursor still won't stop where I want it. Minor? I hope?
Beartooth Stafwright
> On Mon, 13 Mar 2006 11:06:51 -0500, Beartooth wrote:
>
> Pine now won't let me change my signature block. I deleted the literal
> signature, but the cursor still won't stop where I want it. Minor? I hope?
You may all congratulate me : I must be getting a feel for these things at
last -- at long, long last.
I quit pine, and re-launched it late. no automatic signature. Did M > S >
C -- and saw "<empty value>" in the literal-sig place. Happened to think
to delete that.
That did it.
Beartooth Stafwright
> Let us know how stage one of your conversion to the all-imap-all-the-time
> way of doing things goes. When you report back, please also include a list
> of all the machines which you use to access your mail and what operating
> system they use, e.g.,:
I reported previously that there will be four desktops here with FC5 on
PCs. I have now also gotten the G3 iBook laptop back, upgraded it to
FC5.ppc, and installed pine 4.64 on it. (I hope I can transfer all my old
configurations to it, by scp from a PC -- or not have to ...)
Dunno if the PPC architecture will make trouble here or not; if it makes
much, I can live without the whole machine. We seldom travel much, except
to a place with no access at all; so about the only uses the laptop will
have are for house guests to use -- who may well prefer webmail anyhow --
or as a fill-in next time the PCs are being upgraded, to FC6 or 7.
NM Public
> On Tue, 11 Apr 2006 11:00:52 +0100, NM Public wrote:
>
>> Let us know how stage one of your conversion to the all-imap-all-the-time
>> way of doing things goes. When you report back, please also include a list
>> of all the machines which you use to access your mail and what operating
>> system they use, e.g.,:
>
> I reported previously that there will be four desktops here with FC5 on
> PCs. I have now also gotten the G3 iBook laptop back, upgraded it to
> FC5.ppc, and installed pine 4.64 on it. (I hope I can transfer all my old
> configurations to it, by scp from a PC -- or not have to ...)
You do not need to have a pine configuration on any of your
machines. All of them can be set up to use the pine configuration
that is on titan, i.e., by setting up an alias that does this:
pine -p {titan.
^^^^^^^^
specification of your remote_pinerc
I am participating in TV Turnoff Week *and Internet Turnoff Week*
starting tomorrow, April 24, so I won't be on the Net until May
1. I hope that other people will help you get this set up.
Hopefully Ddave has given you IMAP access to his system.
Good luck,
I'll be back in cyberspace on May 1!
Beartooth Stafwright
> You do not need to have a pine configuration on any of your machines. All
> of them can be set up to use the pine configuration that is on titan,
> i.e., by setting up an alias that does this:
>
> pine -p {titan.
> ^^^^^^^^
> specification of your remote_pinerc
>
>
> I am participating in TV Turnoff Week *and Internet Turnoff Week* starting
> tomorrow, April 24, so I won't be on the Net until May 1. I hope that
> other people will help you get this set up. Hopefully Ddave has given you
> IMAP access to his system.
Oh, Lord, don't tell my wife and friends! I've never owned a TV, nor
wanted to; but Internet Turnoff Week is what we get whenever we go visit
the in-laws in the Western foothills of the Great Smokies. I must admit
it's restful and soothing ...
We'll miss you. Enjoy!
Beartooth Stafwright
> All of them can be set up to use the pine configuration that is on
> titan, i.e., by setting up an alias that does this:
>
> pine -p {titan.
> ^^^^^^^^
> specification of your remote_pinerc
If an alias does what I think, then I don't see how nor whether
this is something I can live with.
As I mentioned on March 15,
"The only broadband connection available where I live (and the account I
get my newsfeeds from, and thus use for c.m.p) is the POP3 one on cable --
which is also my only access to usenet, the Web, downloads, etc.
I can't get rid of that..."
That passage may not have made it clear that one reason not to get rid of
direct access to the adelphia address is that it's my lifeline -- when
either my remote, IMAP account or my ssh access to it, is down (usually I
can't tell which), then my recourse is to email my remote ISP
*from* the adelphia account.
So I have to continue to be able to get into it without going through the
remote -- rarely, to be sure, but then urgently.
Man pine says "-p config-file Use config-file as the personal
configuration file instead of the default .pinerc." -- which I suppose
means "config-file" would be some form of my remote address a/o my avenue
of access to the remote IMAP (whatever that may be). Is that right?
Then doesn't setting up an alias making my own machines read "pine" as
"pine -p <etc>" result in disabling the present plain command "pine",
which goes direct to adelphia?
Am I, as I hope but can't be sure, straining at a gnat here under the
misapprehension that it's a camel?? Is there a much easier way to disable
an alias for one command than by reconfiguring it (and then having to
re-reconfigure it back)?
Chris Lawrence
> Man pine says "-p config-file Use config-file as the personal
> configuration file instead of the default .pinerc." -- which I suppose
> means "config-file" would be some form of my remote address a/o my avenue
> of access to the remote IMAP (whatever that may be). Is that right?
pine -p config-file just means pine will get/write its settings into
"config-file", which can be a local file or a remote mailbox folder,
depending on the syntax that you use. If you don't specify -p then pine
defaults to using ~/.pinerc (or pinerc for PC-Pine).
> Then doesn't setting up an alias making my own machines read "pine" as
> "pine -p <etc>" result in disabling the present plain command "pine",
> which goes direct to adelphia?
I use the command 'rpine' to start my Pine from my shell account.
That's an alias which runs pine -p followed by the synatx for my remote
config file. If you want you can use something different instead of
'pine', and perhaps have different aliases for different config files.
Then you could define, for example, tpine to run pine with the titan
server config, and lpine to run pine with a local config file, and so
on.
--
Chris
Beartooth Stafwright
> pine -p config-file just means pine will get/write its settings into
> "config-file", which can be a local file or a remote mailbox folder,
> depending on the syntax that you use. If you don't specify -p then pine
> defaults to using ~/.pinerc (or pinerc for PC-Pine).
Hmmm.... So I could save actually typing that out for the case when I
might want to override the new default, right?
>> Then doesn't setting up an alias making my own machines read "pine" as
>> "pine -p <etc>" result in disabling the present plain command "pine",
>> which goes direct to adelphia?
>
> I use the command 'rpine' to start my Pine from my shell account. That's
> an alias which runs pine -p followed by the synatx for my remote config
> file. If you want you can use something different instead of 'pine', and
> perhaps have different aliases for different config files. Then you could
> define, for example, tpine to run pine with the titan server config, and
> lpine to run pine with a local config file, and so on.
Aha! Tunnel vision on my part -- shudda thunka that. I could guess there
must be something. Many many thanks; that should fix me up.
Beartooth
> pine -p {titan.
> ^^^^^^^^
> specification of your remote_pinerc
>
>
> I am participating in TV Turnoff Week *and Internet Turnoff Week*
> starting tomorrow, April 24, so I won't be on the Net until May
> 1. I hope that other people will help you get this set up.
> Hopefully Ddave has given you IMAP access to his system.
>
> Good luck,
> I'll be back in cyberspace on May 1!
> Nancy
I had to wipe the laptop and do a clean install to get my Gnome back; in
process of reconfiguring it, instead of using scp to get my pine
configuration from another machine here, I decided to try doing M >
S > Z, and letting it walk me through.
I thought I had managed it -- till I went back into my regular ssh session
from my current main machine to pine, which was already in session. I
tried to start an email, and discovered my addressbook there is empty!
--
Beartooth Staffwright, PhD, Squirreler
& Not Quite Clueless Fedora Power User
NM Public
>
> I had to wipe the laptop and do a clean install to get my Gnome
> back; in process of reconfiguring it, instead of using scp to
> get my pine configuration from another machine here, I decided
> to try doing M > S > Z, and letting it walk me through.
>
> I thought I had managed it -- till I went back into my regular
> ssh session from my current main machine to pine, which was
> already in session. I tried to start an email, and discovered
> my addressbook there is empty!
Aaarrgghhhh is right! OK, first thing is this:
**********************************
* Do not use MSZ again *
* unless I explicitly ask you to *
**********************************
MSZ moves things from your local system to the remote system. If
you do it again, you may irreparably screw up the setup on your
remote system. At this point, I'm pretty sure it can be repaired
though.
In order to repair it, please follow the instructions that I'll
post in an upcoming message.
Note: After we repair this, we need to clear up some fundamental
misunderstandings that I think you have.
More soon,
Nancy
--
Nancy McGough
Infinite Ink: <http://www.ii.com>
Bookmarks & Blog: <http://deflexion.com>
NM Public
> On Sun, 23 Apr 2006 14:19:17 +0100, NM Public wrote:
>
>> You do not need to have a pine configuration on any of your
>> machines. All of them can be set up to use the pine
>> configuration that is on titan, i.e., by setting up an alias
>> that does this:
>>
>> pine -p {titan.
>> ^^^^^^^^
>> specification of your remote_pinerc
>
> If an alias does what I think, then I don't see how nor whether
> this is something I can live with.
>
> As I mentioned on March 15,
>
> "The only broadband connection available where I live (and the
> account I get my newsfeeds from, and thus use for c.m.p) is the
> POP3 one on cable -- which is also my only access to usenet,
> the Web, downloads, etc.
>
I understand that and I've understood that all along. I am in a
similar situation. I use ~40K AOL dial up all the time, every
day. That's what I'm using now. You need to understand 3 things:
1] Pine is fundamentally an *online* mail client
2] It does not matter what Internet *Access* Provider (IAP) you
are using to get online.
3] Pine will cache the remote pinerc on your local system and
the fact that you use a remote pinerc will not affect your pine
speed (other than at startup). It is not an issue even on slow
dial up.
I am in the process of trying to walk you through setting this
up. I will make sure that you can access your Adelphia email even
when your primary IMAP server (titan) is down. But first, we need
to get your pine aliases set up. After that, we will muck around
with the config settings (and restore your lost address book!).
I like Chris Lawrence's suggestion to create multiple pine
aliases. To start, I suggest that you use these 2:
alias pine='/usr/bin/pine -p "{titan.lserv.com/novalidate-cert/user=karhunhammas}remote_pinerc"'
alias pine-problems='/usr/bin/pine'
IMPORTANT:
1] You should copy the first alias from your titan
~/.bash_profile.
2] In both of these aliases, replace /usr/bin/pine with the
/absolute/path/to/pine on your local system.
3] Other instructions about setting up aliases are in older
messages in this thread.
4] You can name pine-problems whatever you like, but I suggest
that you give it a name that will remind you that you only use
this alias when the other one does not work!
Let us know what happens. There almost surely will be problems,
but I'm confident we can solve them!
Good luck on this mission Beartooth!
Beartooth
> Sur 2006-05-10, Beartooth skribis:
>> I thought I had managed it -- till I went back into my regular
>> ssh session from my current main machine to pine, which was
>> already in session. I tried to start an email, and discovered
>> my addressbook there is empty!
The addressbook has since come back.
>
> Aaarrgghhhh is right! OK, first thing is this:
>
> **********************************
> * Do not use MSZ again *
> * unless I explicitly ask you to *
> **********************************
Agreed, in thunder.
> MSZ moves things from your local system to the remote system. If
> you do it again, you may irreparably screw up the setup on your
> remote system.
Yes, I finally realized, waking up in the wee hours, that I had been
connected to titan when I thought I was only configuring the laptop to
*use* titan. No doubt it was abundantly obvious to the pinemasters, but it
wasn't to me.
> At this point, I'm pretty sure it can be repaired
> though.
Oh good. I have looked (not changed) and there are three or four .pinercs
on titan now: a plain, at least one remote, something called oldpinerc ...
> In order to repair it, please follow the instructions that I'll
> post in an upcoming message.
I'll stay off titan entirely.
> Note: After we repair this, we need to clear up some fundamental
> misunderstandings that I think you have.
Bless you. I've certainly got some.
--
Beartooth Staffwright, PhD, Squirreler
& Not Quite Clueless Fedora Power User
by God's Grace, Linux's, and the Net's
Beartooth
>> MSZ moves things from your local system to the remote system.
And at the time I was doing it, I had added pine into the clean install on
the laptop, and that was all. I had neither configured anything, nor
copied a .pinerc from another machine. (I have now.) When I invoked it, it
merely opened, without even trying to connect to anything.
--
Beartooth Staffwright, PhD, Squirreler
Beartooth
> Sur 2006-04-25, Beartooth Stafwright skribis:
>> On Sun, 23 Apr 2006 14:19:17 +0100, NM Public wrote:
>>
>>> You do not need to have a pine configuration on any of your
>>> machines. All of them can be set up to use the pine
>>> configuration that is on titan, i.e., by setting up an alias
>>> that does this:
>>>
>>> pine -p {titan.
>>> ^^^^^^^^
>>> specification of your remote_pinerc.pinerc
Is there really such a file as <whaterer>_pinerc.pinerc -- one with the
string "pinerc" in it twice running? ls -a | grep pinerc doesn't find one.
Or, of course, I may always be looking in the wrong place ....
Another question will follow below. I *think* the pine configuration I
need may be one of the following :
.pinerc
.pinerc-05-10-06
.pinerc_05_12_06
.pinerc-2006-04-12.Bkup
.pinerc.old
PineReconfig
.pinesettings
The one called PineReconfig is a file the machine generated, and I named
in process of saving it, while rushing foolishly in with the Z option; it
starts out like this :
You may want to save a copy of this information!
Your Pine configuration data has been copied to
{titan.lserv.com/novalidate-cert/user=karhunhammas}remote_pinerc
To use that remote configuration from this computer you will
have to change the way you start Pine by using the command line option
"pine -p <remote_folder>". The command should probably be
pine -p "{titan.lserv.com/novalidate-cert/user=karhunhammas}remote_pinerc"
The quotes are there around the last argument to protect the special
characters in the folder name (like braces) from the command shell
you use.
[....]
I'm not sure what the file .pinesettings is, nor where it comes from -- it
looks like it might come from a .pinerc ; there is something similar (and
a lot of other stuff) in /etc/pine.conf on my local machine. Here are its
contents :
==== Feature settings ==========
no-alternate-compose-menu
compose-cut-from-cursor
compose-maps-delete-key-to-ctrl-d
compose-rejects-unqualified-addrs
no-compose-send-offers-first-filter
no-enable-alternate-editor-cmd
no-enable-alternate-editor-implicitly
enable-search-and-replace
no-enable-sigdashes
quell-dead-letter-on-cancel
no-quell-user-lookup-in-passwd-file
no-enable-reply-indent-string-editing
no-include-attachments-in-reply
no-include-header-in-reply
no-include-text-in-reply
no-reply-always-uses-reply-to
signature-at-bottom
strip-from-sigdashes-on-reply
no-enable-8bit-esmtp-negotiation
no-enable-background-sending
no-enable-delivery-status-notification
no-enable-verbose-smtp-posting
no-fcc-on-bounce
no-fcc-only-without-confirm
no-fcc-without-attachments
no-use-sender-not-x-sender
no-combined-subdirectory-display
combined-folder-display
enable-dot-folders
enable-incoming-folders
no-enable
I hope it tells you something.
> 1] Pine is fundamentally an *online* mail client
Err... Duh... What other kind is there?
> 2] It does not matter what Internet *Access* Provider (IAP) you
> are using to get online.
Oh good. Thanks for saying that.
> 3] Pine will cache the remote pinerc on your local system and
> the fact that you use a remote pinerc will not affect your pine
> speed (other than at startup). It is not an issue even on slow
> dial up.
OK -- I *think* I have this straight : "remote" means remote always from
me, not opposite things on each end (i.e., remote from Lserv, i.e., here,
in the case of titan) -- right? It gets very confusing ....
> I am in the process of trying to walk you through setting this
> up. I will make sure that you can access your Adelphia email even
> when your primary IMAP server (titan) is down. But first, we need
> to get your pine aliases set up.
Following something you say below, I got onto titan, and found this :
[karhunhammas@titan ~]$ cat .bash_profile
# .bash_profile
# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
# User specific environment and startup programs
PATH=$PATH:$HOME/bin
export PATH
unset USERNAME
alias pine='/usr/bin/pine -p "{titan.lserv.com/novalidate-cert/user=karhunhammas}remote_pinerc"'
[karhunhammas@titan ~]$
Meanwhile, one of my own machines (where pine is working as it normally
has), I see :
[btth@localhost ~]$ cat .bash_profile
# .bash_profile
# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
# User specific environment and startup programs
PATH=$PATH:$HOME/bin
export PATH
unset USERNAME
[btth@localhost ~]$
IF I follow you, you're saying I should simply copy the following :
alias pine='/usr/bin/pine -p
"{titan.lserv.com/novalidate-cert/user=karhunhammas}remote_pinerc"'
(which is all one line on titan) after a btth prompt on each of my local
machines, and hit enter. Is that right?
> After that, we will muck around
> with the config settings (and restore your lost address book!).
I promised not to touch M > S > Z again, and I haven't. But I did get into
my shell on titan, and change the .pinerc clones around -- so the list
above reflects the way they are now. Then I got into M > S > C on titan,
and added back in several settings -- notably my incoming folders and my
default headers. Successfully, I might add; occasionally I win one.
IF I recall correctly, I also did some fiddling in my titan shell with
addressbooks; at any rate, what seems to be the right one is back --
Ctrl-T in the To: field works, as does typing in a nickname. ls -a in
that shell shows, among many other things :
.addressbook
.addressbook-2006-04-11
.addressbook.lu
.addressbook.old
address.txt
address.txt.lu
(the last two do not have dots in front.)
> I like Chris Lawrence's suggestion to create multiple pine aliases. To
> start, I suggest that you use these 2:
>
>
> alias pine='/usr/bin/pine -p
> "{titan.lserv.com/novalidate-cert/user=karhunhammas}remote_pinerc"'
>
> alias pine-problems='/usr/bin/pine'
>
>
> IMPORTANT:
> 1] You should copy the first alias from your titan
> ~/.bash_profile.
>
> 2] In both of these aliases, replace /usr/bin/pine with the
> /absolute/path/to/pine on your local system.
I'm beginning to get comfortable with paths, of the simplest variety; I
seem to recall reading somewhere that PATH and HOME have special meanings
of some sort; but an "absolute" path is new to me. On my home machine, I
get :
[btth@localhost ~]$ whereis pine
pine: /usr/bin/pine /etc/pine.conf [and the man page's location]
so I'm guessing that the absolute path actually *is* /usr/bin/pine --
right?
If not, I also have a folder named /home/btth/mail/pine, consisting of
messages (some from pine, some real emails) -- and two others. One is
/home/btth/Mail/, which contains a folder containing folders with names
like pine folders, each containing other, empty folders. There is also
/home/btth/pine, which is a single folder of emails, some from pine and
some real -- it may be the same as /home/btth/mail/pine. I do *not* see
any such folder as /home/btth/.pine, though I had expected to and looked,
on any of my machines.
> 3] Other instructions about setting up aliases are in older
> messages in this thread.
>
> 4] You can name pine-problems whatever you like, but I suggest
> that you give it a name that will remind you that you only use this
> alias when the other one does not work!
>
> Let us know what happens. There almost surely will be problems, but I'm
> confident we can solve them!
>
> Good luck on this mission Beartooth!
> Nancy
--
Beartooth Staffwright, PhD, Squirreler
NM Public
>>>
>>>> You do not need to have a pine configuration on any of your
>>>> machines. All of them can be set up to use the pine
>>>> configuration that is on titan, i.e., by setting up an alias
>>>> that does this:
>>>>
>>>> pine -p {titan.
>>>> ^^^^^^^^
>>>> specification of your remote_pinerc.pinerc
>
> Is there really such a file as <whaterer>_pinerc.pinerc -- one
> with the string "pinerc" in it twice running?
No, that was a typo. Please just copy & paste the alias from your
bash profile on titan to the bash profile on your local system.
If it works on titan, it should work on your local system. If it
does not work on your local machine, post the exact error message
and I will help you debug it. We need to get this alias working
on your local machine before we can proceed.
Instructions for setting up the aliases 'pine' and
'pine-problems' are in older messages.
Good luck,
Nancy
--
Nancy McGough
Infinite Ink: <http://www.ii.com/>
Bookmarks & Blog: <http://deflexion.com/>
Beartooth
> Sur 2006-05-18, Beartooth skribis:
>> Is there really such a file as <whaterer>_pinerc.pinerc -- one
>> with the string "pinerc" in it twice running?
> No, that was a typo. Please just copy & paste the alias from your
> bash profile on titan to the bash profile on your local system.
OK : I have just done this (with two aliases, of which I'm more likely to
remember at least one at need, for direct local access) :
[btth@localhost ~]$ alias pine='/usr/bin/pine -p "{titan.lserv.com/novalidate-cert/user=karhunhammas}remote_pinerc"'
[btth@localhost ~]$ alias delpine='/usr/bin/pine'
[btth@localhost ~]$ alias Adelpine='/usr/bin/pine'
[btth@localhost ~]$
I then quit pine and exited titan; quit local pine; and commanded simply
"pine" at my normal user prompt. I got a pine main screen, all right, but
with the following at the bottom :
Copyright 1989-2005. PINE is a trademark of the University of Washington.
HOST: mail.adelphia.net (INSECURE) USER: Beartooth ENTER PASSWORD:
^G Help
^C Cancel Ret Accept
That of course is what I get locally. It refused my titan password, of
course, and took my adelphia password -- and sure enough put me into my
adelphia mail. In other words, the new alias did nothing, yet at least.
I'll try logging out and back in, and doing it again; if
that doesn't fix it, I reboot and try a third time. The first time I
succeed, or if both tries fail, I'll report, including any error messages.
> If it works on titan, it should work on your local system. If it
> does not work on your local machine, post the exact error message
> and I will help you debug it. We need to get this alias working
> on your local machine before we can proceed.
>
> Instructions for setting up the aliases 'pine' and
> 'pine-problems' are in older messages.
That's where I got the commands I reproduced above, yes; thanks again for
them!
Meanwhile, there's another oddity; I'm not sure whether it's related or a
problem. It's this : sometimes, not always, when I try to forward a
message from titan, I get the following -- and am not sure where to be in
order to be able to make the substitution and include the /novalidate-cert :
There was a failure validating the SSL/TLS certificate for the server
The reason for the failure was
self signed certificate (details)
We have not verified the identity of your server. If you ignore this
certificate validation problem and continue, you could end up connecting to
an imposter server.
If the certificate validation failure was expected and permanent you may
avoid seeing this warning message in the future by adding the option
/novalidate-cert
to the name of the folder you attempted to access. In other words, wherever
you see the characters
titan.lserv.com
[....]
--
Beartooth Staffwright, Neo-Redneck, Double Retiree,
Not Quite Clueless Linux Power User : Fedora Core 5 [etc]
I have precious (very precious) little idea where up is.
NM Public
>
>>> Is there really such a file as <whaterer>_pinerc.pinerc -- one
>>> with the string "pinerc" in it twice running?
>
>> No, that was a typo. Please just copy & paste the alias from your
>> bash profile on titan to the bash profile on your local system.
>
> OK : I have just done this (with two aliases, of which I'm more likely to
> remember at least one at need, for direct local access) :
>
> [btth@localhost ~]$ alias pine='/usr/bin/pine -p "{titan.lserv.com/novalidate-cert/user=karhunhammas}remote_pinerc"'
> [btth@localhost ~]$ alias delpine='/usr/bin/pine'
> [btth@localhost ~]$ alias Adelpine='/usr/bin/pine'
> [btth@localhost ~]$
>
> I then quit pine and exited titan; quit local pine; and commanded simply
> "pine" at my normal user prompt. I got a pine main screen, all right, but
> with the following at the bottom :
>
> Copyright 1989-2005. PINE is a trademark of the University of Washington.
> HOST: mail.adelphia.net (INSECURE) USER: Beartooth ENTER PASSWORD:
OK, good, we're making progress. Now do this: On your local
machine, type this:
alias
and post here what you get. I'll then tell you what you need to
do to fix the 'pine' alias.
Beartooth
> On Fri, 19 May 2006 14:34:44 +0100, NM Public wrote:
[...]
>> Please just copy & paste the alias from your
>> bash profile on titan to the bash profile on your local system.
>
> OK : I have just done this (with two aliases, of which I'm more likely to
> remember at least one at need, for direct local access) :
>
> [btth@localhost ~]$ alias pine='/usr/bin/pine -p "{titan.lserv.com/novalidate-cert/user=karhunhammas}remote_pinerc"'
> [btth@localhost ~]$ alias delpine='/usr/bin/pine'
> [btth@localhost ~]$ alias Adelpine='/usr/bin/pine'
> [btth@localhost ~]$
>
> I then quit pine and exited titan; quit local pine; and commanded simply
> "pine" at my normal user prompt... In other words, the new alias did
> nothing, yet at least.
> I'll try logging out and back in, and doing it again; if that doesn't
> fix it, I reboot and try a third time. The first time I succeed, or if
> both tries fail, I'll report, including any error messages.
The new alias for pine still does nothing; the other two get the following
errors :
[btth@localhost ~]$ pine
Pine finished -- Closed folder "INBOX". Kept all 329 messages.[wrong acct]
[btth@localhost ~]$ delpine
bash: delpine: command not found
[btth@localhost ~]$ Adelpine
bash: Adelpine: command not found
[btth@localhost ~]$
That happened after logging out and back in, and again after a reboot;
obviously I've made the alias wrong somehow.
>> If it works on titan, it should work on your local system. If it does
>> not work on your local machine, post the exact error message and I will
>> help you debug it. We need to get this alias working on your local
>> machine before we can proceed.
Fwiw, I tried getting into titan by my usual ssh route, and everything to
do with pine there seems normal -- except that when I tried cat .pinerc |
grep titan.lserv.com | less I got a large number of entries containing \/
where I'd've expected / -- and some of those were
titan.lserv.com\/novalidate-cert
While I was doing that, I see, you had posted :
> OK, good, we're making progress. Now do this: On your local
> machine, type this:
> alias
> and post here what you get. I'll then tell you what you need to
> do to fix the 'pine' alias.
So I did, and got :
[btth@localhost ~]$ alias
alias l.='ls -d .* --color=tty'
alias ll='ls -l --color=tty'
alias ls='ls --color=tty'
alias vi='vim'
alias which='alias | /usr/bin/which --tty-only --read-alias --show-dot --show-tilde'
[btth@localhost ~]$
IOW, none of my new aliases are there at all!
NM Public
> IOW, none of my new aliases are there at all!
Just as I suspected. You need to follow the instructions that I
posted a while ago about editing your ~/.bash_profile. The
aliases need to be defined in your ~/.bash_profile. Please do
that and then log off & log back in. Then type this:
alias
and post what you get here. This needs to be done your local
machine. The instructions that you successfully followed before
were on the remote machine (titan), but those instructions should
also work on your local machine.
Beartooth
> Sur 2006-05-19, Beartooth skribis:
>> IOW, none of my new aliases are there at all!
>
> Just as I suspected. You need to follow the instructions that I
> posted a while ago about editing your ~/.bash_profile. The
> aliases need to be defined in your ~/.bash_profile. Please do
> that and then log off & log back in.
Either I'm unusually stupefacted, or something is very strange. to
accompliah the above, I did "nano -w .bash_profile" and added the three
lines at the bottom :
GNU nano 1.3.8 File: .bash_profile
# .bash_profile
# Get the aliases and functions
if [ -f ~/.bashrc ]; then
. ~/.bashrc
fi
# User specific environment and startup programs
PATH=$PATH:$HOME/bin
export PATH
unset USERNAME
alias Adelpine='/usr/bin/pine'
alias delpine='/usr/bin/pine'
alias pine='/usr/bin/pine -p "{titan.lserv.com/novalidate-cert/user=karhunhammas}r$
> Then type this:
>
> alias
>
> and post what you get here. This needs to be done your local
> machine. The instructions that you successfully followed before
> were on the remote machine (titan), but those instructions should
> also work on your local machine.
[btth@localhost ~]$ alias
alias l.='ls -d .* --color=tty'
alias ll='ls -l --color=tty'
alias ls='ls --color=tty'
alias vi='vim'
alias which='alias | /usr/bin/which --tty-only --read-alias --show-dot --show-tilde'
[btth@localhost ~]$
I tried it over again, using pico instead of nano. No change.
NM Public
>
> Either I'm unusually stupefacted, or something is very strange. to
Beartooth, I need to get off the Net now and can't help you debug
this at the moment. Here are a couple suggestions:
1] determine what shell you are using on your local machine,
e.g., maybe it is not bash
2] consult with linux support groups about how to get these
aliases set up in your shell or how to change your shell to bash
Good luck!
More tomorrow,
Nancy
Beartooth
> Either I'm unusually stupefacted, or something is very strange. to
> accompliah the above, I did "nano -w .bash_profile" and added the three
> lines at the bottom :
> [...]
> unset USERNAME
> alias Adelpine='/usr/bin/pine'
> alias delpine='/usr/bin/pine'
> alias pine='/usr/bin/pine -p "{titan.lserv.com/novalidate-cert/user=karhunhammas}r$
That should of course end not with <r$>, but with <...s}remote_pinerc"'>
-- and does, on my machine.
Beartooth
> Beartooth, I need to get off the Net now and can't help you debug
> this at the moment. Here are a couple suggestions:
>
> 1] determine what shell you are using on your local machine,
> e.g., maybe it is not bash
Well, if I enter a typo, such as "rxit" for "exit" I get "bash: rxit:
command not found"
> 2] consult with linux support groups about how to get these
> aliases set up in your shell or how to change your shell to bash
I did that, copying the aliases I was trying to set up, and got this
advice :
> with such simple aliases as these ..., I'd normally put them
> in my ~/.bashrc file instead, that way they work in sub-shells also, as
> ~/.bash_profile only get read/processed by a Login Shell when it first
> opens.
So I now have (on one machine, so far) :
[btth@localhost ~]$ cat .bashrc
# .bashrc
# Source global definitions
if [ -f /etc/bashrc ]; then
. /etc/bashrc
fi
# User specific aliases and functions
alias Adelpine='/usr/bin/pine'
alias delpine='/usr/bin/pine'
alias pine='/usr/bin/pine -p
"{titan.lserv.com/novalidate-cert/user=karhunhammas}remote_pinerc"'
[btth@localhost ~]$
(everything from alias pine to _pinerc"' is on one line)
With this setup, the commands delpine and Adelpine work as intended. The
new plain pine does go straight to titan at lserv; but there are some
problems.
I can't seem to get the novalidate cert effect to work on my
titan inbox, and instead get the long error message when I try to forward
things; and about half my pine folders aren't available -- though
everything at titan still works normally when I ssh into it and then
command pine.
(I haven't tried to get titan to access my adelphia mailbox, because I
have no idea how to do that.)
--
Beartooth Staffwright, Neo-Redneck Double Retiree,
Not Quite Clueless Fedora Core 5 Power User
NM Public
> titan inbox, and instead get the long error message when I try
> to forward things; and about half my pine folders aren't
> available -- though everything at titan still works normally
> when I ssh into it and then command pine.
I'm glad to hear this alias at least works to start pine. Now we
know that Ddave has opened titan up to external IMAP requests.
Next steps:
1] Run the (above) pine alias on your *local* machine.
2] Type MSC to go to the pine config screen.
3] Copy the inbox-path line from that MSC screen and paste it
into a message and post it here.
As we go through the (slow) process of cleaning up this pine
configuration file (your pinerc), it is essential that you be
careful about which pine you are running. For the above 3 steps,
I want you to be using your *local* pine. In future instructions,
I may ask you to run the *remote titan based* pine. Here is a
picture of what is going on:
+-------------+
| your pinerc |
+-------------+
/ \
/ \
local titan
pine pine
In other words, both your local pine and your titan pine are
using the same pinerc. I think the problems that you are
currently experieincing are due to the fact that your local
system and the titan system have different SSL/TLS certificates.
In order for me to know for sure, I need to see parts of your
pinerc. That's why I'm asking you to copy and paste the
inbox-path line.
I hope this makes sense. There are many steps to the process, but
we will get it working!
Nancy
NM Public
send an email message, what happens? If you have problems
sending, we may need to make a pine exception file (pinercex) to
specify the local outgoing SMTP server. Almost everything else
can be shared in your shared pinerc file.
Let us know what happens when you try to email an outgoing
message to a remote system (e.g., you could email a test message
to my email address in the From: header of this message).
Thank you!
Nancy
Beartooth
> Sur 2006-05-21, Beartooth skribis:
>> alias pine='/usr/bin/pine -p "{titan.lserv.com/novalidate-cert/user=karhunhammas}remote_pinerc"'
>>
>> I can't seem to get the novalidate cert effect to work on my
>> titan inbox, and instead get the long error message when I try
>> to forward things; and about half my pine folders aren't
>> available -- though everything at titan still works normally
>> when I ssh into it and then command pine.
>
>
> I'm glad to hear this alias at least works to start pine. Now we
> know that Ddave has opened titan up to external IMAP requests.
> Next steps:
>
> 1] Run the (above) pine alias on your *local* machine.
If I run "pine" on the machine where .bashrc contains that alias, I get
into titan, not adelphia. So I'll report on both places.
> 2] Type MSC to go to the pine config screen.
>
> 3] Copy the inbox-path line from that MSC screen and paste it
> into a message and post it here.
From MSC on in my local pine, getting in by "delpine" it reads :
inbox-path = {mail.adelphia.net/pop3/user=Beartoot...
including the three dots; but when I tell it C (change value), it says :
Name of Inbox server : mail.adelphia.net/pop3/user=Beartooth
without the three dots -- the line ends at ooth.
Before I get to reporting titan, I did two things to confirm the above.
From my userid on the local machine, I get first :
[btth@localhost ~]$ pwd
/home/btth
[btth@localhost ~]$ ls -a | grep pine
Old.pinerc
pine-4.64-1.i386.rpm
pine-4.64-2.lvn5.i386.rpm
.pinerc
[btth@localhost ~]$
and then cat .pinerc | less gives :
[....]
# Over-rides your full name from Unix password file. Required for PC-Pine.
personal-name=Beartooth
# Sets domain part of From: and local addresses in outgoing mail.
user-domain=adelphia.net
# List of SMTP servers for sending mail. If blank: Unix Pine uses sendmail.
smtp-server=mail.adelphia.net
[....]
Now for titan; and again, I'll double-check, using the machine on which
the command "alias" now lists the one for pine on titan, albeit the actual
alias is in .bashrc rather than .bash_profile, and going in first via the
alias, then via ssh.
As soon as I log in, I get a message at the bottom of Pine's main screen,
saying "[Folder "INBOX" opened with 0 messages]" even though I know my
inbox on titan contains about 1300 messages. (NB: This may now change
suddenly -- and still be wrong, reflecting adelphia instead of titan; it
did a little while ago.)
Doing SC from that screen, I get a configuration screen saying inter alia :
inbox-path = <No Value Set: using "inbox">
A little while ago, shortly after that, I had an inbox screen showing no
message senders or titles, but giving the number 354 -- which was very
recently accurate for adelphia! It doesn't seem to want to do that now.
Otoh, if I hit L, I get the listing of what should be my incoming folders,
but trying to open any of them gets a message denying they exist. Opening
sent-mail succeeds, sort of : it gets a short list of messages I've osted
to usenet from adelphia, but none of the messages I've actually sent from
titan by using ssh on another local machine.
Such other folders as the alias sees and can open give similar results.
Checking :
[btth@localhost ~]$ ssh karhun...@68.164.247.62
karhun...@68.164.247.62's password:
Last login: Mon May 22 05:34:24 2006 from blacksburg-bsr1-69-174-64-171.chvlva.adelphia.net
Welcome to Titan.LServ.Com!
[karhunhammas@titan ~]$ ls -a | grep pine
.pinerc
.pinerc-05-10-06
.pinerc_05_12_06
.pinerc-2006-04-12.Bkup
.pinerc.old
.pinesettings
[karhunhammas@titan ~]$
Then I command pine at the titan prompt, and do SC
inbox-path = <No Value Set: using "inbox"> (as above)
exiting that configuration, and hitting L, I can get into my incoming
folders, find new messages, and forward or reply. Doing L again, I can see
a much vaster list of folders, including two (yes, inside titan pine)
named .addressbook and .addressbook-2006-04-11 -- both of which actually
contain messages about Remote Data, rather than real addressbooks.
Quitting pine, but staying on titan, I also get
Pine finished -- Closed folder "INBOX". Kept all 1,259 messages.
[karhunhammas@titan ~]$ ls -a | grep address
.addressbook
.addressbook-2006-04-11
.addressbook.lu
.addressbook.old
address.txt
address.txt.lu
[karhunhammas@titan ~]$
> As we go through the (slow) process of cleaning up this pine
> configuration file (your pinerc), it is essential that you be careful
> about which pine you are running. For the above 3 steps, I want you to
> be using your *local* pine. In future instructions, I may ask you to run
> the *remote titan based* pine.
I did both on one single tab of my gnome-terminal. Henceforth, I will go
back to my standing practice of doing titan pine on one tab of my
gnome-terminal, and local-pine-accessing-adelphia on another, with a green
background for titan and a yellow one for adelphia. That should help.
> Here is a picture of what is going on:
>
>
> +-------------+
> | your pinerc |
> +-------------+
> / \
> / \
> local titan
> pine pine
>
>
> In other words, both your local pine and your titan pine are using the
> same pinerc.
Can we check that? It may be a real mare's nest, not nearly so neat. I've
eschewed any more Z-option futzing, but I have had to go on keeping up
with my email on both accounts, and have made adjustments, with MSC and
MSA, to enable that.
Remember there are at least three or four .pinerc files on titan, some of
which I swapped around, trying to get to things like my addressbook; and
there are also three or four different addressbooks, including an empty
one.
I also recall looking at, if not playing with, /etc/pine.conf on some
machine, which must have been one of mine. (I just ssh'd into titan, from
another machine. cd there put me in /home/karhunhammas -- and "pico
/etc/pine.conf" done there would not let me save any changes, on grounds
of no permission. Since I have no root access on titan, I can't very well
have changed anything there.)
There's another reason to want to check identity of .pinerc files. After
looking in MSC on titan via the alias, I suddenly got a notice that the
inbox had been closed.
> I think the problems that you are currently experieincing
> are due to the fact that your local system and the titan system have
> different SSL/TLS certificates. In order for me to know for sure, I need
> to see parts of your pinerc. That's why I'm asking you to copy and paste
> the inbox-path line.
>
> I hope this makes sense. There are many steps to the process, but we
> will get it working!
I hope I haven't messed things up too badly, just trying to keep them
working.
I presume that a new post in a new thread on this group is actually
addressed to me and to this project. I'll go answer it there.
--
Beartooth Staffwright, Wordcrafty Squirreler
FC5; Pine 4.64, Pan 0.14.2.91; Privoxy 3.0.3; CXO 5.0.1
Dillo 0.8.5, Opera 8.54, Firefox 1.5, Galeon 2.0.1
Remember I have little idea what I am talking about.
Beartooth
> On your *local* system, when you run the pine alias and try to
> send an email message, what happens? If you have problems
> sending, we may need to make a pine exception file (pinercex) to
> specify the local outgoing SMTP server. Almost everything else
> can be shared in your shared pinerc file.
Runnning Pine 4.64 on my local machine (yellow tab), using the alias
Adelpine to connect to Adelphia.net, I get the usual inbox there, from
which I tried sending, forwarding, and replying to my titan account. I
also tried sending a message to your agorae address, with carbons to both
of mine.
> Let us know what happens when you try to email an outgoing
> message to a remote system (e.g., you could email a test message
> to my email address in the From: header of this message).
All of them reported "[Message sent and copied to "sent-mail".]"
I then added a pink tab to my gnome-terminal, ssh'd to titan, commanded
pine, and could see all the test messages, including two which had been
correctly filtered into an incoming folder other than my inbox.
Then I went back to the green tab, used the alias to pine -p into titan,
and got a message saying "Trouble reading remote configuration! Continue
anyway ? [n]:"
I told it y, and got a screen like the first one with a newly installed
pine, but with a message at the bottom, saying "[Can't modify
configuration file "{titan.lserv.com/novalidate-cert/user=]
I hit E for Exit, and got a pine Main screen, with the message "[Can't
modify ..." still there. I hit enter (with L for List highlighted, as it
came up) and got a single array of folders starting with INBOX, and with
the message "[Selectable items in text -- Use Up/Down Arrows to choose,
Return to vie]" (sic!) across the bottom.
INBOX was highlighted. Hitting enter got an almost empty screen, with
PINE 4.64 MESSAGE INDEX Folder: INBOX No Messages
across the top, and pine's usual prompts on the bottom.
Hitting L for List went back one screen. Hitting M for Main worked;
hitting A from there got a normal-looking addressbook. Hitting SC got a
normal-looking configuration screen, including the line
inbox-path = <No Value Set: using "inbox">
but with a line across the bottom saying
[Config file not changeable, can't change options or settings]
So I hit E, then Q, and got back to my own green tab, with
Pine finished -- Closed empty folder "INBOX"
[btth@localhost ~]$
So I went back to my pink ssh tab, which still had
[karhunhammas@titan ~]$ pine
+ HOST: titan.lserv.com USER: karhunhammas ENTER PASSWORD:
Pine finished -- Closed "INBOX". Kept 1,259 messages and removed 3.
[karhunhammas@titan ~]$
from my getting into it before. I told it pine again, and everything
looked normal.
NB: For the past couple years, i.e. since long before this project, titan
has required my password to get on at all, and again to enter pine.
My wife's titan account requires only the password to get on to titan.
After that, she sees only
[tsalagi@titan ~]$ ls -a | grep address
.addressbook
.addressbook.lu
.addressbook.old
[tsalagi@titan ~]$ ls -a | grep pine
.pinerc
.pinerc.old
[tsalagi@titan ~]$
(Her account has had none of the tinkering mine has; she uses no other
email, and has had no reason to participate in this project.)
r royar
> (I haven't tried to get titan to access my adelphia mailbox, because I
> have no idea how to do that.)
Adelphia {mail.adelphia.net/pop3/user=beartooth}INBOX
in your .pinerc should create a mailbox named Adelphia for user
beartooth. An alias such as
alias pineadel='/usr/bin/pine -p "{mail.adelphia.net/pop3/user=beartooth}INBOX"'
(all on one line) ought to work from the command line.
--
rdr
Beartooth
> On Mon, 22 May 2006 17:16:00 +0100, NM Public wrote:
>
>> On your *local* system, when you run the pine alias and try to
>> send an email message, what happens? If you have problems
>> sending, we may need to make a pine exception file (pinercex) to
>> specify the local outgoing SMTP server. Almost everything else
>> can be shared in your shared pinerc file.
[...]
>> Let us know what happens when you try to email an outgoing
>> message to a remote system (e.g., you could email a test message
>> to my email address in the From: header of this message).
>
> All of them reported "[Message sent and copied to "sent-mail".]"
[...]
> Then I went back to the green tab, used the alias to pine -p into titan,
> and got a message saying "Trouble reading remote configuration! Continue
> anyway ? [n]:"
>[...]
> ...and got a single array of folders starting with INBOX, and with
> the message "[Selectable items in text -- Use Up/Down Arrows to choose,
> Return to vie]" (sic!) across the bottom. [....]
Amplification : by "single array," I mean that thin time it didn't even
show my additional incoming folders, much less let me into them.
Beartooth
> Sun, 21 May 2006 (13:48 -0400 UTC) Beartooth wrote:
>
>> (I haven't tried to get titan to access my adelphia mailbox, because I
>> have no idea how to do that.)
>
> Adelphia {mail.adelphia.net/pop3/user=beartooth}INBOX
> in your .pinerc should create a mailbox named Adelphia for user
> beartooth.
Hmmm. I tried, from M > L on titan, creating a new incoming folder named
AdelPine, with the entries taken from that : mail.adelphia.net as the
server and {mail.adelphia.net/pop3/user=beartooth}INBOX as the folder to
access; but I got :
[Connection failed to mail.adelphia.net,143: Connection timed out]
I'm reluctant to fiddle with anything outside a running pine itself at
present, since I'm in the middle of an exchange today with Nancy McGough
about my already tangled .pinerc situation.
> An alias such as
> alias pineadel='/usr/bin/pine -p "{mail.adelphia.net/pop3/user=beartooth}INBOX"'
> (all on one line) ought to work from the command line.
That does now, yes; see other threads back nd forth between me and
NMPublic.
r royar
> On Mon, 22 May 2006 15:22:43 -0400, r royar wrote:
>
>> Sun, 21 May 2006 (13:48 -0400 UTC) Beartooth wrote:
>>
>>> (I haven't tried to get titan to access my adelphia mailbox, because I
>>> have no idea how to do that.)
>>
>> Adelphia {mail.adelphia.net/pop3/user=beartooth}INBOX
>> in your .pinerc should create a mailbox named Adelphia for user
>> beartooth.
>
> Hmmm. I tried, from M > L on titan, creating a new incoming folder named
> AdelPine, with the entries taken from that : mail.adelphia.net as the
> server and {mail.adelphia.net/pop3/user=beartooth}INBOX as the folder to
> access; but I got :
>
> [Connection failed to mail.adelphia.net,143: Connection timed out]
It should not return this error because you asked that Pine open a POP
connection (port 110, not 143 which is IMAP).
> I'm reluctant to fiddle with anything outside a running pine itself at
> present, since I'm in the middle of an exchange today with Nancy McGough
> about my already tangled .pinerc situation.
>
>> An alias such as
>> alias pineadel='/usr/bin/pine -p "{mail.adelphia.net/pop3/user=beartooth}INBOX"'
>> (all on one line) ought to work from the command line.
>
> That does now, yes; see other threads back nd forth between me and
> NMPublic.
>
>
--
Robert Delius Royar The email address is valid as it is written.
NM Public
instructions, I want you to ssh to titan and in an ssh window *on
titan* do the following.
1] Type 'which pine' and paste the output into a reply to this
message.
2] To start pine, type 'pine'
3] Type 'MSC' and set this feature
[X] enable-incoming-folders
4] Quit and restart pine. You need to quit & restart to ensure
that Pine knows about the enable-incoming-folders setting.
5] To go to the FOLDER LIST, type 'ML'
6] Move the focus to 'INBOX' which should be listed first in the
Incoming-Folders collection.
7] While the focus is on 'INBOX', type 'A'
8] You will get this prompt:
Name of server to contain added folder :
At this prompt, paste this:
mail.adelphia.net/pop3/user=Beartooth
9] You will get this prompt:
Folder on "mail.adelphia.net/pop3..." to add :
At this prompt, type this:
INBOX
10] You will get this prompt:
Nickname for folder "INBOX" :
At this prompt, type this:
Adelphia-INBOX
11] Now you should see 'Adelphia-INBOX' in your Incoming-Folders
list. Move the focus to 'Adelphia-INBOX' and press ENTER. You
will be prompted for your Adelphia password and then, if we are
lucky, your Adelphia INBOX will open.
Please post what happens.
IMPORTANT: All 11 of these steps need to be done on pine *running
on titan*.
Good luck,
Nancy
Mark Crispin
>> Hmmm. I tried, from M > L on titan, creating a new incoming folder named
>> AdelPine, with the entries taken from that : mail.adelphia.net as the
>> server and {mail.adelphia.net/pop3/user=beartooth}INBOX as the folder to
>> access; but I got :
>> [Connection failed to mail.adelphia.net,143: Connection timed out]
> It should not return this error because you asked that Pine open a POP
> connection (port 110, not 143 which is IMAP).
Actually, it would, since if you read what he says carefully he set up an
IMAP connection to mail.adelphia.net that opens (if the server on
mail.adelphia.net is UW imapd) a proxy POP3 connection to the server.
Put another way, he set the AdelPine incoming folder as:
{mail.adelpha.net}{mail.adelphia.net/pop3/user=beartooth}INBOX
What he should have done, using his wording, is:
From M > L on titan, create a new incoming folder named AdelPine, with the
entries taken from that : mail.adelphia.net/pop3/user=beartooth as the
server and INBOX as the folder to access.
-- Mark --
http://panda.com/mrc
Democracy is two wolves and a sheep deciding what to eat for lunch.
Liberty is a well-armed sheep contesting the vote.
Beartooth
>>> [...] I got :
>>> [Connection failed to mail.adelphia.net,143: Connection timed out]
>> It should not return this error because you asked that Pine open a POP
>> connection (port 110, not 143 which is IMAP).
>
> Actually, it would, since if you read what he says carefully he set up
> an IMAP connection to mail.adelphia.net that opens (if the server on
> mail.adelphia.net is UW imapd) a proxy POP3 connection to the server.
>
> Put another way, he set the AdelPine incoming folder as:
> {mail.adelpha.net}{mail.adelphia.net/pop3/user=beartooth}INBOX
>
> What he should have done, using his wording, is:
>
> From M > L on titan, create a new incoming folder named AdelPine, with
> the entries taken from that : mail.adelphia.net/pop3/user=beartooth as
> the server and INBOX as the folder to access.
You'll laugh. I did that (while in pine on titan via ssh), and it worked
-- and when I got through doing things with it, I automatically hit Q,
forgetting it was now a folder on titan <gulp>. So of course it logged me
out of pine on titan, and I had to log back in; time to start retraining
fingers ....
Other than that obvious user error, now fixed at least in principle,
everything still seems fine; I just hit tab instead of Q, and it takes me
back into my "real" inbox -- the one I do as much as I can of my mail on.
Much handier than logging back and forth, or keeping two gnome-terminal
tabs open -- as Nancy originally promised. Many thanks!
Now I can go to her next, and back into getting a single common .pinerc
and .addressbook set up so that both accounts use it -- and I can do the
same things via bash alias instead of ssh. Again, many thanks!
Beartooth
> OK, we need to do some clean up of your remote pinerc. For these
> instructions, I want you to ssh to titan and in an ssh window *on
> titan* do the following.
>
>
> 1] Type 'which pine' and paste the output into a reply to this
> message.
Welcome to Titan.LServ.Com!
[karhunhammas@titan ~]$ which pine
alias pine='/usr/bin/pine -p "{titan.lserv.com/novalidate-cert/user=karhunhammas}remote_pinerc"'
/usr/bin/pine
[karhunhammas@titan ~]$
> 2] To start pine, type 'pine'
Done.
> 3] Type 'MSC' and set this feature
>
> [X] enable-incoming-folders
It was already set. I've been using incoming folders on that account
(under ssh) for months, probably years (but not on the adelphia account).
But just in case, I unset it, looged out and back in, reset it, and logged
out and in a third time.
Parenthetical note: when I command pine, from inside titan on ssh, it asks
for my password over again; when I use the new alias, it only asks once.
Dunno if that tells you anything ...
> 4] Quit and restart pine. You need to quit & restart to ensure
> that Pine knows about the enable-incoming-folders setting.
>
> 5] To go to the FOLDER LIST, type 'ML'
Done. The incoming folders are all still there -- and so is the new one,
called AdelPine, which I just learned this afternoon from Mark Crispin in
another thread on this forum how to do.
> 6] Move the focus to 'INBOX' which should be listed first in the
> Incoming-Folders collection.
Yes, it is.
> 7] While the focus is on 'INBOX', type 'A'
>
> 8] You will get this prompt:
>
> Name of server to contain added folder :
>
> At this prompt, paste this:
>
> mail.adelphia.net/pop3/user=Beartooth
>
> 9] You will get this prompt:
>
> Folder on "mail.adelphia.net/pop3..." to add :
>
> At this prompt, type this:
>
> INBOX
>
> 10] You will get this prompt:
>
> Nickname for folder "INBOX" :
>
> At this prompt, type this:
>
> Adelphia-INBOX
Great minds ... That's exactly how MarkC said to do it. I also did it
while in pine on titan under ssh, as I still am.
> 11] Now you should see 'Adelphia-INBOX' in your Incoming-Folders list.
> Move the focus to 'Adelphia-INBOX' and press ENTER. You will be prompted
> for your Adelphia password and then, if we are lucky, your Adelphia
> INBOX will open.
Right -- it did. (I had gotten into it a few minutes ago by tabbing from
another incoming folder. So both ways work. So calling it 'AdelPine'
instead of 'Adelphia-INBOX' must be OK ...)
> Please post what happens.
>
> IMPORTANT: All 11 of these steps need to be done on pine *running on
> titan*.
They were, and they all worked.
What's more, this time I tried send, reply, and forward -- all from within
pine on titan under ssh -- both ways between titan and adelphia, using
AdelPine instead of a separate direct login to adelphia on a different
gnome-terminal tab. They also worked.
Do I imagine aright that the next thing will be to try them using the new
aliassed pine command to get to titan? Or is there still something else
left to do to get the alias connection to show me my incoming folders?
Beartooth
[...]
>> 5] To go to the FOLDER LIST, type 'ML'
>
> Done. The incoming folders are all still there -- and so is the new one,
> called AdelPine, which I just learned this afternoon from Mark Crispin in
> another thread on this forum how to do.
>> 11] Now you should see 'Adelphia-INBOX' in your Incoming-Folders list.
>> Move the focus to 'Adelphia-INBOX' and press ENTER. You will be prompted
>> for your Adelphia password and then, if we are lucky, your Adelphia
>> INBOX will open.
>
> Right -- it did. (I had gotten into it a few minutes ago by tabbing from
> another incoming folder. So both ways work. So calling it 'AdelPine'
> instead of 'Adelphia-INBOX' must be OK ...)
>
>> Please post what happens.
>>
>> IMPORTANT: All 11 of these steps need to be done on pine *running on
>> titan*.
>
> They were, and they all worked.
> Do I imagine aright that the next thing will be to try them using the new
> aliassed pine command to get to titan? Or is there still something else
> left to do to get the alias connection to show me my incoming folders?
Having done the things that needed to be done, I logged out of pine and
off titan, then tried again with the alias on my local machine. I found a
curious thing. It thinks that my inbox is empty, and that my other
previously extant incoming folders don't exist (even though it shows
them!) -- but it does work correctly (well, the same way as under ssh)
with the new incoming folder AdelPine.
When I do M > L, I get this :
-------------------------------------------------------------------------
Folder-Collection <Incoming-Folders>
-------------------------------------------------------------------------
INBOX bblx ACFG VA ARTEMIS VCDL AdelPine
-------------------------------------------------------------------------
Folder-Collection <Mail>
-------------------------------------------------------------------------
[and then what may be either a small fraction of my pine folders on titan,
or the list of my pine folders on adelphia -- which, when I open them,
contain about what they should on adelphia, *not* what they really should
on titan]
Beartooth
> On Tue, 23 May 2006 08:41:51 -0700, Mark Crispin wrote:
>> Actually, it would, since if you read what he says carefully he set up
>> an IMAP connection to mail.adelphia.net that opens (if the server on
>> mail.adelphia.net is UW imapd) a proxy POP3 connection to the server.
I forgot to point out that in fact, mail.adelphia.net is POP3 only -- one
of the biggest reasons I prefer Lserv so much ...
--
Beartooth Staffwright, PhD, Neo-Redneck, Double Retiree,
Not Quite Clueless Linux Power User : Fedora Core 5 [etc]
NM Public
>
> When I do M > L, I get this :
>
> -----------------------------------------------------------------
> -----------------------------------------------------------------
> INBOX bblx ACFG VA ARTEMIS VCDL AdelPine
>
> -----------------------------------------------------------------
> -----------------------------------------------------------------
Hello Beartooth,
We still have a ways to go in getting this all set up. Before we
progress, I want you to use a different name for this
incoming-folder:
AdelPine
From things that you have written, it seems to me that you have
some fundamental misunderstandings. My plan is that ultimately
all these misunderstandings will be cleared up. The first thing
that you need to understand is that the the 'AdelPine'
incoming-folder is completely independent of Pine and it does not
make sense to have the string 'Pine' as part of its name. I like
to use a name that contains the string 'inbox' for my POP3
inboxes, so I would use something like this:
Adel-inbox
You can, of course, use anything you want. Please let me know
what you decide to use so I can refer to it with the nickname
that you use.
Thank you!
NM Public
> independent of Pine and it does not make sense to have the string 'Pine' as
> part of its name. I like to use a name that contains the string 'inbox' for
> my POP3 inboxes, so I would use something like this:
>
> Adel-inbox
>
> You can, of course, use anything you want. Please let me know what you decide
> to use so I can refer to it with the nickname that you use.
Oops, I forgot to post the rename instructions... To rename this
incoming-folder, use ML to go to the pine FOLDER LIST, select the
AdelPine mailbox, type R (for Rename), and specify the new name.
You should be able to rename this from either 'pine' running on
titan or 'pine' running on your local system (that's one of the
beauties of the system we're setting up for you!)
Also, here is a question about this mailbox:
* Do you use any other email client to access this Adelphia
INBOX? E.g., mutt, Thunderbird, and Adelphia webmail client or
anything else?
Let us know what nickname you decide to use,
Beartooth
> We still have a ways to go in getting this all set up. Before we
> progress, I want you to use a different name for this
> incoming-folder:
>
> AdelPine
>
> From things that you have written, it seems to me that you have
> some fundamental misunderstandings.
Probably -- a common price of autodidacticism, alas! I do what I can, and
pay such prices when they blindside me ...
> My plan is that ultimately
> all these misunderstandings will be cleared up. The first thing
> that you need to understand is that the the 'AdelPine'
> incoming-folder is completely independent of Pine and it does not
> make sense to have the string 'Pine' as part of its name.
Aha -- OK, I hadn't gotten that. I think of email as consisting of Pine
and stuff not worth paying attention to, I'm afraid.
> I like
> to use a name that contains the string 'inbox' for my POP3
> inboxes, so I would use something like this:
>
> Adel-inbox
OK, done. But there was another price. Yesterday I had discovered
archiving, supposing it would be like the files my inbox and outbox put
things into by the month; so I created bblx.old, ACFG.old, etc., --
including AdelPine.old. Most of the messages in the other incoming
folders, having always been on titan, had never had anything relabelled as
new -- and everything got swept into one huge archive in one swell foop.
I can cope with that, when I get around to it; those folders are all still
there.
But renaming AdelPine to Adel-inbox made its archive evaporate;
fortunately, there wasn't much in it ...
Not that it's any fault of yours -- you had no reason to guess I might
suddenly start archiving. But if you have any idea whether those messages
still exist, and where, I'd like to know.
--
Beartooth Staffwright, PhD, Neo-Redneck, Double Retiree,
Not Quite Clueless Linux Power User : Fedora Core 5 [etc]
Beartooth
> Oops, I forgot to post the rename instructions... To rename this
> incoming-folder, use ML to go to the pine FOLDER LIST, select the
> AdelPine mailbox, type R (for Rename), and specify the new name.
I had renamed things before.
> You should be able to rename this from either 'pine' running on
> titan or 'pine' running on your local system (that's one of the
> beauties of the system we're setting up for you!)
I did it in Pine on titan, in case that matters.
> Also, here is a question about this mailbox:
>
> * Do you use any other email client to access this Adelphia
> INBOX? E.g., mutt, Thunderbird, and Adelphia webmail client or
> anything else?
Yes. When someone sends me a pic I actually want to look at, or when I'm
away from home and have to use an M$ machine in a public library, I point
any handy browser (except IE if I can help it; but I can't always) at
lserv.com/webmail, which I understand is a squirrelmail interface.
Fwiw, I also have a considerable number of subscriptions to lists I prefer
to use Gmane for; all but one of those are set to nomail. (The developers
of the oddball can't be bothered to make their software enable nomail, or
maybe couldn't even if they tried -- it's majordomo.)
Speaking of Gmane, btw, it shows two lists of yours --
gmane.org.infiniteink and gmane.org.infiniteink.general -- but neither
ever has any new posts. This usually means either that the list has died,
or else (much more likely in your case) that the listowner has taken it
back off. Is that so?
--
Beartooth Staffwright, PhD, Neo-Redneck, Double Retiree,
Not Quite Clueless Linux Power User : Fedora Core 5 [etc]
Beartooth
> On Thu, 25 May 2006 13:29:43 +0100, NM Public wrote:
>> Also, here is a question about this mailbox:
>>
>> * Do you use any other email client to access this Adelphia
>> INBOX? E.g., mutt, Thunderbird, and Adelphia webmail client or
>> anything else?
>
> Yes. When someone sends me a pic I actually want to look at, or when I'm
> away from home and have to use an M$ machine in a public library, I point
> any handy browser (except IE if I can help it; but I can't always) at
> lserv.com/webmail, which I understand is a squirrelmail interface.
Oooppss! Not enough coffee yet -- the above is true of the Lserv account,
and as a whole, not only the inbox. I don't recall ever having used
anything else to get to the Adelphia one, other than in the case of the
abiword list that I can't set to nomail. The messages from that come to
adelphia, and I'm now seeing them in Adel-inbox on titan -- and still
deleting most of them on sight, unless they're replies to questions I ask.