From Newsgroup: comp.mail.pine

On Sun, 7 Aug 2022, David wrote:

Blind Users Locked out of gmail.com going to gmx.com but pinerc doesn't work.

That's because Gmail and Gmx do different things. Gmail enforces that the
From field be the one that they configure and if you set it up incorrectly they modify it to what they think it should be, while Gmx checks that the
From field be the one that is supposed to be and does not send the message
if it is not what it should be.

The easiest way to solve this issue (for this person) is to edit the customized-hdrs field and set it up as

customized-hdrs=Personal Name <address@gmx.com>
--
Eduardo
https://alpineapp.email (web)
http://repo.or.cz/alpine.git (Git)
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.mail.pine

Still Have Sending Mail Problems

Hello Eduardo,

I'm trying to help some of the Slint mailing list users who are blind
who absolutely LOVE Alpine but find it impossible to configure with
the fairly recent changes, both in Alpine and with their new accounts
with gmx.com after gmail.com changed their policies and required
"application specific passwords" - many of the gmail users could not
set those up because they do not know how to use the graphical user
interface .

I've gotten them to use mutt which is easier to configure but they
want Alpine, but alpine is very difficult now to configure and use
especially if you have a computer generated "Application Specific
Password" - incidentally the same Application Specific Password that
we generated for mutt works for alpine.

I am running Slackware 15, variant SLINT for blind and International Users.

I made a new user and home directory for one of the person's I am
trying to help. His name is jim so I added user jim to my system.

He gave me his gmx password and user name.

I can receive his email but I cannot send any messages.

Using my account on the same computer, I can send with alpine using my
dot pinerc file and a bash_alias entry that is:
alias alpine='alpine -passfile ~.pinepass'

I copied my .pinerc file to my friends folder ~/jim and I changed the
account names to his account, and my name to his name and I changed to
file ownership to jim:users.

At the beginning of his file I put these lines:
personal-name="Jim Lastname"
customized-hdrs="Jim Lastname"<emailaddress@gmx.com>


When I try to send mail with alpine it still gives me errors.
Mail Not Sent: Bad Sequence of Commands.

I get these commands when I directly lot into Jim's account on my
computer, or when I start a MATE GUI by logging in as jim and then
using startx.

I have used vimdiff to compare my dot pinerc file and Jim's .pinerc
file in his /home/jim folder and except for his email and name beng
different they're identical.

I've deleted the .alpine-smime folder in Jim's home folder, and I
still get the above error.

What else must I do?

I've worked several days on this, I wish there was a command NOT to
put all the security additions in Alpine like a master password and
the need for a .bash_alias command like I have for Jim's alpine which
is alias alpine='alpine -passfile /home/jim/.pinepass'

The procedure for removing the master password from alpine can be
confusing especially for blind users.

I can't understand why I'm getting this error.

Regards,

David
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.mail.pine

On Wed, 10 Aug 2022, djringjr wrote:

Using my account on the same computer, I can send with alpine using my
dot pinerc file and a bash_alias entry that is:
alias alpine='alpine -passfile ~.pinepass'

I imagine that this means ~/.pinepass, right? (add "/" after "~").

I copied my .pinerc file to my friends folder ~/jim and I changed the
account names to his account, and my name to his name and I changed to
file ownership to jim:users.

At the beginning of his file I put these lines:
personal-name="Jim Lastname"
customized-hdrs="Jim Lastname"<emailaddress@gmx.com>

I imagine there is a space between "Jim Lastname" and
<emailaddress@gmx.com>, and also it should say From: to indicate the name
of the header. Please try:

customized-hdrss=From: "Jim Lastname" <emailaddress@gmx.com>

When I try to send mail with alpine it still gives me errors. Mail Not
Sent: Bad Sequence of Commands.

Yes, without the correct From header you should get this error.

What else must I do?

I believe the problem is the configuration of the From: header.

I've worked several days on this, I wish there was a command NOT to
put all the security additions in Alpine like a master password and
the need for a .bash_alias command like I have for Jim's alpine which
is alias alpine='alpine -passfile /home/jim/.pinepass'

I realize that not everyone likes the master password, but it can be
removed, also you do not need to alias Alpine if you use the password file that was compiled into Alpine. To see the name of the password file that
was compiled into alpine run alpine with the command

alpine -v

and then see what it says under --with-passfile, an if it says .pinepass,
then starting alpine with the command "alpine -passfile ~/.pinepass" is
the same as starting alpine with the command "alpine" and you do not need
to alias Alpine.

I hope this helps.
--
Eduardo
https://alpineapp.email (web)
http://repo.or.cz/alpine.git (Git)
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.mail.pine

Hello Eduardo,

Unfortunately, I am getting the same error.

Alpine 2.25 (LNX 592 2021-09-18) built Mon Sep 20 21:07:05 CDT 2021 on z-mp.slackware.lan
Alpine was built with the following options:
CFLAGS=-O2 -fPIC
./configure --prefix=/usr --mandir=/usr/man --with-ssl-dir=/usr \
--with-ssl-certs-dir=/etc/ssl/certs --with-c-client-target=slx \
--with-system-pinerc=/etc/pine.conf \
--with-system-fixed-pinerc=/etc/pine.conf.fixed \
--with-passfile=.alpine.passfile --disable-debug --with-debug-level=0 \
--without-tcl --program-prefix= --program-suffix= \
--build=x86_64-slackware-linux build_alias=x86_64-slackware-linux

I deleted the bashrc entries and the .bash_aliases entries for alpine,
now alpine just runs alpine without any additional switches.

Alpine correctly asked me for a Master Password, and I made up one and
it worked.

But when I send mail I get this error message.

[Mail not sent: Bad sequence of commands]

I am so frustrated because when I log into my account on the same
computer, I can send email from alpine using my gmx.com account.

I'm going to send you the .pinerc file off list. If you wish, I will
send you the password because there's nothing of secret importance in
Jim's email account.

Just for the list here's the important entries in Jim's .pinerc file.
I am using a separate user account in Slint Slackware 15. The pinerc
file is located in /homejim/.pinerc and I'm sending it off list in
full.

Here's parts of it. Remember, even though I'm not blind, I am
visually handicapped.

# Overrides your full name from Unix password file. Required for PC-Alpine. personal-name="Jim LastName"
customized-hdrs=From: "Jim LastName" <emailaddress@gmx.com>

You had written customized-hdrss=From: "Jim Lastname"
<emailaddress@gmx.com> I tried it that way even though I believe it
was a typo error. That didn't work either!

I have run vimdiff on the two files and they are identical except for
the email name and address.

I really want to get Alpine working for Jim because he prefers it much
more than mutt which he does have working.

There are others on the Slint email list who are having problems with
Alpine, but with the new information on how to find the name of the
password file, things will improve. I tell them to use their name
with all lower case like my master alpine password is davidring fast
enough to type and remember.

Best regards,

David


On Wednesday, August 10, 2022 at 10:37:21 PM UTC-4, Eduardo Chappa wrote:

On Wed, 10 Aug 2022, djringjr wrote:

What else must I do?

I believe the problem is the configuration of the From: header.

alpine -v

and then see what it says under --with-passfile, an if it says .pinepass, then starting alpine with the command "alpine -passfile ~/.pinepass" is
the same as starting alpine with the command "alpine" and you do not need
to alias Alpine.

I hope this helps.
--
Eduardo
https://alpineapp.email (web)
http://repo.or.cz/alpine.git (Git)

--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.mail.pine

On Wed, 10 Aug 2022, djringjr wrote:

I'm going to send you the .pinerc file off list. If you wish, I will
send you the password because there's nothing of secret importance in
Jim's email account.

For those that want to understand the problem here, the issue was
that the .pinerc file was edited by hand and the line for customized-hdrs
was added to the .pinerc file around the beginning of the file without deleting the other customized-hdrs line in the file. This made Alpine use
the second appearance of this line as the configuration for this variable, that is, it made alpine disregard the correct configuration around the top
of the document.

While many times I recommend to add to the .pinerc file an option, value,
etc. by hand, please consider doing it through a configuration screen to
avoid problems like the one that happened here.
--
Eduardo
https://alpineapp.email (web)
http://repo.or.cz/alpine.git (Git)
--- Synchronet 3.21d-Linux NewsLink 1.2

From Newsgroup: comp.mail.pine

On 2022-08-12 05:12, Eduardo Chappa wrote:

On Wed, 10 Aug 2022, djringjr wrote:

I'm going to send you the .pinerc file off list.-a If you wish, I will
send you the password because there's nothing of secret importance in
Jim's email account.

For those that want to understand the problem here, the issue was that
the .pinerc file was edited by hand and the line for customized-hdrs was added to the .pinerc file around the beginning of the file without
deleting the other customized-hdrs line in the file. This made Alpine
use the second appearance of this line as the configuration for this variable, that is, it made alpine disregard the correct configuration
around the top of the document.

While many times I recommend to add to the .pinerc file an option,
value, etc. by hand, please consider doing it through a configuration
screen to avoid problems like the one that happened here.

Idea:

Some programs (for instance, postfix) have an option to dump on screen
the actual configuration it uses.
--
Cheers, Carlos.
--- Synchronet 3.21d-Linux NewsLink 1.2