I spent days on this problem. I have dovecot setup to use SSL and IMAP. I also have a pop account that I had no trouble getting working. Both use PAM authentication on Linux. openssl s_client -connect localhost:993 a login test_user test_secure_password The response I got back was: a BAD Invalid characters in atom I changed the password to "abc" and it worked. The secure password used to work but it was a different architecture (x86_64 I think). The current architecture is armhf. It may be different versions of the software too. Dovecot v2.1.7
It is not architecture related, my phone uses the same account and it used to work. It is either IMAP or Dovecot. On 04/09/2015 12:35 AM, James wrote:> > I spent days on this problem. > I have dovecot setup to use SSL and IMAP. > I also have a pop account that I had no trouble getting working. > Both use PAM authentication on Linux. > openssl s_client -connect localhost:993 > a login test_user test_secure_password > The response I got back was: > a BAD Invalid characters in atom > > I changed the password to "abc" and it worked. > > The secure password used to work but it was a different architecture > (x86_64 I think). > The current architecture is armhf. > It may be different versions of the software too. > > Dovecot v2.1.7 >
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 9 Apr 2015, James wrote:> Both use PAM authentication on Linux. > openssl s_client -connect localhost:993 > a login test_user test_secure_password > The response I got back was: > a BAD Invalid characters in atomDoes your password contain the " quote? If not, enclose the password in "". Or try the literal form: 1 login user {##} password where ## is the number of octets of password> The secure password used to work but it was a different architecture (x86_64 > I think). > The current architecture is armhf.architecture of the server or client? Maybe you need to re-create the password store? - -- Steffen Kaiser -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEVAwUBVSYeynz1H7kL/d9rAQIsqwgAgVzzXjZj1hAO22hoamDM0mPJovqnNlIF YQ9/pR421GOca8YOebh9YHqqMbxuj8DFADS06EAdcKQdyONKd0CsxtHsjqIrV/FB uxEMY/MFdTto9ToMjj33YtQFz0MjACvrqO/hzepgCK3Pgt3HK0UHyN36qYmwnpNs Vzbm/YYb+4xnciYq2sLlAKvrvIn+LQT25OP7toGiXnOkGQSTbwxRtysmLe+f3Cvv XlnYTZsKTIuwAJNcDphKpd0LSts5k6Fua4pw1LtxP42W63xE5iq3KTqGdi4u6nQS jVRdKwAKVjihbbLFN1K1nlVyEEQP2dpEk4B+smRwGQTaxRrDFlki8A==L7CD -----END PGP SIGNATURE-----
I took the " out of the password and it works. The other install worked with the " in the password. On 04/09/2015 02:40 AM, Steffen Kaiser wrote:> -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thu, 9 Apr 2015, James wrote: > >> Both use PAM authentication on Linux. >> openssl s_client -connect localhost:993 >> a login test_user test_secure_password >> The response I got back was: >> a BAD Invalid characters in atom > > Does your password contain the " quote? If not, enclose the password > in "". Or try the literal form: > > 1 login user {##} > password > > where ## is the number of octets of password > >> The secure password used to work but it was a different architecture >> (x86_64 I think). >> The current architecture is armhf. > > architecture of the server or client? > Maybe you need to re-create the password store? > > - -- Steffen Kaiser > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > > iQEVAwUBVSYeynz1H7kL/d9rAQIsqwgAgVzzXjZj1hAO22hoamDM0mPJovqnNlIF > YQ9/pR421GOca8YOebh9YHqqMbxuj8DFADS06EAdcKQdyONKd0CsxtHsjqIrV/FB > uxEMY/MFdTto9ToMjj33YtQFz0MjACvrqO/hzepgCK3Pgt3HK0UHyN36qYmwnpNs > Vzbm/YYb+4xnciYq2sLlAKvrvIn+LQT25OP7toGiXnOkGQSTbwxRtysmLe+f3Cvv > XlnYTZsKTIuwAJNcDphKpd0LSts5k6Fua4pw1LtxP42W63xE5iq3KTqGdi4u6nQS > jVRdKwAKVjihbbLFN1K1nlVyEEQP2dpEk4B+smRwGQTaxRrDFlki8A=> =L7CD > -----END PGP SIGNATURE----- >