similar to: cant 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:

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]:

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:

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)

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]: >>

-----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)

-----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

-----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

I have now deleted EVERYTHING and installed fresh. Now at least it starts doveconf -n: managesieve_notify_capability = mailto managesieve_sieve_capability = fileinto reject envelope encoded-character vacation subaddress comparator-i;ascii-numeric relational regex imap4flags copy include variables body enotify environment mailbox date index ihave duplicate mime foreverypart extracttext

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 Tue, Jan 05, 2016 at 11:48:32PM +0100, Torkil Svensgaard wrote: > Hi > > I have a bunch of FreeNAS servers and a TrueNAS HA server all > spamming the logs with these messages every minute about their own > source name (examples below). > > These boxes are on two physically separate networks, and I find it > unlikely both networks should have some sort of undetected

Hi I have a bunch of FreeNAS servers and a TrueNAS HA server all spamming the logs with these messages every minute about their own source name (examples below). These boxes are on two physically separate networks, and I find it unlikely both networks should have some sort of undetected loop. Any ideas on how to debug this? Samba version is 4.1.18. FreeNAS box on network A " Jan 5

I have set up a secondary IP address in the same network as my primary. So eth0: 192.168.100.29 netmask 255.255.255.0 eth0:0 192.168.100.45 netmask 255.255.255.0 And indeed when I invoke an apache instance that listens on the secondary IP address/interface it works, and it also makes it outside the LAN since the default gateway is defined in the routing tables for 192.168.100.0/24. But

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

On 01/06/2016 01:23 AM, Jeremy Allison wrote: >> Jan 5 23:17:32 storage4 nmbd[34068]: [2016/01/05 23:17:32.086480, >> 0] ../source3/nmbd/nmbd_packets.c:1174(process_lanman_packet) >> Jan 5 23:17:32 storage4 nmbd[34068]: process_lanman_packet: >> Discarding datagram from IP 172.21.140.17. Source name STORAGE4<00> >> is one of our names ! >> " >