similar to: IMAP preauth and stats-writer

Displaying 20 results from an estimated 5000 matches similar to: "IMAP preauth and stats-writer"

2019 Jan 06
2
IMAP preauth and stats-writer
On 06/01/2019 02:26, John Fawcett wrote: > On 05/01/2019 15:49, Mark Hills wrote: >> I use IMAP preauth; I connect with Alpine over SSH which is very useful. >> >> The last few upgrades this has become more difficult to to. Last time >> (moving 2.2 -> 2.3, I think) I had to put in a workaround: >> >> stats_writer_socket_path = >> >> It
2019 Jan 06
3
IMAP preauth and stats-writer
On 06/01/2019 11:37, Stephan Bosch wrote: > > Op 06/01/2019 om 03:35 schreef John Fawcett: >> On 06/01/2019 02:26, John Fawcett wrote: >> >>> Can't see anything in the Dovecot 2.3.4 code that would give this >>> problem, setting >>> >>> stats_writer_socket_path = >>> >>> will overwrite the default value and dovecot does
2019 Jan 06
0
IMAP preauth and stats-writer
On 05/01/2019 15:49, Mark Hills wrote: > I use IMAP preauth; I connect with Alpine over SSH which is very useful. > > The last few upgrades this has become more difficult to to. Last time > (moving 2.2 -> 2.3, I think) I had to put in a workaround: > > stats_writer_socket_path = > > It prevented /usr/local/libexec/dovecot/imap attempting to > connect to a central
2019 Jan 06
2
IMAP preauth and stats-writer
I'm the FreeBSD port maintainer for dovecot and I just added this patch to the port in SVN. 489515. On Sun, Jan 6, 2019 at 11:39 AM Stephan Bosch <stephan at rename-it.nl> wrote: > > Op 06/01/2019 om 18:12 schreef John Fawcett: > > On 06/01/2019 11:37, Stephan Bosch wrote: > >> Op 06/01/2019 om 03:35 schreef John Fawcett: > >>> On 06/01/2019 02:26, John
2019 Jan 06
0
IMAP preauth and stats-writer
Op 06/01/2019 om 18:12 schreef John Fawcett: > On 06/01/2019 11:37, Stephan Bosch wrote: >> Op 06/01/2019 om 03:35 schreef John Fawcett: >>> On 06/01/2019 02:26, John Fawcett wrote: >>> >>>> Can't see anything in the Dovecot 2.3.4 code that would give this >>>> problem, setting >>>> >>>> stats_writer_socket_path =
2019 Jan 06
0
IMAP preauth and stats-writer
and stupid me missed a character, the full fix is in SVN r489516. On Sun, Jan 6, 2019 at 11:47 AM Larry Rosenman <larryrtx at gmail.com> wrote: > I'm the FreeBSD port maintainer for dovecot and I just added this patch to > the port in SVN. 489515. > > On Sun, Jan 6, 2019 at 11:39 AM Stephan Bosch <stephan at rename-it.nl> > wrote: > >> >> Op
2019 Jan 06
0
IMAP preauth and stats-writer
Op 06/01/2019 om 03:35 schreef John Fawcett: > On 06/01/2019 02:26, John Fawcett wrote: > >> Can't see anything in the Dovecot 2.3.4 code that would give this >> problem, setting >> >> stats_writer_socket_path = >> >> will overwrite the default value and dovecot does not attempt to open a socket in that case. >> >> Using your configuration
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
I use a localhost dovecot imap server in order to access maildir folders from Alpine (see 2009 instructions for my set up here https://cpbl.wordpress.com/2009/11/07/alpine-offlineimap-and-gmail-under-ubuntu/ ) My configuration has worked nicely since 2009, but failed after a recent upgrade of dovecot (during basic upgrade from Ubuntu 18.04 to 18.10). The version of Alpine did not change.
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 (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 (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
2015 May 04
2
fatal: ssh_dispatch_run_fatal: Connection reset by peer [preauth]
Hello everybody, I have systemd set up to listen on ssh socket (:::22), the connection is handled to sshd via socket activation. Usually this works perfectly fine. However the service is checked from nagios. Sometimes the host logs: systemd[1]: Started OpenSSH Per-Connection Daemon ([::1]:60865). systemd[1]: Starting OpenSSH Per-Connection Daemon ([::1]:60865)... systemd[1]: Started OpenSSH
2018 Jan 03
2
Dovecot 2.3 - using doveadm as non-root?
Hi dovecot developers and users, I recently upgraded my server running Arch Linux to dovecot 2.3.0, and I noticed some of my cron jobs started issuing me error messages. These cron jobs run as a non-root user associated with my mail account, and they use doveadm to tidy things up (ex. purging the trash, moving old mail in certain folders into the trash). The error message is: > Error:
2012 Nov 01
2
"starting" dovecot
My system never issues the "dovecot start" command. I do, however, run /usr/local/libexec/dovecot/imap on port 9xxx. I talk to the server through port 9xxx and through the preauth tunnel. Is this arrangement OK? Are there some things that will only work if "dovecot" is invoked? Thanks, -- Dave Abrahams BoostPro Computing Software Development
2011 Jun 02
2
preauth privsep logging via monitor
Hi, This diff (for portable) makes the chrooted preauth privsep process log via the monitor using a shared socketpair. It removes the need for /dev/log inside /var/empty and makes mandatory sandboxing of the privsep child easier down the road (no more socket() syscall required). Please test. -d Index: log.c =================================================================== RCS file:
2013 Jul 30
1
fatal: cipher_init: EVP_CipherInit: set key failed for aes128-cbc [preauth]
Am I the only person to be seeing this log message from sshd: fatal: cipher_init: EVP_CipherInit: set key failed for aes128-cbc [preauth] ? (security/openssh-portable, with HPN patches and MIT Kerberos, although Kerberos is not actually configured on this server.) A work-around is to disable aes128-cbc in sshd_config, but it would be nice not to have my logs spammed with this. Currently