similar to: dovecot: auth: Error: DNS lookup for xxx failed: Name does not resolve

I am sure resolving works fine. I tested this in a running mesos container, but also in docker run[1]. I need to have the search local option in resolve.conf. It was actually working, until I started adding the proxy for managesieve, but when I reverted, it still does not work. I think the building from cache mislead me. I suspect this is a different problem, that at some point is giving

Marc> I had a working container with dovecot configured as proxy. And Marc> all of a sudden I am getting these messages 'dovecot: auth: Marc> Error: DNS lookup for roosit03 failed: Name does not resolve' Marc> Pinging/nslookup these hostnames is ok Does nslookup work inside the container? Sounds to me like the setup isn't working properly, but it's hard to know unless

Having > 10 TByte mailstore filesystem-checks takes too much time. At the moment we have four different partitions, but I don't like to set symlinks or LDAP-flags to sort customers and their domains to there individual mount-point. I'd like to work with mdbox:/mail/%d/%n to calculate the path automatically. How do you handle >> 10 TB mailstore? I'm very interested in the

I'm using roundcube webmail managesieve plugin. Webmail can login managesieve to a specific mailstore successfully without proxying. Because I have mutiple mailstores, I have to use proxying to redirect the correct mailstores just as imap/pop3. ???? Stephan Bosch ????? 2016-04-03 22:50 ???? Hawk Chen; dovecot ??? Re: ??: Re: managesieve proxying not working Op 3-4-2016 om 16:32 schreef

Hi all. We've just migrated our back-end NFS mailstore from FC1 systems to CentOS4 and are experiencing problems/delays with vpopmail and user Maildirs. IMAP is fine, it's just POP access that causes us problems. Now, NFS mounts successfully, the clients can see /home/vpopmail and serve content as we would expect. IMAP works perfectly and sees new messages as soon as they're

Hi list, I am trying to build an email system that is using multiple frontends, to a clustered backend using nfs. The backend mounts his filesystems from a central storage, and will be running active-active. While reading through the dovecot documentation, I read that I could do without indexes (well: use memory indexes), and could then be able to run dovecot over NFS. Well: that was until

Hi Aki, If I adapt this configuration on svr1 like this[0], should the mail not be delivered at svr2 passdb { driver = pam # [session=yes] [setcred=yes] [failure_show_msg=yes] [max_requests=<n>] # [cache_key=<key>] [<service name>] #args = dovecot default_fields = proxy=y host=svr2 } passdb { driver = passwd skip = authenticated default_fields = proxy=y

HI All, We have a couple of dovecot director proxies and six backed mailstores each accessing mailboxes stored on five NFSv4 filsystems with about 1TB of mail on each in maildir format.? We have about 800 max users on each mailstore at peak times and performance appears to starting to degrade at these times.? The mailstores are pretty recent hardware with 64GB of RAM and 24 cores.?? The NFS

Hola a tod en s, sigo intentando representar una variable en función de meses. En la columna Mesos tengo los meses de la siguiente manera: 01/08/1996, 01/09/1996 etc. He probado con el siguiente comando: plot(Mesos, Serie01) obteniendo y tendría que obtener: [image: Imágenes integradas 2] Pero donde pone Observation Index, me gustaria tener los meses (para esta grafica he usado

Hi Aki, you have some ingenious remark that could help? -----Original Message----- To: aki.tuomi; dovecot Subject: RE: Local lmtp proxy on backend server I am staring constantly at the same logs, this is what I get from dovecot[1]. Sendmail[2] is sending with test at svr1 maybe this overrides lmtp proxying? This is a test with a special-userdb passwd-file also having host=svr2 [1] Dec

I receive a local mail when I do a 'mail test' on a backend svr1 with this[0] configuration. However when I just add only one configuration change 'lmtp_proxy = yes' I am getting these errors[1]. I would expect this email to still be delivered locally, should this be working or do I misunderstand the lmtp proxy functionality? [0] passdb { args = auth_verbose = default

'K, not sure how/what to debug here ... doing a grep of svr1.postgresql.org in /proc/*/status shows all the processes 'stuck' in inode ... /proc/38750/status:inetd 38750 2072 2072 2072 -1,-1 noflags 1055120147,191009 0,0 0,592 inode 0 0 0,0,0,2,3,4,5,20,31 svr1.postgresql.org /proc/38752/status:inetd 38752 2072 2072 2072 -1,-1 noflags 1055120154,886433 0,0 0,637 inode 0 0

Hello everyone, I playing around with ENUM and have configured * to query a few sources for testing purposes (fierymoon, e164.arpa, e164.org). I'd like to know if there is a way to query these servers manually (ie outside of asterisk via nslookup or equivalent) to find out if particular exchanges are listed with wildcards, so as to terminate calls to those prefixes (I'm not trying to

I added this: passdb { driver = passwd skip = authenticated } Which enables indeed local delivery, I also noticed this. Maybe the password field check shoud not be done, when you enable skip authentication? Dec 16 10:26:37 svr1 dovecot: auth-worker(12046): Debug: passwd(test): lookup Dec 16 10:26:37 svr1 dovecot: auth-worker(12046): passwd(test): invalid password field '*'

Before I undertake this upgrade I thought I would see if anyone has any advice on how to do this on a production system. Maybe someone has already "fought this dragon". Current config Gluster V3.0.0. This has been in production for over 16 months: 2 servers with 8 x 2TB hard drives (bricks) replicated svr1:vol1 <-> srv2:vol1 -> rbrick1 svr1:vol2 <-> srv2:vol2 ->

Well, I have finally installed Samba 4.9 from Van Belle's repo, but still I cannot resolve FQDN's. Dňa 22. 1. 2019 o 15:02 Rowland Penny via samba napísal(a): > On Tue, 22 Jan 2019 14:51:02 +0100 > "Mgr. Peter Tuharsky via samba" <samba at lists.samba.org> wrote: > >> Rowland, thank You, but this removes only the NS record, but the >> faulty domain A

Running a new install of samba 4.1 AD, also using winbind to handle Linux user, group authorizing users. I'm have problems with DNS lookups for ssh client don't work nslookup on the same AD and member system works fine. For example: I can run nslookup example.com and it returns a valid answer right way. If I try to ssh -l username example.com , ssh returns "ssh: Could not resolve

Folks, We are in the process of purchasing new san/s that our mail server runs on (JES3). We have moved our mailstores to zfs and continue to have checksum errors -- they are corrected but this improves on the ufs inode errors that require system shutdown and fsck. So, I am recommending that we buy small jbods, do raidz2 and let zfs handle the raiding of these boxes. As we need more

Hi All, I am using dovecot in the Director setup with multiple proxy and backend mailstores and user information stored in LDAP.? I am aware users can be directed to a single backend server.? It would be useful to be able to direct groups of users to pairs of backend servers to give some fault tolerance against NFS issues and make the whole thing more scalable.??? Otherwise each backend mailstore

Hi All, I need to import mailboxes into my Director NFS setup via one of my director proxy's as doing a direct dsync to the backend mailstores appears to giving me NFS locking issues. It looks like it may be possible to do this using doveadm listeners. I have setup doveadm listeners on a test proxy and backend mailstore. I am not sure how to make the dsync proxy through to the backend