similar to: can't login to Dovecot

I've managed to turn on "plain" and now it seems I can logon. Jun 13 17:24:20 ulmke2 dovecot[1973]: imap(ulw)<2474><+kyqk4du5M7AqGQd>: Namespace '': Mail storage autodetection failed with home=/u/ulw in=0 out=373 deleted=0 expunged=0 trashed=0 hdr_count=0 hdr_bytes=0 body_count=0 body_bytes=0 Jun 13 17:24:20 ulmke2 dovecot[1973]: imap-login: Login:

On 2018-06-13 00:09, Joseph Tam wrote: > On Tue, 12 Jun 2018, Walter Ulmke wrote: > >> ... and just want to login using the standard Linux login > > Depends on what you which "standard" you mean but I'll just assume > you're using PAM, as suggested by your config. > >> auth_mechanisms = plain login digest-md5 cram-md5 ntlm rpa apop >>

On 2018-06-14 07:06, Steffen Kaiser wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Thu, 14 Jun 2018, Walter Ulmke wrote: > >> 1) my inbox is "Posteingang". should I officially declare it >> somewhere? >> >> I now get the following error messages: >> >> Jun 14 00:23:32 ulmke2 dovecot[3981]: >>

1) my inbox is "Posteingang". should I officially declare it somewhere? I now get the following error messages: Jun 14 00:23:32 ulmke2 dovecot[3981]: imap(ulw)<3997><4O/Xbo1uotLAqGQd>: Error: opendir(/u/ulw/Mail) failed: Permission denied (euid=503(ulw) egid=100(users) UNIX perms appear ok (ACL/MAC wrong?)) Jun 14 00:23:32 ulmke2 dovecot[3981]:

solved. It was doen to not being able to log in in "plain" -- -- Best Regards, Walter Ulmke Ulmke Machine Tools, 48496 Hopsten, Germany Tel. ++49/5458/93345-0 Fax. ++49/5458/93345-45 Mobile: ++49/172/5357999 eMail: ulw at ulmke.com Dipl.-Ing. Walter Ulmke e.K. AG Steinfurt HRA 4384

On 2018-06-12 13:14, Steffen Kaiser wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tue, 12 Jun 2018, Walter Ulmke wrote: > >> un 12 12:30:06 ulmke2 dovecot[5814]: auth: Fatal: APOP mechanism can't >> be supported with given passdbs > > Config error. > > "Fatal" sounds fatal ;-) > >> stats: open(old-stats-user)

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 12 Jun 2018, Walter Ulmke wrote: > Date: Tue, 12 Jun 2018 14:23:30 +0200 > From: Walter Ulmke <ulw at ulmke.com> > To: dovecot at dovecot.org > Subject: Re: cant login to Dovecot > > On 2018-06-12 13:14, Steffen Kaiser wrote: >> -----BEGIN PGP SIGNED MESSAGE----- >> Hash: SHA1 >> >> On Tue, 12

On 2018-06-12 15:18, Steffen Kaiser wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On Tue, 12 Jun 2018, Walter Ulmke wrote: > >> Date: Tue, 12 Jun 2018 14:23:30 +0200 >> From: Walter Ulmke <ulw at ulmke.com> >> To: dovecot at dovecot.org >> Subject: Re: cant login to Dovecot >> >> On 2018-06-12 13:14, Steffen Kaiser wrote:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Thu, 14 Jun 2018, Walter Ulmke wrote: > 1) my inbox is "Posteingang". should I officially declare it somewhere? > > I now get the following error messages: > > Jun 14 00:23:32 ulmke2 dovecot[3981]: imap(ulw)<3997><4O/Xbo1uotLAqGQd>: > Error: opendir(/u/ulw/Mail) failed: Permission denied (euid=503(ulw)

Hi all, I can't login. This is a dovecot server for a small inhouse network, and I doon't use any encryption, and just want to login using the standard Linux login dovecot status gives me the following error messages: un 12 12:30:06 ulmke2 dovecot[5814]: auth: Fatal: APOP mechanism can't be supported with given passdbs Jun 12 12:30:06 ulmke2 dovecot[5811]: master: Error:

On 28.05.2014 15:27, Laine Stump wrote: > On 05/27/2014 09:07 AM, Jianwei Hu wrote: >> Hi All, >> >> I have one netcf question, please help me to resolve it, thanks. >> >> I can set a IFF_RUNNING flag to a bridge device which are no interface device attached. What status of a flag on a bridge device in current kernel?(w/o interface), is this a new change in kernel

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Tue, 12 Jun 2018, Walter Ulmke wrote: > un 12 12:30:06 ulmke2 dovecot[5814]: auth: Fatal: APOP mechanism can't be > supported with given passdbs Config error. "Fatal" sounds fatal ;-) > stats: open(old-stats-user) failed: Permission denied Likewise config error, but not fatal. Post your config - -- Steffen Kaiser

On Tue, 12 Jun 2018, Walter Ulmke wrote: > ... and just want to login using the standard Linux login Depends on what you which "standard" you mean but I'll just assume you're using PAM, as suggested by your config. > auth_mechanisms = plain login digest-md5 cram-md5 ntlm rpa apop anonymous Looks like you did a kitchen sink configuration in hopes something will work, but

Hi, while testing racoon on Linux (based on the ported ipsec-tools) the following issue appeared: Racoon did not verify the RSA Signatures during Phase 1 in either main or aggressive mode. Authentication was possible using a correct certificate and a wrong private key. I have verified the below problem using racoon-20030711 on FreeBSD 4.9. I will test it using the SNAP Kit but suspect it to be

virt-builder-repository allows users to easily create or update a virt-builder source repository out of disk images. The tool can be run in either interactive or automated mode. --- .gitignore | 3 + builder/Makefile.am | 84 +++++- builder/repository_main.ml | 570 ++++++++++++++++++++++++++++++++++++ builder/test-docs.sh | 2

virt-builder-repository allows users to easily create or update a virt-builder source repository out of disk images. The tool can be run in either interactive or automated mode. --- .gitignore | 3 + builder/Makefile.am | 84 +++++- builder/repository_main.ml | 584 ++++++++++++++++++++++++++++++++++++ builder/test-docs.sh | 2

virt-builder-repository allows users to easily create or update a virt-builder source repository out of disk images. The tool can be run in either interactive or automated mode. --- .gitignore | 3 + builder/Makefile.am | 85 +++++- builder/repository_main.ml | 589 ++++++++++++++++++++++++++++++++++++ builder/test-docs.sh | 2

virt-builder-repository allows users to easily create or update a virt-builder source repository out of disk images. The tool can be run in either interactive or automated mode. --- .gitignore | 3 + builder/Makefile.am | 86 +++++- builder/repository_main.ml | 597 ++++++++++++++++++++++++++++++++++++ builder/test-docs.sh | 2

virt-builder-repository allows users to easily create or update a virt-builder source repository out of disk images. The tool can be run in either interactive or automated mode. --- .gitignore | 3 + builder/Makefile.am | 89 +++++- builder/repository_main.ml | 590 ++++++++++++++++++++++++++++++++++++ builder/test-docs.sh | 2

Hello! I have a very minor bug to report. The ssl_options configuration directive takes a space-separated list of options, each of which must be in the set {?no_compression?, ?no_ticket?}, according to the 2.2.25 source code. However, the file doc/example-config/conf.d/10-ssl.conf shipped in the tarball only mentions the ?no_compression? option; it makes no mention of the ?no_ticket? option. Oh,