To: column in Sentmail screen?
Howard Schwartz
From and Subject. I already know they are all from me! Is there any way to
get this index screen to show the To: header. This would help me a lot in
locating sent messages of interest.
Lucas Levrel
In Pine 4.64 the behaviour you want is the default. See the help page on
config option "index-format". If you have several addresses you'll have to
setup "alt-addresses" (from the help page of "index-format", follow the
link on tokens, and find the paragraph about FROMORTO).
--
LL
Howard Schwartz
news:Pine.LNX.4.64.09...@coulomb.univ-paris12.fr:
> In Pine 4.64 the behaviour you want is the default. See the help page
> on config option "index-format". If you have several addresses you'll
> have to setup "alt-addresses" (from the help page of "index-format",
> follow the link on tokens, and find the paragraph about FROMORTO).
Actually, I use Alpine V. 2, not Pine V. 4.64 - but the behaviour is the
same. I realized that the default columns are what I want for the message
index of messages sent TO ME. Here I want a column telling me ``From''.
But in the message index (e.g., within sentmail), I want the opposite: I
know all the messages are ``From" me. I want to know who I sent them
`To'.
Fortunately, alpine can configure that with the Index Fromat and the
Alternate Addresses options: There is a token called FromTo that I
display the From Person, if that person is NOT you. Otherwise it displays
the person it is `To'
Because of alias and forwarding issues, the email address people use for
me, is not identical to the one sfo.com wants and expects. Therefore I
use `Alternate Addresses' to specify aliases, old addresses, web
addresses, etc. -- that others might use to write me.
Voila! Now messages sent by me always display who I sent the message To,
within the Fcc file, index screen. Hope this might help others.
Supreet Joshi
On Wed, 14 Oct 2009, Howard Schwartz wrote:
> Lucas Levrel <lucas....@univ-paris12.fr> wrote in
> news:Pine.LNX.4.64.09...@coulomb.univ-paris12.fr:
>
>> In Pine 4.64 the behaviour you want is the default. See the help page
>> on config option "index-format". If you have several addresses you'll
>> have to setup "alt-addresses" (from the help page of "index-format",
>> follow the link on tokens, and find the paragraph about FROMORTO).
>
> Fortunately, alpine can configure that with the Index Fromat and the
> Alternate Addresses options: There is a token called FromTo that I
> display the From Person, if that person is NOT you. Otherwise it displays
> the person it is `To'
>
Is there a way to apply different index-formats to different folders ?
Regards,
Supreet.
Lucas Levrel
> Is there a way to apply different index-formats to different folders ?
In pine, see Config option "index-rules".
--
LL
Supreet Joshi
Unfortunately, the version of Pine I use (4.44) does not have that option.
Instead, I used Setup -> Rules -> Other Rules. THere exist options to
specify index formats and sort orders for specific folders.
Supreet.
Andreas Prilop
> Unfortunately, the version of Pine I use (4.44) does not have that option.
In order to read and send special, non-ASCII characters correctly,
you should use the following options:
feature-list=
downgrade-multipart-to-text,
enable-8bit-esmtp-negotiation,
enable-8bit-nntp-posting,
pass-c1-control-characters-as-is
#character-set=ISO-8859-1
character-set=Windows-1252
� � = 50 � (0.5 euro = 50 cent)
--
Solipsists of the world � unite!
Mark Crispin
> downgrade-multipart-to-text,
There is no need for this setting. It will make your messages be
vulnerable to corruption if they are quoted-printable or base64 encoded.
MIME has been defined for something like 18 years. It is long past time
for people to use MIME-compliant MUAs.
-- 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.
Lucas Levrel
> On Wed, 21 Oct 2009, Supreet Joshi wrote:
>
> > Unfortunately, the version of Pine I use (4.44) does not have that option.
>
> In order to read and send special, non-ASCII characters correctly,
> you should use the following options:
I'm not sure what you're talking about. Supreet Joshi only has 7bit
characters in its message.
> #character-set=ISO-8859-1
> character-set=Windows-1252
And why would one need cp1252 rather than latin-1 (which is ISO)?
--
LL
Lucas Levrel
> > downgrade-multipart-to-text,
>
> There is no need for this setting.
Yes there is. Or it wouldn't exist!
> It will make your messages be vulnerable
> to corruption if they are quoted-printable or base64 encoded.
Isn't quoted-printable an undesirable thing on Usenet? (real question, I
seem to remember having read this in usage advice of some groups)
> MIME has been defined for something like 18 years. It is long past time for
> people to use MIME-compliant MUAs.
As long as this doesn't break something on my side, I always do what I can
so that my messages display gracefully at the recipient's. On Usenet this
is mandatory if you want to be read at all!
In particular, I had to put this setting so that my utf-8 messages display
correctly at some people's. I think the special Content-type: header field
prevented their MUA from seeing they were utf-8 encoded. I may do some
search to find back what precise settings were needed, if you like.
--
LL
Andreas Prilop
> I'm not sure what you're talking about. Supreet Joshi only has 7bit
> characters in its message.
It tried to quote your word "�crit" but it failed.
>> #character-set=ISO-8859-1
>> character-set=Windows-1252
>
> And why would one need cp1252 rather than latin-1 (which is ISO)?
� � = 50 �
� = OE
� = oe
Andreas Prilop
> MIME has been defined for something like 18 years.
> It is long past time for people to use MIME-compliant MUAs.
Why then do I still read Subjects like in
<news:200902261035....@www.epaxios.com>
http://groups.google.co.uk/group/de.alt.netdigest/msg/8630a879647350e5
or in
<news:4a4e4379$0$9889$91ce...@newsreader03.highway.telekom.at>
http://groups.google.co.uk/group/de.etc.sprache.deutsch/msg/9b34f39aae7af7e0
every day?
Why then does Google show Arabic letters in
http://groups.google.co.uk/group/de.test/msg/2a6c653ecde6726a
?
--
Top-posting.
What's the most irritating thing on Usenet?
Lucas Levrel
> On Thu, 22 Oct 2009, Lucas Levrel wrote:
>
> > I'm not sure what you're talking about. Supreet Joshi only has 7bit
> > characters in its message.
>
> It tried to quote your word "écrit" but it failed.
OK. I was confused because you were not replying to me.
As for "écrit", do you mean you see it correctly but it gets corrupted
when you edit your answer? What do you get exactly?
> > And why would one need cp1252 rather than latin-1 (which is ISO)?
>
> ½ € = 50 ¢
> Π= OE
> œ = oe
True that if you use latin-9 (iso-8859-15) you won't have ½. But my use of
any encoding shouldn't prevent you from seeing non-ASCII chars. BTW, my
current encoding isn't latin-1 but utf-8, which can encode any char.
--
LL
Andreas Prilop
>>> Supreet Joshi only has 7bit characters in its message.
>>
>> It tried to quote your word "�crit" but it failed.
>
> As for "�crit", do you mean you see it correctly but it gets
> corrupted when you edit your answer?
The message of Supreet Joshi had
CHARSET=X-UNKNOWN
Andreas Prilop
> Andreas Prilop posted:
>
>> downgrade-multipart-to-text
>
> There is no need for this setting. It will make your messages be
> vulnerable to corruption if they are quoted-printable or base64 encoded.
Okay - you are right! I stay corrected!
Sending multipart/mixed will make http://groups.google.com/
respect the encoding (charset) of a message. Examples at
http://groups.google.co.uk/group/de.test/browse_thread/thread/eac395a2476fc3cf/
Messages with multipart/mixed are currently shown correctly in
Google and those without multipart/mixed are shown incorrectly.
This happens for _both_ 8bit and quoted-printable.
Sure, groups.google.com is wrong in ignoring the charset of a
message and this is a severe bug - but it shows an important benefit
of multipart/mixed.
--
I used to believe in reincarnation in a former life.