similar to: lmtp proxy 'Invalid FROM: Missing domain'

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

If I add a domain, error changes in: connection.c: line 380 (connection_update_properties): assertion failed: (conn->remote_port != 0) -----Original Message----- Subject: 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:

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

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

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

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

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

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

How to send a test message directly to lmtp, to test proxying?

hi (especially to you, Aki), so to solve the previous UID issue, i went the full LMTP route. however, i seem to be having problems with the prefetch userdb (i'm trying to minimize load on the LDAP server). namely, the log says: Aug? 2 00:15:35 rhyno postfix/submission/smtpd[21158]: 5EEF35C05C5: client=localhost[127.0.0.1], sasl_method=login, sasl_username=aik Aug? 2 00:15:40 rhyno

Hi Aki, first thanks for the quick fix. Unfortunately, it only resolves the issue partially. For the ?To: undisclosed-recipients:;?, it works now. For ?To: ? it still crashes (i. e. what I did with my manual lmtp dialog). Michael > On 13. Dec 2019, at 11:54, Aki Tuomi <aki.tuomi at open-xchange.com> wrote: > > Hi! > > We have released v2.3.9.1 fixing this issue. >

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

ah well, but i'm not using sql at all. here's doveconf -n: # 2.2.27 (c0f36b0): /etc/dovecot/dovecot.conf # Pigeonhole version 0.4.16 (fed8554) # OS: Linux 4.9.0-4-amd64 x86_64 Debian 9.4 auth_cache_negative_ttl = 0 auth_mechanisms = plain login hostname = rhyno.tech mail_debug = yes mail_location = maildir:~/mail namespace inbox { ? inbox = yes ? location = ? mailbox Drafts { ???

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 {

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

Hi, We are seeing a frequent assertion failure on LMTP delivery with 2.3.0. This only appears to happen on CentOS/RHEL 7. Jan 24 08:30:58 smoker-devautomerge-c7-1 dovecot: lmtp(29540): Panic: file lib-event.c: line 148 (event_unref): assertion failed: (event != current_global_event) Jan 24 08:30:58 smoker-devautomerge-c7-1 dovecot: lmtp(29540): Error: Raw backtrace:

Can you provide p *addr? Aki On 13.12.2019 13.15, Michael Stilkerich wrote: > HI, > > and the backtrace (essentially same as before except for the line numbers moved by the code changes): > > Core was generated by `dovecot/lmtp'. [50/749] > Program terminated

I tried setting the "destuser" setting on the LMTP director as follows, to preserve the original envelope rcpt: protocol lmtp { auth_socket_path = director-userdb passdb { driver = ... override_fields = destuser=%{orig_user} } } The passdb driver would return the appropriate "user" for each alias. Suppose, for example, user1 has emails user1 at domain.tld,

Hello, since the upgrade from 2.3.8 to 2.3.9 (using the Ubuntu 18.04 packages from dovecot.org), lmtp crashes for me for some mails. Currently I have three pending mails in my postfix deferred queue since the upgrade a couple of days ago. I did not observe these issues with 2.3.8. The backtrace from one of the coredumps: Reading symbols from /usr/lib/dovecot/lmtp...Reading symbols from

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