Displaying 20 results from an estimated 4000 matches similar to: "Local lmtp proxy on backend server"
2019 Dec 16
5
Local lmtp proxy on backend server
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
2019 Dec 16
1
Local lmtp proxy on backend server
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 '*'
2019 Dec 17
1
Local lmtp proxy on backend server
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
2019 Dec 16
0
Local lmtp proxy on backend server
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
2019 Dec 16
0
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
2019 Dec 16
0
Local lmtp proxy on backend server
<!doctype html>
<html>
<head>
<meta charset="UTF-8">
</head>
<body>
<div>
<br>
</div>
<blockquote type="cite">
<div>
On 15/12/2019 23:09 Marc Roos <
<a href="mailto:m.roos@f1-outsourcing.eu">m.roos@f1-outsourcing.eu</a>> wrote:
</div>
<div>
2019 Dec 03
2
Live migrate with virsh migrate
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?
2019 Nov 12
2
proxy dual server setup clarification
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
2018 Oct 03
2
Non-matching linkedid on CDR Records [SEC=UNCLASSIFIED]
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
2016 Jun 12
1
scp via another server
> 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
2020 Apr 16
2
Bug maybe already resolved? Sieve rule does not accept special use folder names
I do not have the log file anymore from the home dir. It just complains
that the folder Spam does not exist.
dovecot: lmtp(xxxx): oG8YI6enmF7FIAAAI7dPvA: sieve: Execution of script
/xxxx/.dovecot.sieve failed, but implicit keep was successful (user
logfile /xxx/.dovecot.sieve.log may reveal additional details)
-----Original Message-----
From: Stephan Bosch [mailto:stephan at rename-it.nl]
2016 Jun 12
4
scp via another server
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
>>
2020 Apr 16
2
Bug maybe already resolved? Sieve rule does not accept special use folder names
It is a 'special use' folder, so it only appears to exist in mail
clients.
# spam folders merging
mailbox Junk {
special_use = \Junk
auto = create
}
mailbox Spam {
special_use = \Junk
auto = no
}
mailbox "Junk E-mail" {
special_use = \Junk
auto = no
}
On 16/04/2020 23:19, Marc Roos wrote:
> I do not have the log file anymore from the
2020 Apr 16
2
Bug maybe already resolved? Sieve rule does not accept special use folder names
Sieve rule fileinto Spam fails, while fileinto Junk succeeds
mailbox Spam {
special_use = \Junk
auto = no
}
dovecot-pigeonhole-2.2.36-3.el7_7.1.x86_64
dovecot-2.2.36-3.el7_7.1.x86_64
CentOS Linux release 7.7.1908 (Core
2019 Nov 30
1
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
2020 Apr 16
1
Bug maybe already resolved? Sieve rule does not accept special use folder names
Hmmm, confusing, clients should then display the mailbox name redirected
by the server.
If a user in a front end just sees the 'Junk E-mail', that is the name
he is going to be using in his mailbox rules. If he does not know that
this is actually the Junk folder on the server, he will make an
incorrect message rule.
So I guess you have to correct this server side, before storing
2016 Jun 12
3
scp via another server
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
2016 Jun 13
2
scp via another server
On June 12, 2016 8:51:42 PM CEST, cpolish at surewest.net wrote:
>On 2016-06-12 19:07, H wrote:
>> 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
2019 Nov 30
2
dovecot: auth: Error: DNS lookup for xxx failed: Name does not resolve
I had a working container with dovecot configured as proxy. And all of a
sudden I am getting these messages 'dovecot: auth: Error: DNS lookup for
roosit03 failed: Name does not resolve'
Pinging/nslookup these hostnames is ok
2019 Nov 30
2
Domain XML Multicast Tunnel
Hello
I found under networking in the Domain XML 'Multcast tunnel'.
My question is does anyone know what is the intended use of multicast tunnel networking?What are the potential pitfalls of using such a configuration other than what's highlighted in the domain xml. eg: can it suffer from throughput issues? Can the tunnel be accessed from outside Libvirt?
I'm struggling to find any