similar to: Dovecot director doveadm with switch "-A" error

Displaying 20 results from an estimated 2000 matches similar to: "Dovecot director doveadm with switch "-A" error"

2011 Dec 05
3
lmtp panic in proxy lmtp director
Hi, we are getting some core dumps with signal 6 in ltmp on a dovecot director proxy server, like this: Dec 5 14:31:51 sproxy1 dovecot: lmtp(29999): Panic: file lmtp-proxy.c: line 376 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof) Dec 5 14:31:51 sproxy1 dovecot: lmtp(29999): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0() [0x363323d99a] ->
2012 Jun 29
2
doveadm purge -A via doveadm-proxy director fails after some users
Hi, we have configured userdb and passdb in the director and try to iterate all users and pass the "purge" command via doveadm proxy to port 19000 on the correct director backend host. A single purge -u username at example.org via doveadm-proxy works correctly, but iterating over some users with -A fails. Note: users/domains have been anonymized in output:
2012 Feb 14
1
doveadm director proxy
I'm trying to configure a doveadm service that will proxy trough our directors, following the recipie at: http://wiki2.dovecot.org/Director#Doveadm_server So on the backends I have: service doveadm { inet_listener { port = 24245 address = * } } doveadm_proxy_port = 24245 local 192.168.42.0/24 { doveadm_password = suPerSeecret } I assume the "local"
2020 May 28
2
service doveadm - how to debug proxying with director
Hello everyone, I'm on a small dovecot director -> dovecot mailbox setup and I try to get doveadm command proxying to work. Though I don't get the expected output. My directors do not forward the doveadm commands to the expected backend host. Doveadm is working as expected on the backend hosts, the director hosts just dont log anything about the proxying that should happen or
2014 May 13
0
Error on doveadm director map
Hi All, I am running Dovecot 1:2.2.9-1~bpo70+1 on Debian Wheezy. I have just started getting the error below when I do a do a list of proxied users. The list of users appears OK afterwards. # doveadm director map doveadm(root): Error: User listing returned failure doveadm(root): Error: user listing failed user mail server ip expire time . . . My director config is below. Thanks
2012 Nov 09
1
doveadm quota get -A via doveadm-proxy director with LDAP
Hi, We are running Dovecot 2.1.10 I want configure dovecot to do execute doveadm commands on the proxy server. We have 1 proxy with director and 2 mail servers. we use LDAP when I try to do doveadm quota get -u user it works fine. The problem is when I try to do doveadm quota get -A ON PROXY I have this result: doveadm(first_user): Error: Proxy is missing destination host doveadm: Error: Failed
2012 Aug 27
1
doveadm commands returning 139 at director servers
Hello, I have configured director in front of dovecot imap/pop/lmtp servers. When I need to manipulate a user mailbox, I use doveadm commands at director server's, with -S option. But some commands return exit code 139 when command returns more than 40 entries (I think). For example, the command: sudo doveadm fetch -u amateo hdr mailbox Trash HEADER Subject "nyctalus11/"
2012 Sep 12
1
doveadm director map : User listing returned failure
Hello we are running Dovecot 2.1.9. We have 2 proxies with director and 4 mail servers. We have the user information in a LDAP. I try to do: # doveadm director map doveadm(root): Error: User listing returned failure doveadm(root): Error: user listing failed user mail server ip expire time <unknown>
2012 Jun 12
2
Problem with lmtp director proxy
Hi, I have a timeout problem only when I have heavy load in my system. I have two director servers directing to 4 backend servers. The problem is when my smtp relays tries to deliver mail to my users via lmtp (proxied with director). In the smtp logs I have: Jun 12 11:41:18 xenon13 postfix/lmtp[4248]: 4433E5D5A0: to=<myuser at um.es>, relay=pop.um.es[155.54.212.106]:24, delay=31,
2012 Jun 29
1
director directing to wrong server (sometimes)
Hello, I have discovered a strange behaviour with director proxying... I have a user, its assigned server is 155.54.211.164. The problem is that I don't know why director sent him yesterday to a different server, because my server was up all the time. Moreover, I'm using poolmon in director servers to check availability of final servers and it didn't report any problem with the
2012 Jun 08
1
director and doveadm server
Hi, I've been reading doc at http://wiki2.dovecot.org/Director to configure my servers. My question is regarding configuration of doveadm server. I have configured both, director and backend servers, as described in that doc, but I don't know how to run doveadm commands in director servers. doveadm is working, because I can run commands, but they are executed in local (director)
2012 Jun 20
1
director map and mysql
hello! Is "doveadm director map" command suppose to work when I store "host" value in mysql table? It gives me nothing in output with no errors in log. I've successfully setup directors with static passdb, and decided to give a try setup with storing host value in mysql table. The proxying is actually working, I'm just unhappy with no output from "doveadm
2013 Nov 06
0
2.2.6 auth process crash using LMTP and LDAP on director.
I'm upgrading my configuration to use director and lmtp for delivery. (doveconf -n at end of the mail). I use the same config for auth on mail backends and see no errors. My setup seem to work nicely but i have some auth process crashing when using lmtp protocol. Everything is working a sexpected then i've got 5-6 errors like this in logs and a crach of the auth process: dovecot:
2017 Mar 20
0
doveadm proxy password
Hi, I'm configuring a proxy host to connect to backend servers. As proxy is done based on an LDAP attribute of the user, I'm not using director. In the proxy server I have configured: doveadm_port = 24245 doveadm_password = secret And in the backend: service doveadm { inet_listener { port = 24245 } } local <mynetwork> { doveadm_password = secret }
2010 Nov 24
1
proxy (director) and destination ports
Hello, i am delivering Mail from postfix via LMTP to dovecot. I am using the director also for LMTP. As long as i connect to the dovecot LMTP TCP socket from postfix everything is working. postfix main.cf: virtual_transport= lmtp:localhost:30025 But when i try to switch to the local socket postfix main.cf: virtual_transport = lmtp:unix:private/dovecot-lmtp The dovecot proxy tries to
2012 Jul 13
1
Difference between proxy_refresh and proxy_timeout in director
Hello, I know proxy_timeout is the timeout for the director operation. But what is the purpose for proxy_refresh? -- Angel L. Mateo Mart?nez Secci?n de Telem?tica ?rea de Tecnolog?as de la Informaci?n _o) y las Comunicaciones Aplicadas (ATICA) / \\ http://www.um.es/atica _(___V Tfo: 868887590 Fax: 868888337
2012 Jul 17
3
doveadm director status username != doveadm director status username@mailserver
Hi, I've almost finished my new director based setup, but in the first test I discovered that imap and lmtp connections were not always being proxied to the same server. After some research now I think that the main problem is that in imap connections users connect as 'username' while lmtp connections are as 'username at mailserver'. In my current setup I receive mail via
2012 Oct 16
1
doveadm purge -A via doveadm-proxy director fails after some users
# 2.1.10: /etc/dovecot/dovecot.conf # OS: Linux 2.6.32-44-server x86_64 Ubuntu 10.04.4 LTS doveadm -c /etc/dovecot-director/dovecot-director.conf -D purge -A shows the following message in the log when iterating the 49th user: Oct 17 00:47:17 10.129.3.233 dovecot: doveadm: Error: purge: invalid option -- 'e' Oct 17 00:47:17 10.129.3.233 dovecot: doveadm(someuser at example-ll.org):
2010 Nov 01
3
Wrong protocol in socket (director-doveadm vs director) ?
I just noticed this error in my logs: director: Error: doveadm not compatible with this server (mixed old and new binaries?) director: Error: director(10.161.192.28:541/right): Wrong protocol in socket (director-doveadm vs director) The first error I removed by changing director_doveadm_port = 541 to director_doveadm_port = 542 Not really sure why that fixed it. The second error I
2017 May 30
3
Asterisk 14.3.1 > 14.4.1 upgrade pjsip nat broken?
Hi first post, so hope I'm not violating protocol. Been using Asterisk as home phone and hobby use for nearly 10 years. I love this project. Anyway, would someone mind verifying my pjsip.conf ? This seems to work well for 14.3.1 but I get no rtp into my natted Linphone when I upgrade to 14.4.1. Other than that the phone registers properly on 14.4.1. I can provide a pjsip log as well,