> On 31/07/2020 11:56 janvv wrote:
>
>
> So happy I found this discussion.
> I spent a day on figuring out an issue with login into IMAP.
> It turned out that the { character in my password was the problem. Grrr...
>
> The strange thing that I could successfully configure my IMAP connection
So happy I found this discussion.
I spent a day on figuring out an issue with login into IMAP.
It turned out that the { character in my password was the problem. Grrr...
The strange thing that I could successfully configure my IMAP connection my
Outlook client. Only when I try to connect
On Apr 10, 2015, at 12:14 AM, Steffen Kaiser skdove...@smail.inf.fh-brs.de
wrote:
password
is no atom and Dovecot should reject it.
No, not passwords should be rejected.
Maybe the former version did not checked the atoms 100% RFC conform.
Where is the definition that passwords have to be
-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
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
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
