search for: tempfails

I briefly got some mails delivered, but not anymore. Attached are dovecot-info.log, dovecot-debug.log, dovecot.log, maillog, /etc/mail/passwd smtpd.conf, vaddr, vusers, vdomains Thanks for any help. Chris Bennett -------------- next part -------------- May 15 12:54:25 master: Error: service(config): pipe() failed: Too many open files May 15 12:54:25 master: Error: service(auth): pipe() failed:

...e lines in question (in src/deliver/deliver.c) read: | 1003 if (error != MAIL_ERROR_NOSPACE || | 1004 getenv("QUOTA_FULL_TEMPFAIL") != NULL) { Does this mean that the corresponding block gets executed whenever quota_full_tempfail is set? If so, setting it transforms all errors into TEMPFAILs, and not only those relating to quota/space issues. I think dovecot-example.conf should at least mention this it's inteded; otherwise, the code should be changed (I'm not completely sure what Timo's intensions are, so I won't comment on possible solutions). Regards, Ulrich PS: All...

Hallo list, I was having quite a hard time configuring dovecot on OpenBSD -current. The problem was default Maildir setting in 10-mail.conf, namely: mail_location maildir:~/Maildir was unable to locate user's home directory. As far as I can remember, it was the correct setting on OpenBSD-current a week or two ago. Once I figured out and changed it to mail_location

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

Hello dovecot-users, I have a question/suggestion regarding the submission_host feature of the lda (either via dovecot-lda binary or lmtp) in combination with sieve. When trying to deliver message to a mailbox and this message has a sieve redirect action applied to it, dovecot is using the configured smtp server to forward the message just fine. Unfortunately, if the server configured for

Hi, Since updating to 2.3.1 on my FreeBSD mailserver mail delivery using lda is broken if I have sieve enabled. (Before updating this was 2.2 and pigeonhole 0.4) FreeBSD 11.1-p8 amd64 Dovecot 2.3.1 Pigeonhole 0.5.1 Mailflow is OpenSMTPd as MTA, using mda delivery to rspamc which utlimately delivers using dovecot-lda. smtpd.conf deliver to mda "rspamc -h scan --mime -e

I'm new to Dovecot, using 1.1.8 and I just wanted to verify that what I am observing is the intended behavior. I'm using Maildir++ quota. When a message is delivered to a mailbox that cannot accept the message because it would place them over the quota limit, deliver states to the MTA that the messsage was delivered successfully (example using postfix): Jan 17 12:05:31 msa

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 no mode is specified, it defaults to "default", which is the current behaviour. In sendmail mode, mail_send_rejection() simply prints the r...

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

On 17 May 2020, at 11:08, Chris Bennett <chris-dvcot at freedomforlife.rocks> wrote: > > I realize that I dumpimg a lot of info out there. 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

I'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?

http://dovecot.org/releases/2.1/dovecot-2.1.11.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.11.tar.gz.sig * lmtp/lda: dovecot.index.cache file is no longer fully mapped to memory, allowing mail deliveries to work even if the file is huge. * auth: userdb passwd lookups are now done by auth worker processes instead of auth master process (as it was

http://dovecot.org/releases/2.1/dovecot-2.1.11.tar.gz http://dovecot.org/releases/2.1/dovecot-2.1.11.tar.gz.sig * lmtp/lda: dovecot.index.cache file is no longer fully mapped to memory, allowing mail deliveries to work even if the file is huge. * auth: userdb passwd lookups are now done by auth worker processes instead of auth master process (as it was

St?phane Cottin writes: >> You're stilling going to lose contents. If dspam fails, the 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.

I tried searching this list, but couldn't find anything related to inode limits except for linux quotas. I wanted to add sieve support for our users, so was attempting to get our email system to use dovecot's deliver lda to handle email, instead of postfix's virtual lda, using maildir mailstore. When I did this, I noticed that emails would get stuck in the queue if a user was

Hi all, Reverted back to 2.2.34 and pigeonhole 0.4.22 and (after reverting config changes) it's working again including Sieve. I was notified of commit https://github.com/stephanbosch/dovecot-core/commit/6553f20bb31b5f0eebb73a0db526f00816b47d71 which I'll try. It's in a different option -f (not -d) but will try. Cheers, Bernard. 2018-04-08 20:10 GMT+02:00 Bernard Spil <brnrd at