similar to: Winbind not listing users/groups

Displaying 20 results from an estimated 3000 matches similar to: "Winbind not listing users/groups"

2004 Jan 13
0
Daemon error
Hi, I have configured Samba on a Solaris 9 machine. I intend to use shared directories on the Solaris machine from Windows 95,98,2000, XP machines on the windows 2000 network. The samba daemon smbd will not start and returns an error 'bind failed on port 139 socket_addr = 0.0.0.0. Error = Address already in use'. I have searched for use of this address and no other process is using the
2004 Jan 15
0
FW: Daemon error
Hi, I have configured Samba on a Solaris 9 machine. I intend to use shared directories on the Solaris machine from Windows 95,98,2000, XP machines on the windows 2000 network. The samba daemon smbd will not start and returns an error 'bind failed on port 139 socket_addr = 0.0.0.0. Error = Address already in use'. I have searched for use of this address and no other process is using the
2020 Oct 19
0
Unable to access mail via Outlook
Bump! On Fri, 16 Oct 2020 at 13:26, Odhiambo Washington <odhiambo at gmail.com> wrote: > > > On Fri, 16 Oct 2020 at 13:15, Aki Tuomi <aki.tuomi at open-xchange.com> > wrote: > >> >> > On 16/10/2020 13:11 Odhiambo Washington <odhiambo at gmail.com> wrote: >> > >> > >> > >> > >> > >> > On Fri, 16
2020 Oct 19
0
Unable to access mail via Outlook
On Mon, 19 Oct 2020 at 09:27, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > On 19/10/2020 09:16 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > Bump! > > > > > > On Fri, 16 Oct 2020 at 13:26, Odhiambo Washington <odhiambo at gmail.com> > wrote: > > > > > > > > > > > > On
2019 Apr 11
0
Mail account brute force / harassment
All your approaches are not well thought out. The best solutions are always the simplest ones. KISS principle dictates so. On Thu, 11 Apr 2019 at 15:01, Marc Roos <M.Roos at f1-outsourcing.eu> wrote: > > How long have we been using the current strategy? Do we have less or > more abuse clouds operating? > > "Let the others bother with their own problems." is a bit
2020 Oct 16
2
Unable to access mail via Outlook
On Fri, 16 Oct 2020 at 13:15, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > On 16/10/2020 13:11 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > > > > > > > On Fri, 16 Oct 2020 at 08:19, Aki Tuomi <aki.tuomi at open-xchange.com> > wrote: > > > > On 15/10/2020 18:14 Odhiambo Washington <odhiambo
2018 Mar 29
0
Release 2.3.1
On 29 March 2018 at 13:26, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > On 29.03.2018 13:14, Odhiambo Washington wrote: > > > > On 29 March 2018 at 13:04, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > >> >> >> On 29.03.2018 10:36, Odhiambo Washington wrote: >> >> >> >> On 29 March 2018 at 09:43, Aki Tuomi
2020 Oct 16
2
Unable to access mail via Outlook
On Fri, 16 Oct 2020 at 08:19, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > On 15/10/2020 18:14 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > Here is what I see on the error.log: > > > > Oct 15 17:37:58 imap(technical at mydomain.name)<62260><9ucgmLax7s3F6FH2>: > Error: Mailbox INBOX: Cache /var/spool/virtual/
2019 Feb 05
0
Release notify (2.2.36.1 and 2.3.4.1)
Bueno. I don't even remember well. Wasn't that issue about mysql-8.0.12 to 8.0.13?? On Tue, 5 Feb 2019 at 23:46, Larry Rosenman <larryrtx at gmail.com> wrote: > 2.3.4 had the same compile issues.... > > > On Tue, Feb 5, 2019 at 2:44 PM Odhiambo Washington <odhiambo at gmail.com> > wrote: > >> Noted. >> >> I will wait for dovecot-2.3.4.2
2020 Oct 19
1
Unable to access mail via Outlook
> On 19/10/2020 09:48 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > On Mon, 19 Oct 2020 at 09:27, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > > > On 19/10/2020 09:16 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > > > > Bump! > > > > > > >
2018 Mar 29
0
Release 2.3.1
On 29 March 2018 at 13:04, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > > > On 29.03.2018 10:36, Odhiambo Washington wrote: > > > > On 29 March 2018 at 09:43, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: > >> >> >> On 28.03.2018 22:14, Odhiambo Washington wrote: >> >> >> >> On 27 March 2018 at 20:06, <aki.tuomi at
2019 Jun 17
1
Deleted dovecot.index.*
On Mon, 17 Jun 2019 at 21:03, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > On 17 June 2019 20:55 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > > > > > > > On Mon, 17 Jun 2019 at 20:45, Aki Tuomi via dovecot <dovecot at dovecot.org> > wrote: > > > > > > > On 17 June 2019 18:59
2020 Oct 16
0
Unable to access mail via Outlook
> On 16/10/2020 13:11 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > On Fri, 16 Oct 2020 at 08:19, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > On 15/10/2020 18:14 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > > > > Here is what I see on the error.log: > > >
2019 Apr 11
1
Mail account brute force / harassment
Marc, There is a strategy loosely referred to as "choose your battles well" :-) Let the others bother with their own problems. If you can, hack the server and dump the 500GB - you'll be using resources transferring the 500GB as the other server receives it. Two servers wasting resources because you think you are punishing an offender! On Thu, 11 Apr 2019 at 13:43, Marc Roos
2019 Feb 05
0
Release notify (2.2.36.1 and 2.3.4.1)
Noted. I will wait for dovecot-2.3.4.2 tarball then. In all the servers I listed (+2 more), I never use the mail/dovecot port. I rely on mail/dovecot port on my own prototype (FreeBSD 12) which I have built in preparation for the upgrade of all the servers I currently have (except the 11.2). So for now, they have to run with 2.3.4, because of that reason - I am not using the port. And yes, I
2010 Nov 02
1
mdbox - how do I fix corrupted indexes?
I am unable top pop mail from my server, using mdbox: Nov 02 16:35:08 pop3-login: Info: Login: user=<wash at domain.co.ke>, method=PLAIN, rip=192.168.40.79, lip=192.168.40.252, mpid=36052 Nov 02 16:35:09 pop3(wash at domain.co.ke): Error: Corrupted dbox file /var/spool/virtual/domain.co.ke/wash/mdbox/storage/m.1 (around offset=1941): Ex t refs metadata corrupted: 3861 783856
2018 Dec 20
3
Authentication Problem
On Thu, 20 Dec 2018 at 15:54, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > On 20 December 2018 at 14:33 Odhiambo Washington < odhiambo at gmail.com> > wrote: > > > On Thu, 20 Dec 2018 at 15:23, Aki Tuomi < aki.tuomi at open-xchange.com> > wrote: > > > > > On 20 December 2018 at 14:10 Odhiambo Washington < odhiambo at gmail.com>
2020 Oct 19
2
Unable to access mail via Outlook
> On 19/10/2020 09:16 Odhiambo Washington <odhiambo at gmail.com> wrote: > > > Bump! > > > On Fri, 16 Oct 2020 at 13:26, Odhiambo Washington <odhiambo at gmail.com> wrote: > > > > > > > > On Fri, 16 Oct 2020 at 13:15, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > > > > > > On 16/10/2020 13:11
2017 Oct 13
0
v2.2.33 released
I have just made an attempt at compiling 2.2.33.1 and it fails on one of my servers - FreeBSD 8.4 where 2.2.32 has been running happily: This is where I am going to start the tests before I move to the other servers (FreeBSD 9.3, 10.3, 11): mv -f .deps/maildir-settings.Tpo .deps/maildir-settings.Plo /bin/bash ../../../../libtool --tag=CC --mode=compile gcc -DHAVE_CONFIG_H -I. -I../../../..
2010 Nov 01
0
Testing pop3/imap4 and mdbox corrupted indexes?
I have two questions: 1. What method/tool (other than a MuA) can I use to test my Dovecot setup from Windows CLI when ssl is enabled? I have tried connecting to to the pop3/imap4 services from a Windows PC but here is what I get: [pop3] +OK Dovecot-2.0-sis ready. user wash at domain.co.ke -ERR Plaintext authentication disallowed on non-secure (SSL/TLS) connections. [imap4] OK [CAPABILITY