Displaying 20 results from an estimated 10000 matches similar to: "Lmtp proxy help assertion failed: (conn->remote_port != 0"
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 15
3
Local lmtp proxy on backend server
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
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 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 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 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
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 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
2014 Dec 22
1
Configuring LMTP/IMAP proxy
Hi,
First, my version:
[root at centos1 conf.d]# dovecot --version
2.2.15
[root at centos1 conf.d]#
I have already configured dovecot that way (on one single VM, so everythinh is stored on the same machine)
- A post fix server sending out to LMTP
- LMTP is the dovecot LMTP server, configured with "lmtp-proxy= no",
- LMTP checks the users receiving
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
2011 Sep 29
1
Panic: file lmtp-proxy.c: line 370 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof)
Hello all,
today I got this crash from dovecot (2.0.14)
Sep 29 14:09:32 imap1 dovecot: lmtp(17693): Panic: file lmtp-proxy.c: line 370 (lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof)
Sep 29 14:09:32 imap1 dovecot: lmtp(17693): Error: Raw backtrace: /usr/lib64/dovecot/libdovecot.so.0(+0x3f9aa)? [0x7f18f10299aa] -> /usr/lib64/dovecot/libdovecot.so.0(+0x3f9f6)
2010 Dec 29
0
panic with lmtp proxy (assertion failed)
Hello!
Got a panic&assertion failed with LMTP proxy. Target Dovecot LMTP
server hanged and Dovecot LMTP proxy server started logging
panics/assertions. Core dumps were disabled unfortunately, so I don't
know if this is helpful at all:
Dec 29 15:41:58 lmtp(8853): Panic: file lmtp-proxy.c: line 370
(lmtp_proxy_output_timeout): assertion failed: (proxy->data_input->eof)
Dec 29
2011 Nov 24
3
Problem with lmtp proxy
Hello everyone,
I have set up postfix to deliver mails to dovecot (2.0.16) using LMTP. On the other hand, I've successfully configured the IMAP proxy setting in dovecot in order to be able to distribute mailboxes among different servers. I wanted to do the same proxy at LMTP level, but it's not working. If I put lmtp_proxy = no, then everything works ok (assuming the mailbox is local),
2014 Jun 25
0
imap/pop3/lmtp proxy question/problem
Dear list,
We are finally back to our task of migrating from cyrus to dovecot.
dovecot mostly does what we want in terms of POP3/IMAP server. Now we
are preparing for migration. The plan is to use dovecot as proxy for
not-yet migrated accounts. This works wonderfully for IMAP but not for
LMTP. Here's what I find in the logs when I try to deliver e-mail to
the dovecot lmtp port:
Jun 25
2019 Nov 24
2
lmtp proxy 'Invalid FROM: Missing domain'
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
2019 Nov 28
2
sendmail -> lmtp 501 5.6.0 Data format error
When changing in a working setup sendmail.mc
From this
MAILER(smtp)dnl
MAILER(procmail)dnl
To this
FEATURE(`local_lmtp',`[IPC]',`FILE /var/run/dovecot/lmtp')dnl
MAILER(local)dnl
I am getting these errors '501 5.6.0 Data format error' and '
Unrecognized host name'.
What should I change in my lmtp config? Could this be related that
messages are being relayed from
2013 Jul 03
2
LMTP Proxy
Trying to figure out Proxying with LMTP to a few back end storage servers
for quota checking before accepting email delivery on the front end nodes.
If I connect to the back end server directly via telnet, everything works
great.
If I use a front-end server to proxy to the back end server, I don't get
the same result.
Running 2.2.4 on both front and back end servers.
Any help would be
2019 Nov 25
2
Health check curl example
:) 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 =
2012 Feb 14
2
R: Re: LMTP : Can't handle mixed proxy/non-proxy destinations
Hi Timo,
I'm writing to alert you that even in version 2.1. we have the error: "Can't
handle mixed proxy/non-proxy destinations" when we write to two users: one
existent and one not.
The error occurs randomly.
I configure LDAP query in the file : dovecot-ldap.conf in this way:
pass_attrs = mail=user,userPassword=password,=proxy=y,mailHost=host,
=proxy_timeout=600
2019 Nov 25
2
Health check curl example
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