similar to: proxy dual server setup clarification

> On 12 Nov 2019, at 16.03, Marc Roos via dovecot <dovecot at dovecot.org> wrote: > > > > > I want to migrate mail users to a new environment. > > If I setup a new server next to the old server, and enable proxy on > both. Is this then enough to migrate user by user with the passdb > host=newsvr option to the new environment? > > Eg. I do not need

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

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

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

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

Looks like I have a correct working proxy on pop3. On both backend servers I can run cat /tmp/test.msg | /usr/libexec/dovecot/lmtp Giving 250 2.1.5 OK 354 OK Info: Disconnect from local: Connection closed (in DATA) However if I run the same command on the proxy, I am getting this error 'Invalid FROM: Missing domain'. How is this FROM even relevant if message just needs to be

When I migrate a guest from svr1 to svr2 and shutdown the guest on svr2. I cannot start it anymore because the xml is not there. How can I make sure this xml is automatically stored so I can start the guest again on svr2?

'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

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

Thanks, Markus, maybe we should add this to the admin_manual? However I am now getting the error 'script: Fatal: Missing script path' Similar as when I try via the command line bash-5.0# /usr/libexec/dovecot/script -e /bin/health-check.sh Fatal: Missing script path bash-5.0# /usr/libexec/dovecot/script -e /bin/ health-check.sh Panic: BUG: No IOs or timeouts set. Not waiting for

Hi asterisk-users, We have recently moved to the 13.x branch of Asterisk from 11.x, and we're trying to correlate CDR records from multiple-legs for billing purposes. As part of this change we have added 'linkedid' to our CDR table schema in an attempt to join the multiple records into one billable record. The call path can be simplified as (transport types in brackets): SIP

:) I really starting to feel a bit like an idiot, but all these 3 configs[0] give error 'Client not compatible with this binary' [0] service health-check { executable = script /bin/health-check.sh inet_listener health-check { port = 5001 } } service health-check { executable = script -e "HOME PATH" /bin/health-check.sh inet_listener health-check { port =

How do I check the standard script then on this port 5001 from the command line? This one of alpine linux also does not have it yet bash-5.0# dovecot --version 2.3.7.2 (3c910f64b) -----Original Message----- Subject: RE: Health check curl example Yes. The passthrough option is rather new. Aki On 24/11/2019 15:28 Marc Roos via dovecot < dovecot at dovecot.org> wrote: I think

I can't yet use -p, the version I have is not supporting it still :( Maybe it is better to wait until alpine linux updates the package. -----Original Message----- Subject: RE: Health check curl example No worries. Now you are not using the passthrough(-p) mode. That is why dovecot is telling you that your client is not compatible. Using "script" without -p would require you

I think I already have that, I am having this configured service health-check { # this is the default configuration using the simple PING->PONG # example health-check. executable = script -p /bin/health-check.sh inet_listener health-check { port = 5001 } } bash-5.0# /bin/health-check.sh HTTP/1.1 200 OK Connection: keep-alive OK -----Original Message----- Subject: Re:

On 06/12/2016 05:21 PM, J Martin Rushton wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > $ scp svr2:/path/to/source svr1:/path/to/dest > > You'll get twice the network traffic since the copy is running on your > workstattoin (or whatever). > > On 12/06/16 15:40, H wrote: >> I normally use ssh to log into a remote server, change directory >>

I normally use ssh to log into a remote server, change directory and then use scp from there to copy files from another remote server to the first one. Now the first server has been hit by continuous error correction messages from the ECC controller, all of which are corrected, and I am unable to get a command line to issue the required commands to change directory and then run scp from the other

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

Hello Guys, I have configured samba & ldap as a domain controller before, but never on a redhat 9 system. I have updated samba & ldap as far as i can tell to the latest. Firstly I have a smaller issue (I think) I get this error when trying to restart ldap, as usual I have followed the samba howto; however it's not the documentation that is the problem more so an unusal problem or

> On Jun 12, 2016, at 11:21 AM, J Martin Rushton <martinrushton56 at btinternet.com> wrote: > > $ scp svr2:/path/to/source svr1:/path/to/dest > > You'll get twice the network traffic since the copy is running on your > workstattoin (or whatever). You probably meant: $ scp -3 svr2:/path/to/source svr1:/path/to/dest -- Jonathan Billings <billings at