Displaying 20 results from an estimated 10000 matches similar to: "How to send a test message directly to lmtp, to test proxying"
2019 Nov 12
0
How to send a test message directly to lmtp, to test proxying
On 12.11.2019 15.26, Marc Roos via dovecot wrote:
>
> How to send a test message directly to lmtp, to test proxying?
Using LMTP protocol:
LHLO localhost
MAIL FROM:<me>
RCPT TO:<you>
DATA
...
.
Aki
2018 Mar 22
2
lmtp service timeouting even after receiving full message
I have a problem with some messages passed from exim to dovecot lmtp service:
From exim debug:
using socket /var/run/dovecot/lmtp
LMTP<< 220 mbox8 ready
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
2013 Jul 04
2
DOVECOT 2.2.4 = 501 5.5.4 Unsupported options in LMTP
Hi,
Sorry for my english.
My problem:
***************************************************
dspam-3.9.0 (dspam-3.10.2 all the time segmentation fault)
dspam.conf
....................
# DeliveryHost /var/run/dovecot/lmtp # same error as IP
DeliveryHost 127.0.0.33
DeliveryPort 24
DeliveryProto LMTP
....................
ServerHost 192.168.1.34
ServerPort
2016 Feb 11
3
LMTP proxy does not pass RCPT TO: ... 5xx response back
Hello,
I'm using dovecot 2.2.9 and a director/backend setup.
On the director I've the LMTP in proxy mode, mapping the users to one of
the backends.
The backends to quota check and return the OverQuota message already at
RCPT TO time.
Here is what I typed, connected to the director
Connection to director1 2525 port [tcp/*] succeeded!
220 director1.rz.hs-example.de Dovecot
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 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
2017 Oct 26
2
Bug: lmtp proxy does not quote local parts with spaces
There seems to be a bug with RFC822 processing in ltmp proxying that doesn't
quote local parts that, for example, contain spaces.
director config:
director_username_hash = %Ln
lmtp_proxy = yes
recipient_delimiter = +
protocol lmtp {
auth_socket_path = director-userdb
auth_username_chars =
auth_username_format = %Ln
passdb {
2012 Sep 27
1
LTMP Proxy fails when backend server connection refused
Version: 2.1.9
Connecting directly to the proxy server on the LMTP port, issue lhlo,
mail from, rcpt to, data. After the . closing of data, it just hangs
there. The logs on the proxy server show:
Sep 27 19:55:12 proxy1 dovecot: lmtp(9398): Connect from 69.8.2.71
Sep 27 19:55:24 proxy1 dovecot: lmtp(9398): Error: lmtp client:
connect(lmtp, 7025) failed: Connection refused
root 9398 1102
2019 Mar 17
2
testing dovecot LMTP with postfix/spamassassin
:-)
On 3/17/19 10:22 AM, Yassine Chaouche via dovecot wrote:
>
> On 3/16/19 3:49 PM, Marek Kozlowski via dovecot wrote:
>> Can I test local mail delivery by dovecot LMTP manually? I mean: to
>> simulate "I'm the Postfix" and produce for some testing e-mail the
>> same effect as postfix granting it via `local_transport' to dovecot?
>>
> You can
2017 Oct 26
2
Bug: lmtp proxy does not quote local parts with spaces
On 26/10/2017 18:38, Alexander Dalloz wrote:
> Am 26.10.2017 um 12:20 schrieb David Zambonini:
>>
>> There seems to be a bug with RFC822 processing in ltmp proxying that
>> doesn't
>> quote local parts that, for example, contain spaces.
>
> Newer related RFCs are RFC 5321 and 5322.
Typo, meant to say RFC2822, which they still supercede, not that the
2017 Nov 01
2
Bug: lmtp proxy does not quote local parts with spaces
Hi again,
I've not heard anything further regarding this bug, so I've had a look at the code.
To restate the bug in a more precise way: LMTP in dovecot treats external RFC822
email addresses in the envelope recipient and internal usernames as almost
identical/interchangeable. This is incorrect and leads to issues when attempting
to use director as an LMTP proxy to proxy to recipients
2013 Jul 19
3
mails delivered to the wrong user when using lmtp_proxy and reject_unverified_recipient
Hi,
looks like we detected a serious bug in dovecot's lmtp proxying where
e-mails are delivered to the wrong user.
The setup is:
*) Dovecot is configured with "lmtp_proxy=yes"
# Support proxying to other LMTP/SMTP servers by performing passdb lookups.
lmtp_proxy = yes
*) Postfix uses "dynamic recipient verification", so Postfix starts
sending a (verify) mail by LMTP to
2012 Jan 27
1
LMTP : Can't handle mixed proxy/non-proxy destinations
Hello,
In my current setup, I uses two mailservers to handle the users
connections, and my emails are stored on a distant server using NFS
(maildir architecture)
Dovecot is both my IMAP server and the delivery agent (LMTP via postfix)
To avoid indexing issues related to NFS, proxying is enabled both on IMAP
and LMTP. But when a mail is sent to users that are shared between the
servers, I got the
2019 Dec 12
1
Lightweight LMTP daemon to avoid overkill MTA
I ended up 'hacking' LMTP support into the external spam filter. Someone else already contributed 'real' patches to implement LMTP support, so once I go live with this mail platform it should be stable.
Met vriendelijke groeten,
William Edwards
T. 040 - 711 44 96
E. wedwards at cyberfusion.nl
?
----- Original Message -----
From: Marc Roos (M.Roos at f1-outsourcing.eu)
Date:
2017 Feb 24
4
Sieve removeflag Action
Op 2/22/2017 om 8:40 PM schreef Thomas Leuxner:
> * Thomas Leuxner <tlx at leuxner.net> 2017.02.20 12:56:
>
>> Feb 20 07:00:23 nihlus dovecot: master: Dovecot v2.2.devel (8f42a89) starting up for imap, lmtp
>>
>> This one processed the dovecot-news mail for 2.2.28.rc1 fine which uses a similar sieve rule. I will monitor global rules with this build and report back.
2019 Dec 11
3
Lightweight LMTP daemon to avoid overkill MTA
Hi,
I was unclear in my question. The spam filter is only able to deliver mail over SMTP, not over LMTP.. So I would still need some kind of daemon that listens for SMTP and then offers incoming email to Dovecot's LMTP socket.
Met vriendelijke groeten,
William Edwards
T. 040 - 711 44 96
E. wedwards at cyberfusion.nl
?
----- Original Message -----
From: Marc Roos (M.Roos at
2019 Dec 13
2
Dovecot 2.3.9 - lmtp crashes with Signal 11
Hallo Aki,
the affected code location seems to be concerned with parsing to ?To:? header. I checked all the mails causing the crash, the To: header is either empty (but present) or contains ?undisclosed-recipients:;?.
I checked this manually and sure enough lmtp crashes:
nc -C -U dovecot-lmtp
220 keira.mike2k.de Dovecot