similar to: v2.1.11 released

Displaying 20 results from an estimated 4000 matches similar to: "v2.1.11 released"

2015 Jan 29
2
quota_full_tempfail = yes broken with lmtp_rcpt_check_quota (was: Re: lmtp_rcpt_check_quota not working)
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 >>>
2012 Nov 27
6
v2.1.11 soon
Just to let you know: I'm planning on releasing v2.1.11 today/tomorrow. If you wish to get something fixed for it, ask quickly. :)
2012 Nov 26
1
lmtp_rcpt_check_quota working somewhere?
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hello, I'm running Dovecot v2.1 and enabled the lmtp_rcpt_check_quota option in conf.d/20-lmtp.conf, because I just found it in the sample config. Is this option working somewhere? When I have the option enabled, I get _no_ response in the RCPT TO phase, if the user is under quota. If I go on and enter the DATA keyword eventually, I get
2014 Feb 11
2
lmtp_rcpt_check_quota not working
Hi, Dovecot 2.2.9 (Debian package from backports) does not seem to respect lmtp_rcpt_check_quota # 2.2.9: /etc/dovecot/dovecot.conf # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.4 deliver_log_format = from=<%e>, size=%p, message-id=<%m>, status=%$ disable_plaintext_auth = no lmtp_rcpt_check_quota = yes mail_debug = yes mail_gid = mstore mail_location =
2020 May 17
3
Problems with userdb and mail deliveribility
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:
2019 Oct 05
2
LMTP-Process stays in RCPT TO state
Hi We tried to update our Dovecot Director-Ring to 2.3 (latest version) and had one problem/bug. When we try to deliver an email from Exim to a receiving Dovecot (2.3 latest) via the LMTP-Proxy the LMTP process 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
2012 Nov 09
1
Sieve puts incoming message into inbox on any problem with submission_host
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
2012 Apr 23
4
Latest 6.2 kernel is broken
I just kickstarted a new machine with the latest CentOS 6.2 files, including kernel 2.6.32-220.13.1.el6.x86_64. It came up without network interfaces. dmesg says: bnx2: Broadcom NetXtreme II Gigabit Ethernet Driver bnx2 v2.2.1 (Dec 18, 2011) alloc irq_desc for 36 on node -1 alloc kstat_irqs on node -1 bnx2 0000:01:00.0: PCI INT A -> GSI 36 (level, low) -> IRQ 36 bnx2 0000:01:00.0:
2018 Jul 09
2
v2.3.2.1 released
https://dovecot.org/releases/2.3/dovecot-2.3.2.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.2.1.tar.gz.sig v2.3.2 still had a few unexpected bugs: - SSL/TLS servers may have crashed during client disconnection - lmtp: With lmtp_rcpt_check_quota=yes mail deliveries may have sometimes assert-crashed. - v2.3.2: "make check" may have crashed with 32bit systems
2018 Jul 09
2
v2.3.2.1 released
https://dovecot.org/releases/2.3/dovecot-2.3.2.1.tar.gz https://dovecot.org/releases/2.3/dovecot-2.3.2.1.tar.gz.sig v2.3.2 still had a few unexpected bugs: - SSL/TLS servers may have crashed during client disconnection - lmtp: With lmtp_rcpt_check_quota=yes mail deliveries may have sometimes assert-crashed. - v2.3.2: "make check" may have crashed with 32bit systems
2015 Jan 13
0
[PATCH] Make Delivered-To optional
Hi, I've read at least one e-mail on this list about making delivered-to in lmtpd optional, but now I need this too, so I made a patch. The default remains as is now (enabled). Rationale: I would like to dsync users and I have catchall POP mailboxes (meaning: a single mailbox gets the mails for a lot of e-mail addresses). If I deliver the e-mails to Dovecot's lmtpd as the original
2018 Jul 10
1
v2.3.2.1 released
On 10 Jul 2018, at 10.40, Tom Sommer <mail at tomsommer.dk> wrote: > > On 2018-07-09 16:48, Timo Sirainen wrote: >> https://dovecot.org/releases/2.3/dovecot-2.3.2.1.tar.gz >> https://dovecot.org/releases/2.3/dovecot-2.3.2.1.tar.gz.sig >> v2.3.2 still had a few unexpected bugs: >> - SSL/TLS servers may have crashed during client disconnection >> - lmtp:
2012 Nov 16
2
Initial status notification not received
Hello, We have SLES-11 SP2 Xen VMs running dovecot as IMAP proxies. At VMs startup, dovecot almost always shows these errors: Nov 16 14:29:19 server dovecot: master: Dovecot v2.1.10 starting up (core dumps disabled) Nov 16 14:29:55 server dovecot: master: Error: service(anvil): Initial status notification not received in 30 seconds, killing the process Nov 16 14:29:55 server dovecot: master:
2018 Apr 08
5
lda fails in parse_angle_addr if sieve is enabled
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
2009 Jan 17
3
Dovecot discards mail over quota
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
2018 Mar 04
3
LMTP delivery segfaults when user is over quota.
Hello! I'm having crashes with LMTP delivery when user is over quota on the latest CentOS 7.4 with the latest Dovecot 2.3.0.1 from Dovecot repo. I see the issue has been fixed on January 17, but it doesn't seem to 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).
2019 Oct 06
0
LMTP-Process stays in RCPT TO state
On 05/10/2019 13:01, Pascal Christen via dovecot wrote: > > Hi > > > We tried to update our Dovecot Director-Ring to 2.3 (latest version) > and had one problem/bug. When we try to deliver an email from Exim to > a receiving Dovecot (2.3 latest) via the LMTP-Proxy the LMTP process > stays open forever and never closes. So after a few hours, we hit the > LMPT-Process
2012 Mar 20
1
mdbox and pop3 locking
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
2008 Apr 30
2
deliver: handling of quota_full_tempfail and -e
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 intended behavior).
2017 Oct 05
0
v2.2.33 release candidate released
https://dovecot.org/releases/2.2/rc/dovecot-2.2.33.rc1.tar.gz https://dovecot.org/releases/2.2/rc/dovecot-2.2.33.rc1.tar.gz.sig There are a couple more small changes still coming, but this should be very close to the final release. I'm especially interested in hearing if there are any problems with doveadm log proxying or with director. We've improved our automated director tests quite a