Matt Ackeret | 28 Aug 03:59 2015
Picon

Quelling the "server didn't respond" prompt?


The other recent discussion of perf issues reminds me of something I've
been seeing lately..

I often get the (paraphrase) "The server didn't respond in 60 seconds?
Disconnect?" prompt.

Basically, I NEVER want this prompt. I *know* I can just ignore it and it'll
go away when it reconnects..

But this is one of the times when the modal-ish nature of alpine is slightly
a pain.   My "workaround" is to use a GUI mail reader alongside alpine (I also
use it to view the rich emails with charts or something that I really want/need
to read, e.g. work emails)... and of course I can still use it while alpine is
hung.

Is clearing out tons of email from my INBOX really the only workaround?
(I have over 88K messages in my INBOX at the moment -- and a few years ago,
I made a separate mailbox for INBOX before 2010!)
stef | 27 Aug 12:20 2015
Picon

Alpine Sluggish on IMAP folders

Hi,

I am trying to resolve an issue which is somewhat frustrating: Alpine is slow/sluggish to refresh, mostly
noticed when switching between one email collection to another (so one email account to another), using
the "L" command. 

As well, it is fairly sluggish repainting the screen when hitting <space> to switch pages, etc.

Courier IMAP.
I'm on Linux.
My setup is very plain-vanilla, using most of the defaults; I have not messed with anything I can recall.  

I have 2 collections in the one profile and 3 collections in another profile I use.  I have about 12k emails in
the INBOX./ tree. 

(More than 3 email accounts seems to really slow things down so that is the limit I set, arbitrarily.)

I have read a few suggestions on various websites (e.g. Stayopen folders, etc.) but fail to get a clear
understanding of which parameters/options/settings to use to improve efficiency in
refreshing/repainting. 

Which parameters are suitable for this situation?  There seem to be quite a few which could be pertinent but
it is hard to tell which, if any, could help improve the situation and I'd appreciate some feedback from
experienced users here.

Thanks.
Bob Bernstein | 24 Aug 21:30 2015

Reply acting up

Due to pilot error I had to reconfigure alpine pretty much from 
scratch. Now, "Reply" fails to give me a choice between everyone 
("Reply All") or not. So, when answering an email list message 
that was Cc'd to me it's as if alpine doesn't even see that.

Isn't there an option for an enhanced Reply menu?

--

-- 
Bob Bernstein
Thomas Gramstad | 24 Aug 03:47 2015
Picon
Picon

Error message when trying to postpone message (fwd)

When I try to postpone a message I'm writing with Ctrl-O I get this error 
message:

> Fcc: Error:  "Permission denied" Message NOT sent or copied.

I'm a MS Exchange survivor -- I recently got away from this 
horror, replacing mail.uio.no with imap.uio.no, and I suspect the 
problem may be related to some leftovers from MS Exchange.

Thomas Gramstad
Wang Kang | 21 Aug 20:01 2015
Picon

Added GB18030 charset support for Alpine


Hi, all

GB18030 is a Chinese charset, basically it completely equals to GBK. Some 
mail provider use GB18030 like QQ Mail, which has large number of users in 
China for now.

I added GB18030 support by adding a simple patch as below. And it works!

Hope someone can add this patch to new version of alpine.

Thanks!

diff --git a/alpine-2.10+dfsg/imap/src/c-client/utf8.c
b/alpine-2.10+dfsg/imap/src/c-client/utf8.c
index 8fda7ff..2f15d06 100644
--- a/alpine-2.10+dfsg/imap/src/c-client/utf8.c
+++ b/alpine-2.10+dfsg/imap/src/c-client/utf8.c
 <at>  <at>  -170,6 +170,9  <at>  <at>  static const CHARSET utf8_csvalid[] = {
     (void *) &gb_param,SC_CHINESE_SIMPLIFIED,"GBK"},
        {"CN-GB",CT_DBYTE,CF_DISPLAY,
              (void *) &gb_param,SC_CHINESE_SIMPLIFIED,"GBK"},
              +// added by scateu  <at>  2015-08-22
              +  {"GB18030",CT_DBYTE,CF_DISPLAY,
              +     (void *) &gb_param,SC_CHINESE_SIMPLIFIED,"GBK"},
               #ifdef CNS1TOUNICODE
                  {"ISO-2022-CN",CT_2022,CF_PRIMARY | CF_UNSUPRT,
                        NIL,SC_CHINESE_SIMPLIFIED |
                        SC_CHINESE_TRADITIONAL,

(Continue reading)

Bob Bernstein | 6 Aug 16:56 2015

Folders

I feel like I must have gone 'round the bend a little bit _more_, since I 
do not know how to set up my folders so that, when they are opened, the 
most recent messages are displayed, i.e. the current "end" of the list is 
displayed, regardless of any unread "New" messages etc.

Thx!

--

-- 
Bob Bernstein
Bob Bernstein | 5 Aug 18:16 2015

configure weirdness with openssl

Hi Everyone!

I am coming up with some really weird behaviour trying to build 
alpine-2.20. I grabbed the tarball last night from your archive. 
I get a configure error telling me to install openssl >= 1.0.1.c 
but I have version 1.0.1k-3+deb8u1 installed.

To compound the mystery, the identical 2.20 alpine source 
configures and builds just fine on another debian system I have. 
That one is i386, ver. 7.8, the problem child is amd64, ver. 
8.1, but why should a configure test screw up?

tia

--

-- 
IMPORTANT: This email is intended for the use of the individual
addressee(s) named above and may contain information that is
confidential, privileged or unsuitable for overly sensitive
persons with low self-esteem, no sense of humour or irrational
metaphysical beliefs.

Mike Miller | 4 Aug 00:44 2015
Picon

fetchmail problem with gmail -- is it just me?

I hope this isn't too off-topic -- it is about how I use Alpine, and I 
think I mustn't be the only one doing this.

I use Alpine on a Linux box, using the Gmail SMTP server to send the mail 
and using fetchmail to retrieve incoming mail.  It checks every 5 minutes 
for new messages.

Starting a week or so ago, I'm having the problem that fetchmail isn't 
getting any messages for stretches of time in the middle of the day even 
though the messages are in my inbox at gmail.com.  Checking the logs...

from /var/log/mail.log (replacing my username with "me"):

Aug  3 17:14:53 taxa fetchmail[6884]: awakened at Mon 03 Aug 2015 05:14:53 PM CDT
Aug  3 17:14:53 taxa fetchmail[6884]: Server certificate verification error: certificate signature failure
Aug  3 17:14:53 taxa fetchmail[6884]: SSL connection failed.
Aug  3 17:14:53 taxa fetchmail[6884]: socket error while fetching from me@... <at> pop.gmail.com
Aug  3 17:14:53 taxa fetchmail[6884]: Query status=2 (SOCKET)
Aug  3 17:14:53 taxa fetchmail[6884]: sleeping at Mon 03 Aug 2015 05:14:53 PM CDT for 300 seconds

Aug  3 17:19:53 taxa fetchmail[6884]: awakened at Mon 03 Aug 2015 05:19:53 PM CDT
Aug  3 17:19:53 taxa fetchmail[6884]: Server certificate verification error: certificate signature failure
Aug  3 17:19:53 taxa fetchmail[6884]: SSL connection failed.
Aug  3 17:19:53 taxa fetchmail[6884]: socket error while fetching from me@... <at> pop.gmail.com
Aug  3 17:19:53 taxa fetchmail[6884]: Query status=2 (SOCKET)
Aug  3 17:19:53 taxa fetchmail[6884]: sleeping at Mon 03 Aug 2015 05:19:53 PM CDT for 300 seconds

It has been working without a hitch for about 7 years and I haven't 
changed anything.  It ultimately gets the messages several hours later.

(Continue reading)

Porcelain Mouse | 24 Jul 23:51 2015
Picon

Fedora 22 + TMUX = broken reverse color char escape

Hi All,

Anyone else use Fedora?  I just upgraded to F22 and I'm beset by strange 
terminal issues.  One is broken reverse color when using TMUX (and 
TERM=screen, which is the default).  Anybody else see this?  All 
characters that should be reverse color are actually italic font, not 
reverse color.

I'm contacting Alpine-Info because I *really* notice it with Alpine. 
Alpine uses reverse color lots of little places: all menus and all notice 
messages, just for starters.  It looks very different, now.

Alpine isn't the only place this happens, so it's not Alpine.  Even 'man' 
is affected, and so is 'less.' It occurs with Gnome-terminal, LXterminal, 
Xfce Terminal, and the real xTerm, at a minimum.  How this got past 
*anyone* else, I have no idea.  Does this make any sense to anyone else?

(Setting TERM=xterm fixes this particular problem, but TMUX, unlike 
screen, reacts very badly to that configuration.)

--

-- 
PMouse
Stefan | 19 Jul 02:01 2015
Picon

Alpine on OS X Yosemite


Dear Özgür,

could you explain how to install ALpine 2.20 on a fresh Yosemite (10.10.4) 
install? I am new to Macs and OS X. I downloaded the binary you compiled 
from Eduardo's website (see below), but simply copying that to the the 
right location wasn't enough, it seems. Upon starting alpine, it complains 
about some openssl library not being found. Do I need to install 
homebrew/fink/macports or something similar?

> As a side note, 2.20 binaries for OS X are available at
> http://patches.freeiz.com/alpine/release/index.html. I built the Intel
> version on OS X Yosemite 10.10.1, and the PPC version on Leopard 10.5.8.
> They should be backwards compatible.
>

Greetings, Stefan

Dear Özgür,

could you explain how to install ALpine 2.20 on a fresh Yosemite (10.10.4) 
install? I am new to Macs and OS X. I downloaded the binary you compiled 
from Eduardo's website (see below), but simply copying that to the the 
right location wasn't enough, it seems. Upon starting alpine, it complains 
about some openssl library not being found. Do I need to install 
homebrew/fink/macports or something similar?

> As a side note, 2.20 binaries for OS X are available at
> http://patches.freeiz.com/alpine/release/index.html. I built the Intel
(Continue reading)

Beartooth | 12 Jul 21:51 2015
Picon
Picon

<sigh> The old, old "access error"


	I have a local Net access account with Comcast. When it began to 
offer IMAP, I signed up -- and started trying to access my Comcast email 
with Alpine. 

	Whenever I go to it, I get a minute or two of normal behavior, 
then the old bete noir: 

[MAIL FOLDER "INBOX" CLOSED DUE TO ACCESS ERROR]

	If I'm quick enough, I can delete the first four or five spams on 
sight (without opening any) before I get the error message. Then I have 
to hit L, <enter>, <enter> to get another minute or two of access. 

	Then I start getting the egregious "[No reply in XYZ seconds from 
server imap.g.comcast.net. Still Waiting]," with no way I know to get 
back into my email except endless waiting for a chance to hit Y (meaning 
yes, break the connection).

	I have a faint recollection, or maybe a cyber-mirage, to the 
effect that once, years ago and far away, there was a way to get out of 
this dead end. Am I imagining it? Or is it still usable?

--

-- 
Beartooth Staffwright, Not Quite Clueless Power User
Remember I know little (precious little!) of where up is.


Gmane