Karen Lewellen | 22 Dec 15:50 2014
Picon

for the alpine issue. (fwd)

Hi,
here it is.
I needed to be careful as this problem is tied to a totally different 
address. I use pine here at shellworld and did not want to get the files 
confused.
thanks,
Karen

From: karen lewellen <klewellen@...>
Subject: for the alpine issue.

Karen Lewellen - President/Senior Producer
Curtain Up Distribution INC.
Using media to champion under represented voices & ideas since 1990.
#
# Alpine configuration file
#
# This file sets the configuration options used by Alpine and PC-Alpine. These
# options are usually set from within Alpine or PC-Alpine. There may be a
# system-wide configuration file which sets the defaults for some of the
# variables. On Unix, run alpine -conf to see how system defaults have been set.
# For variables that accept multiple values, list elements are separated by
# commas. A line beginning with a space or tab is considered to be a
# continuation of the previous line. For a variable to be unset its value must
# be blank. To set a variable to the empty string its value should be "".
# You can override system defaults by setting a variable to the empty string.
# Lines beginning with "#" are comments, and ignored by Alpine.

# Over-rides your full name from Unix password file. Required for PC-Alpine.
(Continue reading)

Karen Lewellen | 21 Dec 05:26 2014
Picon

"Inbox closed due to access error?"

Hi all,
I think I mentioned having this problem before, but might not have  shared the 
exact issue.
It is continuing even though the provider involved has moved our server to 
the same one where their mail  is managed, same computer area I should 
say.
Here is what happens.  I am reading mail in alpine, and find  I wish to 
answer.  While I am drafting my email though my inbox apparently closes, so 
that when I am finished I cannot go back to reading email.
I hope this is making sense, as I have never had the problem with any other 
mail program.
I am for example drafting this email in pine, and know my inbox will still 
be waiting for me once I am done.
Thoughts?
Karen

Karthik Vishwanath | 12 Dec 18:05 2014
Picon

deleting messages

Hello,

I use alpine for reading mail from a gmail account. There are 2 issues I am having:

1. When I "delete" and then "expunge" a message in my INBOX, it is gone from my INBOX but is still available under "[Gmail]/All Mail". Is there way for me to make alpine move these messages to the "[Gmail/Trash" folder, instead?

2. The second issue regards when messages marked "D" are actually expunged. Previously, I had to use "X" for expunging them. Although I have the option "Expunge Only Manually" selected, messages from INBOX are expunged on other operations (such as saving other messages, or pressing the down-arrow on the last message etc). How to change this behavior?


Thanks,

--
-Karthik Vishwanath
<div><div dir="ltr">
<div>
<div>Hello,<br><br>
</div>I use alpine for reading mail from a gmail account. There are 2 issues I am having:<br><br>
</div>1. When I "delete" and then "expunge" a message in my INBOX, it is gone from my INBOX but is still available under "[Gmail]/All Mail". Is there way for me to make alpine move these messages to the "[Gmail/Trash" folder, instead? <br><div><br></div>
<div>2. The second issue regards when messages marked "D" are actually expunged. Previously, I had to use "X" for expunging them. Although I have the option "Expunge Only Manually" selected, messages from INBOX are expunged on other operations (such as saving other messages, or pressing the down-arrow on the last message etc). How to change this behavior? <br><br><br>
</div>
<div>Thanks,<br>
</div>
<div><br clear="all"></div>
<div><div><div><div>
<div><div class="gmail_signature">--<br>-Karthik Vishwanath<br>
</div></div>
</div></div></div></div>
</div></div>
Jose Riha | 8 Dec 09:59 2014
Picon

server-side search for gmail

hello list,

does anyone knows if it is possible to do a serverside search in 
configured gmail account? it is quite common that i need to go further 
back than my current imap limit of 1000 synced messages. is such thing 
planned for the future or anyone knows of a workaround (other than 
reaching for my smartphone or logging via webbrowser)?

thank you, jose
David Sewell | 6 Dec 21:43 2014

Clear screen option on exit?

I can't remember if this has ever come up as a feature request for 
Alpine, but would others agree that it would be useful for alpine to 
do a screen-clear before exiting? Otherwise, one's index headers remain 
visible, and that is a privacy concern to some extent.

Of course it's easy to write an alias or function that invokes alpine 
and then "clear" or equivalent, but I've wondered why it is not built 
in.

David S.
Walter Cazzola | 3 Dec 16:27 2014
Picon

alpine and leafnode

Dear Alpine Experts,
I'm used to access newsgroups through alpine with satisfaction. To do
that I've a leafnode server installed on my machine.

Recently I've reinstalled my machine with Fedora 20 and since then
alpine refuses to connect to the leafnode server with the message:

   400 NNTP connection broken (response)

the leafnode server seems running since it replies to telnet as:

  >telnet localhost 119
  Trying ::1...
  Connected to localhost.
  Escape character is '^]'.
  200 Leafnode NNTP Daemon, version 1.11.8 running at localhost

and also fetchnews seems doing its work:
  >fetchnews -vv
  leafnode 1.11.8: verbosity level is 2, debugmode is 1
  try_lock(timeout=5), fqdn="localhost"
  news.aioe.org: connecting to port nntp...
  news.aioe.org: connected to 94.75.214.39:119, reply: 200
  news.aioe.org: connected.
  news.aioe.org: using STAT <message-ID> command.
  news.aioe.org: 0 articles posted.
  news.aioe.org: getting new newsgroups
  news.aioe.org: got 0 new newsgroups.
  news.aioe.org: reading server info from
  /var/spool/news/leaf.node/news.aioe.org
  news.aioe.org: conversation completed, disconnected.
  wrote active file with 29454 lines
  Started process to update overview data in the background.
  Network activity has finished.

Even if without a client I can't subscribe any group but the list of the
groups available on the remote server is correctly in
/var/spool/news/leaf.node/groupinfo

In the .pinerc I've:

   nntp-server=localhost:119
   folder-collections=Mail mail/[],
           {127.0.0.1/nntp}#news.[]

and in general the content of the .pinerc didn't change between the two
installations of the machine.

Currently I'm using

   leafnode-1.11.8-11.fc20.x86_64
   alpine-2.11-1.fc20.x86_64

/etc/leafnode belongs to news.news and my user is in the group news.

I don't have any idea about how to solve the problem. Also googling
around on the error message I didn't find anything useful.

Do you have any idea?

Thank you in advance for your time.

Best Regards
Walter

--

-- 
Ulf-Dietrich Braumann | 2 Dec 12:09 2014
Picon

advanced bouncing

Hello,

is there a way to bounce a set of selected messages using a specific role?

Thanks - UD
Robert Giles | 20 Nov 23:32 2014
Picon

S/MIME versus Thunderbird 31.2.0

Hi folks - wondering if anyone else has had problems with Thunderbird 
complaining about S/MIME-signed e-mails from Alpine?

Thunderbird reports:  "Digital Signature Is Not Valid - This message 
includes a digital signature, but the signature is invalid.  The 
signature does not match the message content correctly.  The message 
appears to have been altered after the sender signed it.  You should not 
trust the validity of this message until you verify its contents with 
the sender."  (screenshots attached if the alpine-info list permits it)

Microsoft Outlook 2013 has no problems with the exact same e-mail, 
reporting:  "Digital Signature:  Valid".

Thunderbird seems to play nice with various versions of Thunderbird and 
Outlook;  just doesn't seem to like Alpine?

Alpine in this transaction is 2.19.9992 (DEB 65 2014-06-20).

Thanks -

Robert

Attachment (smime.p7s): application/pkcs7-signature, 5146 bytes
Hi folks - wondering if anyone else has had problems with Thunderbird 
complaining about S/MIME-signed e-mails from Alpine?

Thunderbird reports:  "Digital Signature Is Not Valid - This message 
includes a digital signature, but the signature is invalid.  The 
signature does not match the message content correctly.  The message 
appears to have been altered after the sender signed it.  You should not 
trust the validity of this message until you verify its contents with 
the sender."  (screenshots attached if the alpine-info list permits it)

Microsoft Outlook 2013 has no problems with the exact same e-mail, 
reporting:  "Digital Signature:  Valid".

Thunderbird seems to play nice with various versions of Thunderbird and 
Outlook;  just doesn't seem to like Alpine?

Alpine in this transaction is 2.19.9992 (DEB 65 2014-06-20).

Thanks -

Robert

Bob Bernstein | 16 Nov 19:40 2014

recall earlier values


Let's say I am composing a new message, and I am 
editing the To header. Is there a key-stroke combo 
that will recall a recently used To address so I do 
not have to retype or refind it in the address book? 
Perhaps also for the Subject or other headers?

nb. I posted this a few days ago but used an MUA other 
<gasp> than Alpine. Then I started having dark 
phantasies that perhaps the list server has a kill 
file for such transgressions. Even though a quick 
check of the list archives relieved me of that fear, I 
thought, along simple diplomatic lines, to repost 
using Alpine. <oh well>

--

-- 
"Natasha! First we shoot jet, then we go after moose and squirrel."

Bob Bernstein | 14 Nov 04:16 2014

command history?

Let's say I am composing a new message, and I am editing the To 
header. Is there a key-stroke combo that will recall a recently used 
To address so I do not have to retype or refind it in the address 
book? Perhaps also for the Subject or other headers?

thanx,

--

-- 
Bob Bernstein

			 
Gregory Heytings | 7 Nov 11:34 2014

Decoding bug?


Hi list,

I'm facing an apparent decoding bug.  Assume the following input email:

----SNIP----
From foo@...  Sat Nov  1 02:03:04 2014
Date: Sat, 01 Nov 2014 02:03:04 +0500 (CET)
From: Foo <foo@...>
To: Bar <bar@...>
Subject: Baz
Content-Type: multipart/mixed; boundary="=_boundary"
MIME-Version: 1.0

--=_boundary

From foo to bar

--=_boundary
Content-Type: text/csv; name="example.csv"
Content-Disposition: attachment; filename="example.csv"
Content-Transfer-Encoding: base64

Rm9vO0pvc8OpO0JhcjsK

--=_boundary--
----SNIP----

When I try to view the attached file with alpine (2.11 or 2.19.9992), I 
have "Foo;Jos??;Bar;".  When I save it to a file, I also have 
"Foo;Jos??;Bar;", with the following hexdump:

46 6f 6f 3b 4a 6f 73 3f 3f 3b 42 61 72 3b 0a |Foo;Jos??;Bar;.|

However, if I feed the string "Rm9vO0pvc8OpO0JhcjsK" to the base64 
utility, I have "Foo;José;Bar;", with the following hexdump:

46 6f 6f 3b 4a 6f 73 c3 a9 3b 42 61 72 3b 0a |Foo;José;Bar;.|

This is what I would have expected in the first place: the attached file 
is encoded in UTF-8, and the bytes 8 and 9 should be 0xc3a9 (which is the 
UTF-8 encoding for the small letter e with acute), and NOT 0x3f3f.  I 
would have guessed that the encoding of the file should not be relevant in 
the decoding process of a base64-encoded attachment, but apparently it is.

Is this a bug?  Or is something incorrectly formatted in the input email?

Gregory

Hi list,

I'm facing an apparent decoding bug.  Assume the following input email:

----SNIP----
From foo@...  Sat Nov  1 02:03:04 2014
Date: Sat, 01 Nov 2014 02:03:04 +0500 (CET)
From: Foo <foo@...>
To: Bar <bar@...>
Subject: Baz
Content-Type: multipart/mixed; boundary="=_boundary"
MIME-Version: 1.0

--=_boundary

From foo to bar

--=_boundary
Content-Type: text/csv; name="example.csv"
Content-Disposition: attachment; filename="example.csv"
Content-Transfer-Encoding: base64

Rm9vO0pvc8OpO0JhcjsK

--=_boundary--
----SNIP----

When I try to view the attached file with alpine (2.11 or 2.19.9992), I 
have "Foo;Jos??;Bar;".  When I save it to a file, I also have 
"Foo;Jos??;Bar;", with the following hexdump:

46 6f 6f 3b 4a 6f 73 3f 3f 3b 42 61 72 3b 0a |Foo;Jos??;Bar;.|

However, if I feed the string "Rm9vO0pvc8OpO0JhcjsK" to the base64 
utility, I have "Foo;José;Bar;", with the following hexdump:

46 6f 6f 3b 4a 6f 73 c3 a9 3b 42 61 72 3b 0a |Foo;José;Bar;.|

This is what I would have expected in the first place: the attached file 
is encoded in UTF-8, and the bytes 8 and 9 should be 0xc3a9 (which is the 
UTF-8 encoding for the small letter e with acute), and NOT 0x3f3f.  I 
would have guessed that the encoding of the file should not be relevant in 
the decoding process of a base64-encoded attachment, but apparently it is.

Is this a bug?  Or is something incorrectly formatted in the input email?

Gregory

Gmane