search for: svr1

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

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 16 16:30:16 svr1 dovecot: lmtp(16466): Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= Dec 16 16:30:16 svr1 dovecot: lmtp(16466): Connect from local Dec 16 16:30:16...

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 16 16:30:16 svr1 dovecot: lmtp(16466): Debug: none: root=, index=, indexpvt=, control=, inbox=, alt= Dec 16 16:30:16 svr1 dovecot: lmtp(16466): Connect from local Dec 16 16:30:16 s...

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

'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,886...

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 '*' -----Original Message----- From: Aki Tuomi [mailto:aki.tuomi at open-xchange.com] Sent: 16 December 2019 06:22 To: Marc Roos; dovecot...

...e 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 -> rbrick2 svr1:vol3 <-> srv2:vol3 -> rbrick3 svr1:vol4 <-> srv2:vol4 -> rbrick4 svr1:vol5 <-> srv2:vol5 -> rbrick5 svr1:vol6 <-> srv2:vol6 -> rbrick6 svr1:vol7 <-> srv2:vol7 -> rbri...

Hi Aki, I also tried with changing the original ldap source to svr2. Although everywhere svr2 is configured, still mails keep being delivered locally on svr1. Do I need to configure more than 20-lmtp.conf? [@svr1 conf.d]# cat 20-lmtp.conf | grep -v '^#' lmtp_proxy = yes protocol lmtp { # Space separated list of plugins to load (default is global mail_plugins). mail_plugins = $mail_plugins sieve info_log_path = /var/log/dovecot-l...

...<a href="mailto:m.roos@f1-outsourcing.eu">m.roos@f1-outsourcing.eu</a>> wrote: </div> <div> <br> </div> <div> <br> </div> <div> I receive a local mail when I do a 'mail test' on a backend svr1 with </div> <div> this[0] configuration. However when I just add only one configuration </div> <div> change 'lmtp_proxy = yes' I am getting these errors[1]. I would expect </div> <div> this email to still be delivered locally...

...e 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 Phone---(SIP)---Asterisk Svr1---(IAX)---Asterisk Svr2---(IAX)---Asterisk Svr3---(SIP)---PSTN As per the CDR spec, I expected the 'linkedid' to propagate between the records and be the same throughout... However, we observe differing linkedid values for the same call... Thus (xxx's added for privacy): | id | ca...

Mar 11 11:24:52 box1 tincd: Trying to connect to svr1 (a.a.a.a port 443) Mar 11 11:24:52 box1 tincd: Connected to svr1 (a.a.a.a port 443) Mar 11 11:25:02 box1 tincd: Timeout from svr1 (a.a.a.a port 443) during authentication Mar 11 11:25:02 box1 tincd: Closing connection with svr1 (a.a.a.a port 443) Mar 11 11:25:02 box1 tincd: Could not set up a meta...

Hi, I see there’re two configuration in tinc: In main configuration: BindToAddress = <address> [<port>] In host configuration: Port = <port> So, let’s say on svr1 /etc/tinc/test/tinc.conf: BindToAddress = ip_addr p1 BindToAddress = ip_addr p2 /etc/tinc/test/hosts/svr1: Port = p1 On the client side c1 /etc/tinc/test/tinc.conf: ConnectTo = svr1 /etc/tinc/test/hosts/svr1: Port = p2 So, in the above case, the c1 will establish meta-connection to svr1 on p2,...

...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 missing packages on my system. ERROR1: [root@Tini-Svr1 sbin]# service ldap restart Stopping slapd: [FAILED] Starting slapd: Unrecognized database type (bdb) [FAILED] ERROR2: [root@Tini-Svr1 sbin]# ./smbldap-populate -a root -k 0 -m 0 Can't...

> 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 negate.org>

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 >> and then use scp from there to copy files from...

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

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?

I have this in my 20-lmtp.conf file and created passdb-file, this should be enough to route a message to svr1? The port 24 is reachable from the proxy. bash-5.0# cat 20-lmtp.conf lmtp_proxy = yes protocol lmtp { # Space separated list of plugins to load (default is global mail_plugins). passdb { driver = passwd-file args = /etc/dovecot/special-passdb default_fields = proxy=y host=svr1 } }...

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 to configure a director setup? I only need to enable proxy for imap and lmtp on both servers? (messages on the oldsvr will be proxied to the

...communication. When this happens, reloading the usbhid-ups driver and even unplugging and re-inserting the USB cable does not fix the problem, and lsusb does not list the UPS at all. On one system, an x86_64 server running kernel 3.17.3, the following can be seen in the log: Nov 21 23:24:07 test-svr1 kernel: [111233.920039] ohci-pci 0000:00:02.0: frame counter not updating; disabled Nov 21 23:24:07 test-svr1 kernel: [111233.920047] ohci-pci 0000:00:02.0: HC died; cleaning up Unloading and re-inserting the ohci kernel modules (ohci_hcd and ohci_pci) does temporarily resolve the issue on this ho...