search for: rcpt

...have made it into 2.3.0.1 (I compared with the source from https://dovecot.org/releases/2.3/dovecot-2.3.0.1.tar.gz). https://github.com/dovecot/core/commit/2bf919786518d138cc07d9cc21e14ad5e07e5e56#diff-7964e00c46515956a959fa47fc86d605 I also noticed a similar construct being used on line 465 (rcpt->rcpt.rcpt->path) that was causing the segfault on the above commit on line 136. struct smtp_address *rcpt_to = rcpt->rcpt.rcpt->path; Should that also use rcpt->rcpt.path; ? Thanks from the other side of the gulf! Reio -------------- next part -------------- An HTML attachment...

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 (Ubuntu) ready. LHLO mailhub1.rz.hs-example.de 250-director1.rz.hs-example.de 250-8BITMIME 250-ENHANCEDSTATUSCODES 250...

...2v15rsQAAdP1VAQ:2>: Error: mkdir(/var/vmail//rodeo/Maildir) failed: Permission denied (euid=1000(rodeo) egid=1000(rodeo) missing +w perm: /var, dir owned by 0:0 mode=0755) May 16 00:16:03 lmtp(rodeo)<45419><iDyPNMV2v15rsQAAdP1VAQ:2>: Error: lmtp-server: conn unix:pid=95104,uid=0 [1]: rcpt rodeo: Mailbox INBOX: Failed to autocreate mailbox: Internal error occurred. Refer to server log for more information. [2020-05-16 00:16:03] May 16 00:24:55 master: Warning: Killed with signal 15 (by pid=0 uid=0 code=kill) May 16 00:27:47 lmtp(rodeo)<20665><zVcqLZV5v165UAAAdP1VAQ:2>: Er...

I have a situation where my LMTP RCPT TO: goes to a mailbox user account that does not reflect either the final (through aliasing) or envelope email address. SMTP RCPT TO: (envelope-local-part at envelope-domain) Final Recipient: (final-local-part at final-domain) LMTP RCPT TO: (mailbox-local-part at mailbox-domain) I'd lik...

...out having to duplicate the user database (it is explained here: http://wiki2.dovecot.org/LDA/Postfix ) I set up LMTP so that postfix uses the socket provided by dovecot, and it works. Only I get the following error message in the logs: Feb 10 18:05:53 ashley postfix/smtpd[9298]: NOQUEUE: reject: RCPT from mail-wi0-f179.google.com[209.85.212.179]: 450 4.1.1 <mildred at mildred.fr>: Recipient address rejected: unverified address: host mail.mildred.fr[private/dovecot-lmtp] said: 550 5.1.1 <mildred at mildred.fr> User doesn't exist: mildred at mildred.fr(in reply to RCPT TO command)...

...unctional. destination server is not accepting from any relay host. can anyone try from his server and see if it is deliverable to ray at tata-nigeria.com Thanks / Regards Prabhpal S. Mavi Apr 12 11:06:00 titan postfix/qmgr[11860]: C3C142E4012: from=<****@digital-infotech.net>, size=1391, nrcpt=1 (queue active) Apr 12 11:06:02 titan postfix/smtp[12039]: C3C142E4012: host mx2.servershost.net[205.234.223.160] said: 450 4.1.7 <****@digital-infotech.net>: Sender address rejected: unverified address: host mail.digital-infotech.net[41.211.25.193] said: 450 4.7.1 Client host rejected: cann...

...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 local-part spec has changed. :) > > [ ... ] > >> MAIL FROM:<test at testdomain.com>\r\n >> RCPT TO:<deemzed.uk+Junk E-mail>\r\n >> >> 501 5.5.4 Invalid.parameters\r\n > > That recipient address is totally invalid. It is neither just a local > part without a domain, nor a plussed address destination. > > Check your setup with i.e. > > RCPT TO:<&quot...

Bernhard Schmidt <berni at birkenwald.de> wrote: Hi, > Axel Luttgens <AxelLuttgens at swing.be> wrote: > > Hi Axel, > >> Le 11 f?vr. 2014 ? 08:34, Bernhard Schmidt a ?crit : >> >>> [...] >>> so Dovecot should reject in RCPT TO phase, but according to the logs of the >>> upstream Postfix it does so after END-OF-DATA >>> >>> (host xxx[2001:xxx] said: 452 4.2.2 >>> <user at domain.de> Quota exceeded (mailbox for user is >>> full) (in reply to end of DATA command)) >...

...l result_internalfail = return-fail } } lmtp.ext: password_query = SELECT 'y' AS proxy, NULL AS password, 'y' AS nopassword FROM users WHERE userName='%Ln' from exim -> director LMTP network dump: MAIL FROM:<test at testdomain.com>\r\n RCPT TO:<"deemzed.uk+Junk E-mail"@mailbox.localhost>\r\n DATA\r\n (etc) .\r\n 501 5.5.4 Invalid parameters\r\n QUIT\r\n from director -> dovecot LMTP network dump: MAIL FROM:<test at testdomain.com>\r\n RCPT TO:<deemzed.uk+Junk E-mail>\r\n 501 5.5.4 Invalid.parameters...

...The following addresses had permanent fatal errors ----- <acardi at cs.com> <adorablealicia at cs.com> <aclaudet at cs.com> <acarter5 at cs.com> <acrader at cs.com> ? ?----- Transcript of session follows ----- ... while talking to air-yg01.mail.aol.com.: >>> RCPT To:<acrader at cs.com> <<< 550 MAILBOX NOT FOUND 550 <acrader at cs.com>... User unknown >>> RCPT To:<acarter5 at cs.com> <<< 550 MAILBOX NOT FOUND 550 <acarter5 at cs.com>... User unknown >>> RCPT To:<aclaudet at cs.com> <<&lt...

...(I compared with the source from > https://dovecot.org/releases/2.3/dovecot-2.3.0.1.tar.gz). > > https://github.com/dovecot/core/commit/2bf919786518d138cc07d9cc21e14ad5e07e5e56#diff-7964e00c46515956a959fa47fc86d605 > > I also noticed a similar construct being used on line 465 > (rcpt->rcpt.rcpt->path) that was causing the segfault on the above > commit on line 136. > > struct smtp_address *rcpt_to = rcpt->rcpt.rcpt->path; > > Should that also use rcpt->rcpt.path; ? > > Thanks from the other side of the gulf! > Reio > I now managed to...

...example.com quota_rule=*:bytes=1024000000 mail_crypt_global_private_key=LS0tLS1CRUd.....LS0tLS0K mail_crypt_global_public_key=LS0tLS1CRUd.....LS0tCg== mail_crypt_save_version=2) lmtp(someone at example.com)<248><e2dcD6TuumP4AAAALzF/Qw>: Debug: lmtp-server: conn 172.17.0.1:6376 [1]: rcpt someone at example.com: Added userdb setting: plugin/mail_crypt_global_private_key=LS0tLS1CRUd.....LS0tLS0K imap(someone at example.com)<247><WlggG8PxEOvAqDEB>: Debug: duplicate db: Initialize lmtp(someone at example.com)<248><e2dcD6TuumP4AAAALzF/Qw>: Debug: lmtp-server:...

...be made. 3. The third problem is then re-encoding the username in the envelope recipient when proxying, which was not done at all. I've added a function lmtp_client_rfc822_escape_address(), which is similar to str_append_maybe_escape() to escape the address at protocol time in lmtp_client_send_rcpts() [src/lib-smtp/lmtp-client.c], although I suspect it should be done earlier, this is just a working proof. The other reason I don't believe this patch is production quality is that I have not examined any interaction between these changes and sieve's use of the envelope recipient. I'...

...++ logcheck-postfix 2004-06-21 20:10:32.000000000 +0100 @@ -1,4 +1,8 @@ ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postfix/smtpd\[[0-9]+\]: warning: [^[:space:]]+: hostname [^[:space:]]+ verification failed: Host not found$ ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postfix/smtpd\[[0-9]+\]: [[:alnum:]]+: reject: RCPT from [^[:space:]]+: [0-9]+ Client host rejected: cannot find your hostname, [^[:space:]]+; from=[^[:space:]]+ to=[^[:space:]]+ proto=(ESMTP|SMTP) helo=[^[:space:]]+$ +^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postfix/smtpd\[[0-9]+\]: [A-Z0-9]+: reject: RCPT from [^[:space:]]+: [45][0-9][0-9] <[^[:space...

...hole setup works perfectly fine with the > latest version of dovecot 2.2 > > The problem only exists if the quota of the user is full, every other > message gets delivered without a problem, and the lmtp process change > back to READY state. But in this case, it stays in the "RCPT TO? > forever. I?ve talked to ?cmouse? today on the IRC and he recommended > continue here. > > kdump and lmtp debug logs: https://pastebin.com/raw/MSVcj6qN?&?And > from the backend I only have a tcpdump from another process but it's > always the same behaviour: https:...

...at are used for the tests. However, it pointed out my problem quite clearly. > Thank you for this. Actually, after many hours of head-bashing, I discovered the problem. sieve doesn't work when you're just using telnet port 25 ! I was doing : ehlo test mail from:sender at example.com rcpt to:recip at example.com data Subject: hello world Hello World ! . With the above, sieve was simply sending everything to INBOX When I changed my methodology : ehlo test mail from:sender at example.com rcpt to:recip at example.com data From:<sender at example.com> To:<recip at example.com...

...y write a rule to match that logentry and put it in a file called my_rules in /etc/logcheck/ignore.d.server/ ... that worked perfectly fine. Until that rule: Logcheck keeps reporting me that: Security Events =-=-=-=-=-=-=-= Mar 16 15:45:48 uhweb64206 postfix/smtpd[21799]: NOQUEUE: reject_warning: RCPT from unknown[220.231.197.4]: 504 5.5.2 <220.231.197.4>: Helo command rejected: need fully-qualified hostname; from=<lory9 at syssrc.com> to=<diequeen at klappspaten.info> proto=ESMTP helo=<220.231.197.4> So I wrote this rule: ^\w{3} [ :0-9]{11} [._[:alnum:]-]+ postfix/smt...

...aving the same issue. The whole setup works perfectly fine with the latest version of dovecot 2.2 The problem only exists if the quota of the user is full, every other message gets delivered without a problem, and the lmtp process change back to READY state. But in this case, it stays in the "RCPT TO? forever. I?ve talked to ?cmouse? today on the IRC and he recommended continue here. kdump and lmtp debug logs: https://pastebin.com/raw/MSVcj6qN <https://pastebin.com/raw/MSVcj6qN> & And from the backend I only have a tcpdump from another process but it's always the same behaviou...

Hi I tried to get some logs: https://pastebin.com/Z8xVzpzW As you can see the process isn't shutdown and still in transaction as long dovecot is running. It destroyed the transaction when I stopped Dovecot. And this behavior only happens when the mailbox of user is full... Any Ideas how to debug this correctly? > So far, I haven't been able to reproduce anything weird at this end.

...s stays open forever and never closes. So after a few hours, we hit the LMPT-Process limit.? The problem only exists if the receiving Dovecot reports "Quota exceeded (mailbox for user is full)" back to the Exim. If this is the case the state on the LMPT process stays at "lmtp: [_IP_ RCPT TO] (lmtp) and never closes. The TCP-Connection to the Exim is then in CLOSE_WAIT state on the Proxy. On the receiving Dovecot we set the "lmtp_rcpt_check_quota=yes" option. For me, it sounds similar to this bug:?https://dovecot.org/list/dovecot/2018-January/110697.html?but without the SE...