Hi all,
What specifically does this flag do?
Does it affect what happens:
--
- when the drive is full?
- when the system user’s disk quota is full?
- when the mailbox’s quota is full?
--
Also, does it work with both LDA and LMTP?
I don’
> On 29 Jan 2015, at 14:53, Bernhard Schmidt wrote:
>
> - In 2.2.9 and 2.2.13 lmtp_rcpt_check_quota is ignored
> - In 2.2.15 lmtp_rcpt_check_quota works, but quota_full_tempfail is
> ignored at the RCPT TO stage. It still works at the DATA stage, so
> disabling lmtp_rcp
6 (4b9b9a88ac9b)
> # OS: Linux 3.2.0-4-amd64 x86_64 Debian 7.8
>
> -> MAIL FROM:
><- 250 2.1.0 OK
> -> RCPT TO:
><** 552 5.2.2 Quota exceeded (mailbox for user is full)
>
> But as you can see, the setting for quota_full_tempfail is now ignored.
> It sho
h LMTP (i.e. because it was generated on a server
> that doesn't check quota-status), it is deferred in LMTP in the
> END-OF-DATA phase, not in RCPT TO as expected.
To follow up here:
Dovecot 2.2.13 (from Debian testing compiled on wheezy) is still showing
the same behaviour as 2.2.9. lmtp_rcpt_check_quot
On Fri, 2008-05-02 at 13:35 +0200, Ulrich Zehl wrote:
> Now that the intial confusion is cleared up, I'd like to propose the
> following patch which changes deliver's -e flag behavior to also include
> the error message when TEMPFAILing.
> This is useful in setups like mine where deliver is called
On Wed, Apr 30, 2008 at 05:53:37PM +0200, Johannes Berg wrote:
>
> > The lines in question (in src/deliver/deliver.c) read:
> > | 1003 if (error != MAIL_ERROR_NOSPACE ||
> > | 1004 getenv("QUOTA_FULL_TEMPFAIL") != NULL) {
> [...]
>
> Hence, what happ
> The 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?
N
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
