similar to: Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1

Displaying 20 results from an estimated 4000 matches similar to: "Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1"

2018 Dec 31
2
Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1 (fwd)
Hi Aki, Oops; I did not think carefully enough about your instructions. Here is the output from $ dovecot -n -c /home/meuser/dotfiles/auto-stanford-dovecot.conf # 2.3.2.1 (0719df592): /home/meuser/dotfiles/auto-stanford-dovecot.conf # Pigeonhole version 0.5.2 () # OS: Linux 4.18.0-13-generic x86_64 Ubuntu 18.10 ext4 # Hostname: cpbl-t450s doveconf: Warning: please set
2018 Dec 31
2
Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1
Hi Aki, Yes, the same connect error: imap(meuser,)Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission denied The mail location in "doveconf -n" (belo) does not reflect my preferences. In Alpine, if I acknowledge the error I get, which tells me to add novalidate-cert in my pinerc file, it prompts me for my POSIX username and password. After that, I get my
2018 Dec 31
2
Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1
Hi Aki, Thanks. I put that in the .conf file I mentioned, and it made no difference. Chris > Hi! > > In your case it's probably easiest to change > > service stats { > unix_listener stats-writer { > mode = 0666 > } > } > > Aki > > > On 31 December 2018 at 16:05 cpblpublic+dovecot at gmail.com wrote: > > > > > >
2018 Dec 31
2
Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1 (fwd)
Hi Aki, I am not 100% sure. I do not really know what my OS does. "ps -A" says dovecot is running, but if I say "sudo service dovecot stop", my email client works fine still (that is, assuming the old version of dovecot is installed). ie the on-demand instances of dovecot-imapd that Alpine calls are, I assume, started and stopped by Alpine. (?) Is my OS using dovecot
2018 Dec 31
2
Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1 (fwd)
Hi Aki, Bingo! Putting that line in dovecot.conf rather than my custom file, and then using my old custom file, unchanged, from Alpine works perfectly. My only remaining question, then, would be ... what was this (change) about / or is there any documentation that I should/could have read to know what to do without asking a lead developer? Thank you very much. I hope you had a great start
2018 Dec 31
2
Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1
Hi Aki, (This message might not make it to the list; I have to switch back to the other dovecot to be able to send from that address) Oops; I did not think carefully enough about your instructions. Here is the output from $ dovecot -n -c /home/meuser/dotfiles/auto-stanford-dovecot.conf # 2.3.2.1 (0719df592): /home/meuser/dotfiles/auto-stanford-dovecot.conf # Pigeonhole version 0.5.2 () # OS:
2019 Jan 06
1
Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1
Hello Stephan, I'm interested to see this get fixed (and ideally one day for it to be really easy for people to set up Alpine so that it competes fairly with heavier GUIs!), but I do not know that I am qualified to help (beyond light testing). Is there someone from Alpine on this thread? The second (askubuntu.com) link you give is my own question (and answer, based on Aki Tuomi's
2018 Dec 31
0
Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1 (fwd)
Am I assuming correctly that you are not, in fact, running anything but imap process from Dovecot? Aki > On 31 December 2018 at 18:35 Chris BL <cpblpublic+dovecot at gmail.com> wrote: > > > > Hi Aki, > > Oops; I did not think carefully enough about your instructions. Here is the output from > > $ dovecot -n -c /home/meuser/dotfiles/auto-stanford-dovecot.conf
2018 Dec 31
0
Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1 (fwd)
If your client directly executes imap binary, it is not mandatory for dovecot to be running, but you need to put the service section into /etc/dovecot/dovecot.conf and restart the dovecot service. Putting it to your local config file does not affect the global service. Aki > On 31 December 2018 at 22:16 Chris BL <cpblpublic+dovecot at gmail.com> wrote: > > > > Hi Aki,
2018 Dec 31
0
Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1 (fwd)
We are working on fixing this. Aki > On 31 December 2018 at 23:45 Chris BL <cpblpublic+dovecot at gmail.com> wrote: > > > Hi Aki, > > Bingo! Putting that line in dovecot.conf rather than my custom file, and > then using my old custom file, unchanged, from Alpine works perfectly. > > My only remaining question, then, would be ... what was this (change) >
2018 Dec 31
0
Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1
Hi! In your case it's probably easiest to change service stats { unix_listener stats-writer { mode = 0666 } } Aki > On 31 December 2018 at 16:05 cpblpublic+dovecot at gmail.com wrote: > > > > I use a localhost dovecot imap server in order to access maildir folders from Alpine (see 2009 instructions for my set up here >
2018 Dec 31
0
Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1
You are still getting the connect error? Can you share your doveconf -n? Aki > On 31 December 2018 at 16:42 cpblpublic+dovecot at gmail.com wrote: > > > Hi Aki, > > Thanks. I put that in the .conf file I mentioned, and it made no > difference. > > Chris > > > Hi! > > > > In your case it's probably easiest to change > > > >
2018 Dec 31
0
Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1
Did you remove the service section before taking doveconf -n? 'cos I can't see it here.. Also, did you restart dovecot after config change? Aki > On 31 December 2018 at 16:54 Chris BL <cpblpublic+dovecot at gmail.com> wrote: > > > Hi Aki, > > Yes, the same connect error: imap(meuser,)Error: net_connect_unix(/var/run/dovecot/stats-writer) failed: Permission
2019 Jan 06
0
Localhost imap server fails after upgrade from 2.2.33.2-1 to 1:2.3.2.1
Op 31/12/2018 om 16:53 schreef Chris Barrington-Leigh: > I then followed the instructions in the Warning lines above and now I > get: > > ?dovecot -n -c /home/meuser/dotfiles/auto-stanford-dovecot.conf > # 2.3.2.1 (0719df592): /home/meuser/dotfiles/auto-stanford-dovecot.conf > # Pigeonhole version 0.5.2 () > # OS: Linux 4.18.0-13-generic x86_64 Ubuntu 18.10 ext4 > #
2015 Jun 15
3
Problem logging in during testing
Am Montag, den 15.06.2015, 13:33 -0400 schrieb Steve Matzura: > I think I have it now! Found info about *correctly* defining > namespaces. I now get the following when telnetting in, and it all > looks valid. > > Trying 127.0.0.1... > Connected to 127.0.0.1. > Escape character is '^]'. > * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE >
2017 Apr 04
3
Problem with Dovecot and BlackBerry
Hi all, i've got a strange behaviour with a BlackBerry Classic Phone (BBOS 10.3.2.2876) in combination with Dovecot 2.2.13 while trying to fetch mails. Before burying myself into debugging sessions, i try to get an understanding if the following is a Client- or a Server-specific error in the behaviour: CIGA8 UID FETCH 10009:10035 (UID FLAGS) (CHANGEDSINCE NOMODSEQ) CIGA8 BAD Error
2015 Jun 15
3
Problem logging in during testing
On Mon, 15 Jun 2015 17:22:13 +0200, you wrote: >> Now, when I telnet 127.0.0.1 143 and attempt to log in with the >> string: >> >> a login <any username> <any password> >> >> whether it's one in my users file or not, I get: >> >> a NO [AUTHENTICATIONFAILED] Authentication failed. >> > >Logs might give you a clue what
2019 Apr 09
2
masteruser can not select INBOX
Hello, My Dovecot Master can login but not not select INBOX ! What's wrong ? best regards Luda 1) USER can select INBOX: OK --------------------------------------------------- telnet localhost imap Trying ::1... Connected to localhost. Escape character is '^]'. * OK [CAPABILITY IMAP4rev1 LITERAL+ SASL-IR LOGIN-REFERRALS ID ENABLE IDLE STARTTLS AUTH=CRAM-MD5 AUTH=DIGEST-MD5
2014 Jan 07
1
Assertion failed with imapc after upgrading Dovecot from 2.1.7 to 2.2.9
Hi ! I have an old Courier IMAP and in front of it, I have put a proxy cache with Dovecot/imapc. I use Debian Wheezy (stable) which package Dovecot in version 2.1.7. I have tested the upgrade to Debian Jessie (testing) which package Dovecot in version 2.2.9 but an assertion is thrown : dovecot: imap(xxx): Panic: file imapc-list.c: line 499 (imapc_list_delete_unused_indexes): assertion failed:
2017 Feb 18
2
Issue connecting to dovecot from remote machine
Hi, I've set up a postfix +dovecot configuration on my debian jessie. But I have a connection issue. When I try to connect from thunderbird it doesn not work. When I check out my debug logs I get : auth-worker(22252): Info: pam(myuser,hostIP): pam_authenticate() failed: Authentication failure (password mismatch?) (given password: correctPassword) Running doveadm auth test tells me I can