From kolos at tatar.hu Fri Oct 3 03:21:54 2014 From: kolos at tatar.hu (Tatar Kolos) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] filtering based on email address isn't working Message-ID: Hi, I'm using Alpine at work to connect to my email through IMAP. I'm trying to set up filtering rules based on email, but it appears if I specify bits of the email addresses before the '@' sign, it works, once I add the '@' sign, it doesn't (ie - full email addresses don't work in filters). Anyone any idea what I might be missing here? Alpine 2.10 (LFD 1266 2009-07-14) built Thu Oct 31 17:31:10 UTC 2013 on buildvm-19.phx2.fedoraproject.org Cheers, Kolos From letter at openmailbox.org Tue Oct 7 07:32:21 2014 From: letter at openmailbox.org (message) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] tor incompatibility Message-ID: <3d5fb64957a10595b1a23e612da87d31@openmailbox.org> Readers, Trying to use alpine with tor, to send and receive mail. Alpine started: torsocks alpine Receipt of mail fails, reporting a time out error. Transmission of mail fails reporting the following error: [Mail not sent: : Client host rejected: A] Correct configuration advice please From alpine at nephros.org Tue Oct 7 08:29:32 2014 From: alpine at nephros.org (Peter G.) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] tor incompatibility In-Reply-To: <3d5fb64957a10595b1a23e612da87d31@openmailbox.org> References: <3d5fb64957a10595b1a23e612da87d31@openmailbox.org> Message-ID: Hello. Hodie Non. Oct. MMXIV AUC quidam/qu?dam/quoddam 'message' inquit: > Readers, > > Trying to use alpine with tor, to send and receive mail. Alpine started: > > torsocks alpine > > Receipt of mail fails, reporting a time out error. > > Transmission of mail fails reporting the following error: > > [Mail not sent: : Client > host rejected: A] > > Correct configuration advice please Looks like the remote host is rejecting mail coming from TOR exit nodes. Nothing you can do about it apart from asking the admins to let you through. HTH, Peter G. -- "I do not think the way you think I think." -- Kai, last of the Brunnen G From carlos.e.r at opensuse.org Tue Oct 7 09:41:42 2014 From: carlos.e.r at opensuse.org (Carlos E. R.) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] tor incompatibility In-Reply-To: References: <3d5fb64957a10595b1a23e612da87d31@openmailbox.org> Message-ID: <543417C6.7060601@opensuse.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-10-07 17:29, Peter G. wrote: > Hello. > > Hodie Non. Oct. MMXIV AUC quidam/qu?dam/quoddam 'message' inquit: >> Receipt of mail fails, reporting a time out error. >> >> Transmission of mail fails reporting the following error: >> >> [Mail not sent: >> : Client host >> rejected: A] > Looks like the remote host is rejecting mail coming from TOR exit > nodes. Nothing you can do about it apart from asking the admins to > let you through. It can be they reject tor itself, or that for some reason they reject the particular IP the exit node happens to have. or that they reject any proxy. Gmail, for instance, can be difficult or even impossible with tor, but because the apparent IP you use can geographically jump "thousand of miles". They keep the location of your previous connections, and if you connect from somewhere else they think that it is not you, but somebody else, faking, and require confirmation: for instance, a code sent via sms to your phone. Of course, this breaks completely any attempt at privacy attained by using tor... - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlQ0F8MACgkQtTMYHG2NR9VxIQCfUICQXoiM2uPAz4225VXuwKL8 CqYAn3QQgQ5+pHESsMSZkV9hRVvK5YRv =ejgX -----END PGP SIGNATURE----- From porcelain_mouse at vfemail.net Wed Oct 8 21:12:21 2014 From: porcelain_mouse at vfemail.net (Porcelain Mouse) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] Account Temporarily Unavailable-->Password Deletion Message-ID: Hi All, When Alpine gives me the error message "Account Temporarily Unavailable" it immediately deletes my saved password for that (IMAP) account and I am forced to retype it. I don't know what causes this error, but I wonder if there is away to prevent this reaction. I looked in configuration, but didn't see anything obviously related. I don't think I've ever experienced this before, but I only started using .pine-passfile a few years ago, so I probably didn't notice if it did happen. But, I'm pretty sure it is particular to this IMAP server/service. Alpine actually deletes the password on file, so even if I quit Alpine and restart it, it still asks me for the password. If I give the password, it will give a different error (invalid password) and repeats the prompt. Sometimes this continues only for a few minutes, but then connects. But, this can happen repeatedly: I will take reconnect with the password I type, then when I hit TAB to go to the next folder, it can recur. It's clearly related to *something* on my providers end, but, it is also new to the service as I've used them for about a year. The first time this happened there was an upgrade that didn't go smoothly. But, obviously, I don't want Alpine to react this way when there is just any kind of server trouble. I tried contacting my provided, again, but they didn't recognize this as related to anything specific on their end. Does anyone recognize this behavior? Is "account temporarily unavailable" a standard IMAP server message? Perhaps not; seems like something you might get if you had a load balancing front end, doesn't it? It's trying to be helpful and trick your client into "simply" reconnecting if the back-end you were using goes down. So, it might not even be the IMAP server's message that is the problem. Without instrumenting my IMAP sessions, I don't know how to determine what is the problem that causes this reaction. But, approaching it from the other end, perhaps someone knows to which circumstances Alpine reacts this way? That might tell us what is happening. I suppose I could check for this message in the code, but thought I would ask the list, first. I assume this is a valid use case and Alpine is reacting appropriately, but, as you can imagine, I'd prefer a different behavior. -- PMouse From chappa at gmx.com Thu Oct 9 12:13:31 2014 From: chappa at gmx.com (Eduardo Chappa) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] Account Temporarily Unavailable-->Password Deletion In-Reply-To: References: Message-ID: On Wed, 8 Oct 2014, Porcelain Mouse wrote: > When Alpine gives me the error message "Account Temporarily Unavailable" > it immediately deletes my saved password for that (IMAP) account and I > am forced to retype it. I don't know what causes this error, but I > wonder if there is away to prevent this reaction. I looked in > configuration, but didn't see anything obviously related. Hello, Alpine 2.10 (I think) does this, but previous versions do not. Let me tell you a little bit what is going on. It will take me some time to get there, so bear with me for a little bit. There are two problems that you have. One is that the server replies to you with a message you do not expect. This is typically the case of services that go into the cloud. Out of all the services I use, only the one that uses Microsoft servers give me trouble (sometimes the password will not work, sometimes I am authenticated by not connected, etc.) I consider this normal for that server. It does not happen with other servers. I also use a password file, but this is encrypted, so I do not have the problem of having anyone steal my password file. I am quite confident that the password file is decrypted correctly every time Alpine opens, so I do not think that this code has any problem. I am quite confident that the problem is in the cloud. Whenever Alpine fails to log me in, I cancel (press ^C) when Alpine asks me to input the password and this will normally leave the password file untouched, so the password is preserved for the next session, and I will not input it again. In fact, many times, I just close Alpine and restart it, and this will cure the issue all by itself (because as I said before, the problem was not Alpine, but the authentication server in the cloud.) If you are finding that Alpine is erasing your password is because of the following confluence of two situations: * If Alpine finds a password it tries it, without asking you if it should. This is normal, that is why you have a passwrod file in the first place, and * some servers close the connection on you if you enter your password incorrectly at the first attempt to login. So, if your server falls in this category, and the login process fails for whatever reason (e.g. you changed your password through the web interface or the server failed to authenticate you, etc.) Alpine has no way of recovering, because the first attempt (which will fail) is the only attempt you will get. Once you get to the second attempt it is too late, the connection has already been closed and Alpine will not ask you for the password because there is no server to connect to, so you are in a catch 22 type of situation. The only way to get out of this is deleting the password from the password file, or more drastically, by deleting the full password file. In order to avoid the latter, the former is done, and that's why this happens. There is no way to specify that you want to delete the password if login in fails, or if you want to keep it in your password file. I hope this explains what you are seeing. -- Eduardo From superaorta at gmail.com Thu Oct 9 13:07:07 2014 From: superaorta at gmail.com (superaorta@gmail.com) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] Account Temporarily Unavailable-->Password Deletion In-Reply-To: References: Message-ID: <2162774.d5IUR5HE85@lunesta> I don't have this problem but I could not understand why the password needs to be deleted! it seems to me that the password file could simply be left untouched? > 22 type of situation. The only way to get out of this is deleting the > password from the password file, or more drastically, by deleting the full > password file. In order to avoid the latter, the former is done, and > that's why this happens. From chappa at gmx.com Thu Oct 9 13:31:46 2014 From: chappa at gmx.com (Eduardo Chappa) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] Account Temporarily Unavailable-->Password Deletion In-Reply-To: <2162774.d5IUR5HE85@lunesta> References: <2162774.d5IUR5HE85@lunesta> Message-ID: On Thu, 9 Oct 2014, superaorta@gmail.com wrote: > I don't have this problem but I could not understand why the password > needs to be deleted! it seems to me that the password file could simply > be left untouched? I just checked this, but It looks like you are using a patched version of Alpine. The clean version of Alpine does not delete passwords from the password file. So, move to the unpatched version and this will go away. -- Eduardo From carlos.e.r at opensuse.org Thu Oct 9 13:33:14 2014 From: carlos.e.r at opensuse.org (Carlos E. R.) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] Account Temporarily Unavailable-->Password Deletion In-Reply-To: <2162774.d5IUR5HE85@lunesta> References: <2162774.d5IUR5HE85@lunesta> Message-ID: <5436F10A.6050709@opensuse.org> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2014-10-09 22:07, superaorta@gmail.com wrote: > > I don't have this problem but I could not understand why the > password needs to be deleted! it seems to me that the password file > could simply be left untouched? Try mark it read only. Or inmutable. - -- Cheers / Saludos, Carlos E. R. (from 13.1 x86_64 "Bottle" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iEYEARECAAYFAlQ28QcACgkQtTMYHG2NR9VQmgCeJJn+IzUTB/g1DYN1p0O12vRm VOEAnibqun3rFI/WSDx6cQgbp48Mn+3I =0upq -----END PGP SIGNATURE----- From W.Scheinast at web.de Fri Oct 10 00:39:18 2014 From: W.Scheinast at web.de (Werner Scheinast) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] Account Temporarily Unavailable-->Password Deletion In-Reply-To: <2162774.d5IUR5HE85@lunesta> References: <2162774.d5IUR5HE85@lunesta> Message-ID: Gestern schrieb superaorta@gmail.com: > I don't have this problem but I could not understand why the password needs to > be deleted! it seems to me that the password file could simply be left > untouched? If the password in the file is wrong, you'll be caught in an endless loop. Whenever Alpine comes up, it will first try a login with the wrong pass- word, then the server will be blocked. Restarting Alpine to "renew" the IMAP connection will make the server accessible again, but repeat only the problem. Maybe Alpine can offer a "reconnect" option for remote folders, so you needn't quit and Alpine will know that the password has failed before. Or Alpine can simply ask before it deletes the possibly wrong password. Have a nice weekend Werner From klewellen at shellworld.net Tue Oct 14 13:58:15 2014 From: klewellen at shellworld.net (Karen Lewellen) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] odd alpine access error? Message-ID: Greetings list, My name is Karen lewellen, and I have a question regarding an error I experience with alpine. My nonprofit organization curtain up distribution INC.., has a hosting account with dreamhost. www.dreamhost.com As a part of our account we have shell access which I use via ssh TELNET. Included on the shell is Alpine 2.02 (1266) Which they provide since their hosting structure is rooted in ubintu. Actually the error existed when they were still using debian squeeze, but it continues after the upgrade as well. Here is what happens. Once in my inbox, I may be reading mail or writing one when I will get the following. Folder "inbox" closed due to access error. No other information is provided, and the team at dreamhost is frankly far from aware of how alpine works. In fact I joined this list at their suggestion. Any ideas about what might be causing this problem? Thanks, Karen From chappa at gmx.com Tue Oct 14 14:52:15 2014 From: chappa at gmx.com (Eduardo Chappa) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] odd alpine access error? In-Reply-To: References: Message-ID: On Tue, 14 Oct 2014, Karen Lewellen wrote: > Here is what happens. > Once in my inbox, I may be reading mail or writing one when I will get the > following. > Folder "inbox" closed due to access error. Dear Karen, I believe that the imap server that your provider uses is set to close the connection if you do not use it for a short amount of time. While the standard says that this connection can not be closed for 30 minutes, in reality, it seems that your server is closing it unilaterally. Try pressing M S C now and set up the variable Mail Check Interval = to be a small number, such as 15. The default seems to be too big for that server. -- Eduardo From klewellen at shellworld.net Tue Oct 14 18:16:34 2014 From: klewellen at shellworld.net (Karen Lewellen) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] odd alpine access error? In-Reply-To: References: Message-ID: Good evening Eduardo, Would you believe? that value was set to 150. Have changed it to 15, and will see if the error goes away. Profound thanks for providing a swift solution. Kare On Tue, 14 Oct 2014, Eduardo Chappa wrote: > On Tue, 14 Oct 2014, Karen Lewellen wrote: > >> Here is what happens. >> Once in my inbox, I may be reading mail or writing one when I will get the >> following. >> Folder "inbox" closed due to access error. > > Dear Karen, > > I believe that the imap server that your provider uses is set to close the > connection if you do not use it for a short amount of time. While the > standard says that this connection can not be closed for 30 minutes, in > reality, it seems that your server is closing it unilaterally. > > Try pressing M S C now and set up the variable > > Mail Check Interval = > > to be a small number, such as 15. The default seems to be too big for that > server. > > -- > Eduardo > > From mattack at apple.com Tue Oct 14 18:44:29 2014 From: mattack at apple.com (Matt Ackeret) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] odd alpine access error? In-Reply-To: References: Message-ID: On Tue, 14 Oct 2014, Karen Lewellen wrote: > Good evening Eduardo, > Would you believe? that value was set to 150. > Have changed it to 15, and will see if the error goes away. > Profound thanks for providing a swift solution. Also, if that for some reason doesn't work, a relatively quick way to reopen your INBOX is to type < . (or return instead of period works too) since that goes back to the list of folders, then the return/period reopens INBOX. From thomas at ifi.uio.no Fri Oct 17 06:40:52 2014 From: thomas at ifi.uio.no (Thomas Gramstad) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] Expunge without mailcheck? Message-ID: Is it possible in Alpine to x(punge) deleted messages without triggering mailcheck and filtering? I can't seem to find a config setup choice regulating this. Thomas Gramstad From beartooth at comcast.net Sun Oct 19 07:36:22 2014 From: beartooth at comcast.net (Beartooth) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] attaching contrarily Message-ID: alpine-2.11-1.fc20.x86_64 asks me, as it should when I tell it to forward with full headers, whether to forward as an attachment. I tell it no -- and it creates the attachment anyway. I cancelled sending and tried again -- three times. What is wrong?? -- Beartooth Staffwright, Not Quite Clueless Power User Remember I know little (precious little!) of where up is. From alpine-info at monkeybutt.com Thu Oct 30 17:40:59 2014 From: alpine-info at monkeybutt.com (Baron Fujimoto) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] (no subject) Message-ID: Can anyone suggest a workaround for the following problem? I'm using Alpine 2.0.3 as my MUA. Alpine is configured to use IMAP for an ISP account that Gmail provides mail (MX) services for. I have other personal domains with email addresses configured such that they forward email to this Gmail-handled ISP account. Gmail only keeps one copy of each message, as determined by its Message-ID. If Alpine is configured to save its Fcc to a Gmail IMAP folder (e.g., Gmail's standard "[Gmail]/Sent Mail"), Alpine apparently writes directly to this folder via IMAP, with only the set of message headers generated by Alpine, including Message-ID. The problem arises when the forwarded message finally gets handed off to the Gmail for delivery. Gmail sees that it already has a copy of the message based on its Message-ID, considers it a duplicate, and does not deliver it to the Inbox. If I disable Fcc by setting the Fcc folder to "", this doesn't happen since Alpine is not storing the copy directly via IMAP, but then I also don't get an archive of Sent Mail, so this is undesirable as well. Institutions outsourcing their mail services to Gmail are increasingly prevalent, so it seems unlikely I'm the only one in this situation. Or am I missing something here? From chappa at gmx.com Thu Oct 30 18:55:56 2014 From: chappa at gmx.com (Eduardo Chappa) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] (no subject) In-Reply-To: References: Message-ID: On Thu, 30 Oct 2014, Baron Fujimoto wrote: > Can anyone suggest a workaround for the following problem? The problem is called Gmail, so your solution has to pass by either convincing google to change its way (impossible) or by you changing your way (you have no other option). Unless there is a directive from someone forcing you to use Gmail for your sent-mail, I would suggest not to use Gmail for the sent-mail folder. You can always use a local folder or a random folder in an imap server not under the control of Google. -- Eduardo http://patches.freeiz.com/alpine/ From alpine-info at monkeybutt.com Thu Oct 30 19:17:11 2014 From: alpine-info at monkeybutt.com (Baron Fujimoto) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] (no subject) In-Reply-To: References: Message-ID: On Thu, 30 Oct 2014, Eduardo Chappa wrote: > On Thu, 30 Oct 2014, Baron Fujimoto wrote: > >> Can anyone suggest a workaround for the following problem? > > The problem is called Gmail, so your solution has to pass by either > convincing google to change its way (impossible) or by you changing your way > (you have no other option). Had pretty much come to that conclusion. > Unless there is a directive from someone forcing you to use Gmail for your > sent-mail, I would suggest not to use Gmail for the sent-mail folder. You can > always use a local folder or a random folder in an imap server not under the > control of Google. Urgh. Was afraid of that. Local folders pretty much defeat the purpose of IMAP, IMO. Alas, random folders under a different account/server also pretty undesirable. *sigh* But thanks for the sanity check. -baron > -- > Eduardo > http://patches.freeiz.com/alpine/ > From mbmiller+l at gmail.com Fri Oct 31 07:20:09 2014 From: mbmiller+l at gmail.com (Mike Miller) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] (no subject) In-Reply-To: References: Message-ID: I'm not sure if this helps -- I'm using gmail, too, but I don't usually use IMAP. I'm having fetchmail grab every new message from gmail every 5 mins and store it locally. I use gmail's smtp server: # List of SMTP servers for sending mail. If blank: Unix Pine uses sendmail. smtp-server=smtp.gmail.com/submit/tls/user=GMAILUSER@gmail.com (Replace "GMAILUSER" with your gmail username.) I use a local Fcc. But ... everything is on Gmail, and everything is local, too. Everything is stored in both places. Also, if I use the Gmail web interface to send a message, that message is still stored on my local machine -- fetchmail grabs those messages, too. I also can use IMAP to see the messages stored on Gmail directly: # 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=mail/[], Gmail {imap.gmail.com/novalidate-cert/user=GMAILUSER/ssl}[] So even if I deleted the local copies, I'd still have access via IMAP. I think this has been working very well for me for about 6 years now, but I do have an always-on Linux box at a university. I connect to it via SSH and run Alpine that way. Mike On Thu, 30 Oct 2014, Baron Fujimoto wrote: > Can anyone suggest a workaround for the following problem? > > I'm using Alpine 2.0.3 as my MUA. Alpine is configured to use IMAP for > an ISP account that Gmail provides mail (MX) services for. I have other > personal > domains with email addresses configured such that they forward email to > this Gmail-handled ISP account. > > Gmail only keeps one copy of each message, as determined by its Message-ID. > If Alpine is configured to save its Fcc to a Gmail IMAP folder (e.g., Gmail's > standard "[Gmail]/Sent Mail"), Alpine apparently writes directly to this > folder via IMAP, with only the set of message headers generated by Alpine, > including Message-ID. The problem arises when the forwarded message finally > gets handed off to the Gmail for delivery. Gmail sees that it already has > a copy of the message based on its Message-ID, considers it a duplicate, and > does not deliver it to the Inbox. > > If I disable Fcc by setting the Fcc folder to "", this doesn't happen since > Alpine is not storing the copy directly via IMAP, but then I also don't get > an archive of Sent Mail, so this is undesirable as well. > > Institutions outsourcing their mail services to Gmail are increasingly > prevalent, so it seems unlikely I'm the only one in this situation. Or > am I missing something here? > _______________________________________________ > Alpine-info mailing list > Alpine-info@u.washington.edu > http://mailman13.u.washington.edu/mailman/listinfo/alpine-info > From dnlbrkc at gmail.com Fri Oct 31 14:49:36 2014 From: dnlbrkc at gmail.com (Daniel B) Date: Tue Jun 12 15:14:58 2018 Subject: [Alpine-info] smtp with password authentication Message-ID: Dear all, I am trying to configure the SMTP of a mailbox in Alpine 2.0. The server of my mailbox does not support TLS authentication, only password authentication. i.e. the SMTP server requires entering the username and password. I could not find any option in alpine where I could set smtp authentication to password mode. is there such an option? I am using: smtp.domain.com/user=USERNAME/ssl to set the smtp address. Thank you for your help. Best, Daniel