Branches
Articles referencing this project
Comments
[»]
Like an email client
by hillhopper - Nov 17th 2007 14:12:47
After some searching for free text only clients that also featured linking
to URLs, I found two worth using until I get Pine up and running. Phoenix,
and Vivian.
Vivian at http://www.deepsleep.de/e/vivianmail/
and Phoenix at
http://phxmail.sourceforge.net/
--
All mushrooms are edible. Some only once. -Croatian proverb
[reply]
[top]
[»]
Re: Like an email client
by hillhopper - Nov 17th 2007 14:23:19
> After some searching for free text only
> clients that also featured linking to
> URLs, I found two worth using until I
> get Pine up and running. Phoenix, and
> Vivian.
>
> Vivian at
> http://www.deepsleep.de/e/vivianmail/
>
> and Phoenix at
> http://phxmail.sourceforge.net/
This is also of value; SMTPdiag,exe at:
http://www.smtpdiagnostics.com/
>
>
>
>
>
--
All mushrooms are edible. Some only once. -Croatian proverb
[reply]
[top]
[»]
Mac OS X 10.2?
by Elden Fenison - Sep 4th 2002 15:05:09
Pine 4.44 seems to be broken under Mac OS X 10.2. Won't compile using Apple
dev tools. (gcc 3.1)
[reply]
[top]
[»]
NTLM authentication in PINE
by hrbrmstr - Apr 24th 2002 13:36:57
My employer has implemented a policy whereby only NTLM authentication is
accepted by the MS Exchange Server IMAP Service.
Previous to this, I was using PINE directly against the IMAP xch
service.
Now, I have to use fetchmail to periodically grab the mail and dump it
locally and use PINE/IMAP on a local server to read mail via Unix.
I see the various files for alternative authentication schemes, but I was
wondering if there is any sort of documentation regarding how one builds a
pluggable one. I'd like to extract/mangle the fetchmail/NTLM code (which is
extracted/mangled SAMBA code) and build a driver to support directly
authenticating via NTLM in PINE w/o having to use fetchmail.
Any pointers would be appreciated.
[reply]
[top]
[»]
Get rid of X-X-Sender?
by Tom - Apr 13th 2002 11:40:18
I figured out how to change the From header but now how do I get rid of the
X-X-Sender header?
[reply]
[top]
[»]
Quite Happy User
by Bill Wadley - Feb 17th 2002 05:17:36
I've used Pine as my MUA since I started using Linux, and that was 7 years
ago. Everyday, all day, for all of my email needs. I'm not saying it has
every feature known to humankind, but it has never let me down.
--
"The dinosaurs became extinct because they didn't have a space program."
-Larry Niven
[reply]
[top]
[»]
Re: Quite Happy User
by David Collantes - Feb 20th 2002 16:29:00
> needs. I'm not saying it has every
> feature known to humankind, but it has
> never let me down.
True, perhaps for you. Pine has been very limiting on what I can do in the
past, it has crashed on me, slowed me down, etc. I bet one thing tho', if
you go and try Mutt, you will not come back.
[reply]
[top]
[»]
Re: Quite Happy User
by Frédéric L. W. Meunier - Feb 21st 2002 18:11:08
>
> % needs. I'm not saying it has every
> % feature known to humankind, but it
> has
> % never let me down.
>
>
> True, perhaps for you. Pine has been
> very limiting on what I can do in the
> past, it has crashed on me, slowed me
> down, etc. I bet one thing tho', if you
> go and try Mutt, you will not come
> back.
So what ? From looking at your "Blah" post...
Yes, I also use Mutt, but respect their choice.
[reply]
[top]
[»]
Re: Quite Happy User
by David Collantes - Feb 23rd 2002 11:02:22
> So what ? From looking at your "Blah"
> post...
>
> Yes, I also use Mutt, but respect
> their choice.
Did I said I did not respected their choice? Learn how to read. I wrote
"..._if_ you give Mutt a try you will never go back..." I simply
stated a truth.
Peace.
[reply]
[top]
[»]
Re: Quite Happy User
by Frédéric L. W. Meunier - Feb 23rd 2002 18:56:58
>
> Did I said I did not respected their
> choice? Learn how to read. I wrote
> "..._if_ you give Mutt a try you
> will never go back..." I simply
> stated a truth.
Your "Blah" comment with "Get Mutt at (http://www.mutt.org/)"...
[reply]
[top]
[»]
Re: Quite Happy User
by FattMattP - Dec 6th 2002 13:13:17
> I wrote "..._if_ you give Mutt a try you
> will never go back..." I simply stated a truth.
That's not a truth. That's an assumption. You're assuming that someone
will like mutt enough to not go back to pine. I can speak from experience
that not going back isn't always the case.
I tried mutt for two months but went back to pine. In my opinion, pine
wins out over mutt in that it has a more refined user interface. The best
example that I can think if is how pine handles displaying of the message
index on the screen for different sized terminals. Pine will resize the
columns such as sender name, message size, and message subject so that they
take up the same percentage of width depending on the width of the
terminal. With mutt, I had to set the width in characters for each one of
these columns and it was fixed. Since I access my email server from many
different computers all with differing terminal sizes, this forced me to
enter numbers into the mutt config for a lowest common denominator (80x25).
Although I normally use a terminal size of 132x55 on my home computer, all
of my information was in the first 80 characters of each line. Had I set
the config for my 132x55 screen, I wouldn't even be able to see the subject
lines if I found myself on a 80x25 character console.
Another issue was that when I went to a folder list, or any list for that
matter, it would just print out one item per line. When you have a lot of
folders, that makes for a very long list. Pine is smart enough to list all
the items out in multiple columns that fit on my screen, much like the
ls command does.
It's little things like that which make the difference for me. Pine is
much more polished and a lot of thought went into the interface. Mutt
leaves me with the impression that it's just a quick hack. Although I've
never had either program crash on me or cause me any problems, mutt's
hackish presentation and nature left me with an uneasy feeling.
Honestly, I don't see any advantage of using mutt over pine save for the
fact that mutt allows for easy rebinding of key commands and has maildir
support. Mutt has nice threading, but pine has
had similar threading via a patch for some time now. The main
distribution has threading support in it now as well.
I've found that most of the people who have such a fervent liking for mutt
have never used pine. They're usually elm refugees that haven't bothered
to use another mail program and assume that all others from before mutt's
time must be as simplistic as elm. However, I realize that different
people like different tools. For you it may be mutt. For me, pine serves
my needs better than any other option I have found.
[reply]
[top]
[»]
Mutt
by Harri Haataja - Jan 15th 2002 12:58:14
Mutt sucks much less. =)
I've been happy ever since. Specially the vi-ish keys that resemble those
of less, vi, even slrn and other better software. Pine reeks so DOS-ish.
(which it actually is, at least in one incarnation)
[reply]
[top]
[»]
Blah
by David Collantes - Jan 14th 2002 15:01:16
Get Mutt at (http://www.mutt.org/)
[reply]
[top]
[»]
DOS newlines in attachments
by Pavel Roskin - Feb 8th 2001 20:01:09
Pine has a very annoying feature-bug. Text files
attached in Pine are converted to the DOS line
endings. Pine converts the test back to UNIX
style, but other mail clients don't.
As a result I'm forced either to insert the text
file inline or to compress it with gzip.
Why on earth should patches to UNIX programs (that
no DOS user will ever need) be transferred as
encoded files with DOS line endings?
[reply]
[top]
[»]
Re: DOS newlines in attachments
by Kari Hurtta - Apr 28th 2002 02:17:48
> Pine has a very annoying feature-bug. Text files
> attached in Pine are converted to the DOS line
> endings. Pine converts the test back to UNIX
> style, but other mail clients don't. <...>
> Why on earth should patches to UNIX
> programs (that no DOS user will ever need) be
> transferred as encoded files with DOS line endings?
I do not use Pine (I'm author of other mail client), but
that conversion is requirement of MIME. MIME says that
canonical encoing of text is CRLF endings of lines, so
base64 text data must have converted to CRLF ending
before encoding it if it is send as Text/* type. So what is that
"other mail clients" what you are refering ? (Assuming that
PINE labels attachment with type Text/...)
Basically almost all Internet standards use CRLF as line
ending for text data... :-)
[reply]
[top]
[»]
alan is right
by lymond - Nov 21st 2000 23:35:25
I agree with Alan. I also contacted the PINE guys to see if they could add
support for a way to attach a whole slew of files at one time. I sometimes
mail comic strips to my wife at work, up to seventy or so of them. To do a
control + j SEVENTY times is not friendly to a user. Now, you can select a
list option in Pine's address book which lets you choose multiple addies,
so why not code a list mode into attachments? For now, if you want this
feature, you can send multiple files on one cli with sendEmail or MFMail,
both found at freshmeat, by coincidence. grin. I do wish the PINE folk
seemed to care more about suggestions, tho.
[reply]
[top]
[»]
Re: alan is right
by Sukru Tikves - Apr 4th 2001 17:16:07
> I agree with Alan. I also contacted the
> PINE guys to see if they could add
> support for a way to attach a whole slew
> of files at one time. I sometimes mail
> comic strips to my wife at work, up to
> seventy or so of them. To do a control
> + j SEVENTY times is not friendly to a
> user. Now, you can select a list option
> in Pine's address book which lets you
> choose multiple addies, so why not code
> a list mode into attachments? For now,
> if you want this feature, you can send
> multiple files on one cli with sendEmail
> or MFMail, both found at freshmeat, by
> coincidence. grin. I do wish the PINE
> folk seemed to care more about
> suggestions, tho.
Well there is a simple program called "tar" to achive this goal,
independent of the mail program (eg: yahoo mail accepts 3 attachments at a
time, but you can send a .tar / .zip archive with 2000 files!)
[reply]
[top]
[»]
Re: alan is right
by Tuttle (Vlada Macek) - Apr 8th 2002 04:31:49
> I agree with Alan. I also contacted the
> PINE guys to see if they could add
> support for a way to attach a whole slew
> of files at one time. I sometimes mail
> comic strips to my wife at work, up to
> seventy or so of them. To do a control
> + j SEVENTY times is not friendly to a
> user. Now, you can select a list option
> in Pine's address book which lets you
> choose multiple addies, so why not code
> a list mode into attachments?
Well, it seems, as of version 4.40, Pine still lacks this quite useful
feature I would wish too. But you can do this for yourself, by using the
-attachlist command line option, which must be the last one on the
command line. After it you can add all files you want to send to your wife
(Pine will jump directly into Compose mode).
In the case you prepared the files in the separate directory, the job is
even easier than selecting one by one in the non-existing "multiple list"
feature, e.g. pine wife -attachlist temp4wife/*
Smile,
Tuttle
[reply]
[top]
[»]
Suggestion for Pine
by Alan Bryant - Nov 21st 2000 17:52:47
I already contacted the authors of Pine and requested this, but they didn't
seem very interested. In Pine, there is an option to select multiple To:
addresses at the same time, byt selecting the list option within the
addressbook. Well wouldn't it be a good idea if you could do that with
attachments as well? For now, the only way to select multiple attachments
is one at a time, which can be time consuming.
[reply]
[top]
[»]
Take care with 4.30
by Frédéric L. W. Meunier - Oct 30th 2000 20:47:53
Some bugs were found after this release. Maybe the worse is "No -DDEBUG
makes pine not configurable". Some patches are available at the
comp.mail.pine newsgroup. A new release should be available soon (and I
hope with Maildir support, since it's of use for some of us without it).
[reply]
[top]
[»]
from:-field.
by Simon Kagstrom - Sep 3rd 2000 10:21:34
Hello.
Is it possible to change the sender field in pine? I always get
username@localhost, whereas I want my real address there. Stupid error...
// Simon
[reply]
[top]
[»]
Re: from:-field.
by Brian E. Seppanen - Feb 1st 2001 20:32:59
> Hello.
>
> Is it possible to change the sender
> field in pine? I always get
> username@localhost, whereas I want my
> real address there. Stupid error...
>
> // Simon
Yes, there are several good resources available on the web. Do a
simple deja news search, or a google search. Don't ask the question
without wearing asbestos underwear on comp.mail.pine. Some of
the *Regulars* there tend to get upset when the question is asked.
--
Area 54: The Secret Government Disco Labs in Provo Utah
[reply]
[top]
[»]
Re: from:-field.
by Aleksey Nogin - Feb 2nd 2001 00:40:54
Is it possible to change the sender field in pine?
Yes. See http://www.ii.com/internet/messaging/pine/changing_from/#changing
[reply]
[top]
[»]
Pine CRYPT Errors!
by cspence@delphi-tech.com - Jan 17th 2000 16:22:36
Pine 4.21 assumes you use Libc5. If you have Libc6, crypt is seperate.
you have to add the link option -lcrypt for it to compile.
[reply]
[top]
[»]
Stable and (Reasonably) Secure mailbox on a Networked PC Client is Required.
by siva - Jun 4th 1999 15:36:12
Pine - I would like to see a version of PC Pine for use with a networked PC
with a way of ensuring that each user's mailbox is secure and moves with
the user from PC to PC. The existing use of environment variable prevents
this. One way to do this is to eliminate use of the environment variable,
and a config file located in a fixed location eg. C:\, and use the login
script to copy down the user's config file down from the server (Samba
preexec command). The user's config file could specify a mailbox which is
on a private Samba share accessible to the user only, thereby preventing
anyone else accessing it and making the mailbox move with the user if he
logs onto another machine. It is possible for someone to change the config
file located in C:\, but since it will be overwritten for each login, other
user's mailboxes can't be read. I consider the environment variable as a
bad way to set the file locations in any case because of possible security
problems.
[reply]
[top]
|
