search for: tempfail

...-------------- May 17 05:09:11 cowboyup smtpd[41057]: cd9b5d88482434f5 mda delivery evpid=3704d7a5d0da3083 from=<chris at consulting-diy-construction.com> to=<rodeo at consulting-diy-construction.com> rcpt=<rodeo at consulting-diy-construction.com> user=vmail delay=2h50m40s result=TempFail stat=Error (temporary failure: "mail.lmtp: LMTP server error: 550 5.1.1 <rodeo at consulting-diy-construction.com> User doesn't exist: rodeo at consulting-diy-construction.com") May 17 05:13:27 cowboyup smtpd[41057]: cd9b5d8af87ce6f9 mda delivery evpid=ae7e98ffbb801f8b from=<...

Hi, while testing out dovecot 1.1, I found that when you set quota_full_tempfail = yes in dovecot.conf and use the deliver -e command line flag, no deferral reason is printed, thus breaking my fancy quota_exceeded_message. This appears to be because of the if() block in lines 1003-1009 in src/deliver/deliver.c, and should be easily fixable (if it is indeed a bug, and not inten...

...mail root dir in: ~/Maildir Nov 26 07:11:01 mail dovecot: lda(admin): Fatal: Invalid user settings. Refer to server log for more information. Nov 26 07:11:01 mail dovecot: lda(admin): Fatal: Invalid user settings. Refer to server log for more information. Nov 26 07:11:01 mail smtpd[9800]: delivery: TempFail for fbf36ef37c9c77b7: from=<root at mail.home.lan>, to=<root at mail.home.lan>, user=admin, method=mda, delay=5h40m36s, stat=Error (exited abnormally) Nov 26 07:11:01 mail smtpd[9800]: delivery: TempFail for 4bb3fc1714ae81fc: from=<root at mail.home.lan>, to=<root at mail.home....

Currently if saving to mailbox fails for any reason, the mail is saved to INBOX instead. Same if a Sieve redirect fails, the mail is saved to INBOX. I'm wondering if anyone actually prefers this behavior when the error is temporary? For example if some index file corruption was detected, the save will most likely succeed the next time it's attempted. Or if the redirect fails because the

...to find messages in their inbox. Also problems with the submission_host could very much be temporary and a little delay in delivering a message is better then putting it somewhere the user doesn't expect a message to be. Is there any way to change the behavior of dovecot or the sieve plugin to tempfail in case a message cannot be sent out? I know that with multiple sieve actions it gets more complicated as there could be corner cases were the first message can be sent via the submission server and another message produced by the same sieve script cannot. I'd love sieve to behave like this:...

...[6390]: smtp-in: Closing session 81939f0d30337a47 Apr 8 19:36:55 email dovecot: lda(user2)<21091><Ljv6JzdTylpjUgAAWr0fMA>: Panic: file message-address.c: line 147 (parse_angle_addr): assertion failed: (*ctx->parser.data == '<') Apr 8 19:36:55 email smtpd[6390]: delivery: TempFail for 9db769b13edef5a7: from=<user1 at example.org>, to=<user2 at example.net>, user=bernard, method=mda, delay=1s, stat=Error ("") Apr 8 19:36:57 email smtpd[6390]: smtp-out: Closing session 81939f0c09f5140b: 1 message sent. Apr 8 19:37:04 email dovecot: lda(user2)<21102&g...

...the mail is discarded (dropped). Then a bounce is created stating the mail was rejected: Your message to <test at example.com> was automatically rejected: Quota exceeded (mailbox for user is full). Question: is it possible (without changing code) to alter this to where deliver would instead tempfail or something. Somehow it seems wrong to me to tell the MTA that everything is good, and then silently discard messages - regardless of the fact dovecot creates a bounce. This is not necessarily ideal either, but I _am_ wondering if this is configurable or not. deliver(test at example.com): 2009-01...

Hi all! Just migrated out UW-IMAP installation to Dovecot and so far so good. Had small teething problems though which left me with one question. The scenario was that I have a set of public folders that are only needed by the main company group (gid = company). Then there are some external users as well, not directly in the company group. I set up the public mailbox with permissions 660,

With mdbox, what does dovecot lock when "pop3_lock_session(pop3): yes"? Specifically, I'm wondering if Dovecot LDA is able to deliver mail when a session is locked, if using mdbox, or if it will tempfail until the session is unlocked? Thanks, Ken -- Ken Anderson Pacific Internet - http://www.pacific.net

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I've put together an always tempfail & sendmail-like DSN report back patch. Because I don't know how to transform the rejection reason into sysexit.h codes, it always tempfails. The hooks are so that: a) config file setting: lda_mode = mode b) command line: deliver --mode mode where mode is default or sendmail. When...

Hi, Please I have a question: If my server is out of space (disk full) and the postfix is LDA, the new messages a deffered or refused,so postfix send 450 to sender ... But When I use dovecot (1.2.16) like LDA, postfix accept message (even there is no space), forward to dovecot, dovecot REFUSE the message and message is lost ! How can I solve this ? I don't want tu use quota and the disk

Lets try again, put wrong changelog to the mail. Sorry about this. https://dovecot.org/releases/2.3/dovecot-2.3.5.2.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.5.2.tar.gz.sig Binary packages in https://repo.dovecot.org/ ??? * CVE-2019-10691: Trying to login with 8bit username containing ??? ? invalid UTF8 input causes auth process to crash if auth policy is ??? ? enabled. This could be

Lets try again, put wrong changelog to the mail. Sorry about this. https://dovecot.org/releases/2.3/dovecot-2.3.5.2.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.5.2.tar.gz.sig Binary packages in https://repo.dovecot.org/ ??? * CVE-2019-10691: Trying to login with 8bit username containing ??? ? invalid UTF8 input causes auth process to crash if auth policy is ??? ? enabled. This could be

...But not what we need. doveconf -n postfix -n (or equivalent) What MTA you are using (postfix, etc) Errors in mail.log showing the failures. > I can shoot for system users, but I really want to get the virtual users > working. This is a bit of a project. user=vmail delay=2h50m40s result=TempFail stat=Error (temporary failure: "mail.lmtp: LMTP server error: 550 5.1.1 <rodeo at consulting-diy-construction.com> User doesn't exist: Probably your LMTP lookup is malformed, probably in your MTA. lmtp(rodeo)<45419><iDyPNMV2v15rsQAAdP1VAQ:2>: Error: mkdir(/var/vmail//r...

...m converting my system from mbox to Maildir one user at a time, and I'd like to disable access for the user I'm working on. Is there a way to tell Dovecot to lock out a specific user? Perhaps with a control file in the home directory? At the same time, how can I get sendmail+procmail to tempfail incoming messages for one user until I'm done?

...sses instead of auth master process (as it was documented, but accidentally didn't work that way). + lmtp: lmtp_rcpt_check_quota=yes setting checks quota on RCPT TO. - lmtp: After successful proxying RCPT TO, the next one to a nonexistent user gave tempfail error instead of "user not found". - lmtp proxy: Fixed hanging if remote server was down. - imap: Fixed crash when SEARCH contained multiple KEYWORD parameters. - doveadm: Various fixes to handling doveadm-server connections. - -i <instance name> para...

...sses instead of auth master process (as it was documented, but accidentally didn't work that way). + lmtp: lmtp_rcpt_check_quota=yes setting checks quota on RCPT TO. - lmtp: After successful proxying RCPT TO, the next one to a nonexistent user gave tempfail error instead of "user not found". - lmtp proxy: Fixed hanging if remote server was down. - imap: Fixed crash when SEARCH contained multiple KEYWORD parameters. - doveadm: Various fixes to handling doveadm-server connections. - -i <instance name> para...

...he mail >> is dumped, the LDA returns exit code 75, and the MTA will probably >> issue a bounce Email to the sender. > > from dovecot-lda man page : > > 75 A temporary failure. This is returned for almost all failures. See the log file for > details. (EX_TEMPFAIL) > > The mta keep the mail and retry delivery later, which is what I need. Ah, my mistake. But ... > I don't want to deliver email on dspam error, I prefer TEMPFAIL and > future retries, so I have a chance to fix the issue later without > loosing or deliver unprocessed mails...

...ueue if a user was over quota, this got fixed when I added in quota support, and set it up to check it using the line: quota = fs:User quota:user:inode_per_mail Now if a user excedes disk space via quota, it's bounced with a message. But if a user excedes their inode quota, it's still tempfail and hangs in the queue till it expires. I just wanted to know if anyone knows about this issue, if I made a stupid mistake or anything else, before I go digging into the source.

...session 81939f0d30337a47 > Apr 8 19:36:55 email dovecot: > lda(user2)<21091><Ljv6JzdTylpjUgAAWr0fMA>: Panic: file > message-address.c: line 147 (parse_angle_addr): assertion failed: > (*ctx->parser.data == '<') > Apr 8 19:36:55 email smtpd[6390]: delivery: TempFail for > 9db769b13edef5a7: from=<user1 at example.org>, to=<user2 at example.net>, > user=bernard, method=mda, delay=1s, stat=Error ("") > Apr 8 19:36:57 email smtpd[6390]: smtp-out: Closing session > 81939f0c09f5140b: 1 message sent. > Apr 8 19:37:04 email dovec...