Configuration is not working with Thunderbird

[Quark]

I did all this & it still gives the same error.  I have connected with 
my android phone with no security with my current setup, however I still 
get the same error message from Dovecot.

May 22 08:54:30 ********** dovecot: imap-login: Aborted login (no auth 
,attempts in 0 secs): user=<>, rip=***********, lip=***********, 
,session=<***********>

I've tried to do all sorts of changes in the way that I attempt to login 
via Thunderbird & it gives me the same error.

Any suggestion on how to get Thunderbird to login?

On 05/22/2017 09:26 AM, Aki Tuomi wrote:
>> On May 22, 2017 at 4:03 PM Quark <zquark32 at gmail.com> wrote:
>>
>>
>> So, I have this error now:
>>
>> May 22 08:54:30 ********** dovecot: imap-login: Aborted login (no auth
>> attempts in 0 secs): user=<>, rip=***********, lip=***********,
>> session=<***********>
>>
>> I found this:  https://wiki2.dovecot.org/WhyDoesItNotWork
>>
>> I have this set in my dovecot.conf: disable_plaintext_auth=yes
>>
> Do you have auth_mechanisms set? That seems to indicate that the client wasn't happy about the provided authentication options, or you forgot to use STARTTLS with port 143.
>
> Try setting auth_mechanisms = plain login and see if it helps.
>
> Aki
>
>> Same error, even when I try to connect port 143 instead of ssl (993).
>> Any suggestions on what I can do now?
>>
>> On 05/22/2017 02:00 AM, Aki Tuomi wrote:
>>> On 21.05.2017 20:48, Quark wrote:
>>>> Hi, I'm new to the list (and postfix / dovecot), so if I mistakenly
>>>> omit something, then please forgive me.
>>>>
>>>> I cannot log into Thunderbird via IMAP with my configuration. However,
>>>> I can check the mail of each user by logging into their user account &
>>>> then using the "mail" command.  Is there something that is wrong with
>>>> my config to not allow me to log into Thunderbird (Version 52.1.1)?
>>>> I'm using Postfix 3.1.0 if that helps.  Any help would be greatly
>>>> appreciated.  Thanks!
>>>>
>>> Please turn on
>>>
>>> auth_debug=yes
>>>
>>> and inspect your logs, such as /var/log/syslog or similar, and see what
>>> you can find or alternatively post them to list (not the whole log file,
>>> mind).
>>>
>>> Aki