On 2021-07-29 21:34, Christoph Haas wrote:
Noel:
The only solution is to reject all mail for an over-quota recipient
during recipient restrictions, and if the mail passes that stage,
deliver it anyway even if it makes the user go over quota.
Seconded. Is that possible with the current
On 29-07-2021 21:33, Mart Pirita wrote:
Hi,
This is very bad news.
I don't think that disto is old, if I can compile almost every software
with it.
If that CentOS distro is EOL and/or you can't even find the source rpms
to compile/rebuild them to retrofit patches addressing security
Hello,
When working with director, the state of the backend nodes are not
checked by Dovecot. The state always remains as "up". I understand that
there are external applications documented that monitor backend nodes,
and changes the state of them to "down" if they become unresponsive. The
Am 29.07.21 um 22:08 schrieb Benny Pedersen:
On 2021-07-29 20:13, Christoph Haas wrote:
I really wouldn't want to script my own policy daemon just to avoid
backscatter. :(
why not ? :=)
I'm considering it. But I still hope that I'm doing something wrong or
that Dovecot's plugin can be
On 2021-07-29 20:13, Christoph Haas wrote:
I really wouldn't want to script my own policy daemon just to avoid
backscatter. :(
why not ? :=)
quota grace is ideal with same size as max mailsize in postfix, with is
10MB as standard, the quota grace ensure one mail is possible to be sent
if
On 7/29/2021 2:44 PM, dove...@ptld.com wrote:
The only solution is to reject all mail for an over-quota recipient
during recipient restrictions, and if the mail passes that stage,
deliver it anyway even if it makes the user go over quota.
But does this happen out of the box? Wont dovecot end
The only solution is to reject all mail for an over-quota recipient
during recipient restrictions, and if the mail passes that stage,
deliver it anyway even if it makes the user go over quota.
But does this happen out of the box? Wont dovecot end up back splatter
bouncing one of the recipients
In the sieve plugin settings i have
plugin {
...
sieve_user_email = %u
}
Variables pages says
%u = full username (e.g. user@domain)
This config seems to work in practice, the email is from: the users
email address.
However on starting dovecot im getting a warning twice:
Noel:
The only solution is to reject all mail for an over-quota recipient
during recipient restrictions, and if the mail passes that stage,
deliver it anyway even if it makes the user go over quota.
Seconded. Is that possible with the current quota-status?
…Christoph
On 7/29/2021 2:15 PM, dove...@ptld.com wrote:
Plus Dovecot complains that the policy service is only supposed
to be
used in the RCPT stage. So clearly this is a bad approach.
I want to explore this more. I tried it and also see:
dovecot[1096]: quota-status(26164): Warning: Received policy
There isn't much documentation on quota_grace.
How would you disable quota grace?
quota_grace = 0
quota_grace = 0%
quota_grace = 0m
quota_grace = -1
Assuming "0" isn't an "unlimited" setting?
Plus Dovecot complains that the policy service is only supposed to be
used in the RCPT stage. So clearly this is a bad approach.
I want to explore this more. I tried it and also see:
dovecot[1096]: quota-status(26164): Warning: Received policy query from
MTA in unexpected state END-OF-MESSAGE
Am 29.07.21 um 20:13 schrieb dove...@ptld.com:
If you are not aware, dovecot has by default a 10% over quota grace. So
even being a couple of bytes over quota it would still accept a small
message.
I had set…
plugin {
quota_grace = 0
}
It sounds like a better approach would be to make Dovecot reject any
email no matter what the size is (even size=0) if a user is over
quota. I'll take further discussion to the dovecot mailing list then.
If you are not aware, dovecot has by default a 10% over quota grace. So
even being a
>> At least from Thunderbird, yes. But SIZE=… does not seem to be a
>> mandatory addition to the RCPT-TO line. Perhaps other mail clients do
>> not use SIZE either. Just guessting.
Correct. It's optional and can't be trusted anyway.
> http://www.postfix.org/SMTPD_POLICY_README.html
> The
and since dovecot does not know postfix virtual aliases is would make
sense dovecot also support postfix virtual aliases in dovecot quota
service
Why not? You can create a query telling dovecot to lookup the quota of
the mailbox the alias points to. Ofcourse your tables wont look like
mine
On 7/6/21 6:40 PM, Michal Soltys wrote:
Hi,
While I was checking old bug I once reported (that one seems to be
fixed, https://www.dovecot.org/list/dovecot/2017-January/106593.html) I
discovered another issue happening under current version when user
sharing his mailbox (with Maildir storage)
On 2021-07-29 02:44, dove...@ptld.com wrote:
Like you said when sending a real email it gets rejected right?
postfix can only check results from dovecot, not dictate that new mails
size is a real iso or other content, mta stage cant be made to hand over
size in policy server since email
Hello,
I'm testing the migration from and old dovecot server 2.2.24 to a new
one with 2.3.15 using this command:
doveadm -c /etc/dovecot/dovecot-migration.conf -o mail_fsync=never
backup -x "shared" -x "shared/*" -x "dovecot/sieve" -R -T 60 -u
andrea.gabellini...@telecomitalia.sm imapc:
> You can use Developer Toolset. It comes with newer GCC versions. I
> don't know the precise CentOS repository layout, but there is a
> devtoolset-7-gcc package somewhere.
SCL is included with CentOS, see:
https://www.softwarecollections.org/en/scls/rhscl/devtoolset-7/
At least from Thunderbird, yes. But SIZE=… does not seem to be a
mandatory addition to the RCPT-TO line. Perhaps other mail clients do
not use SIZE either. Just guessting.
http://www.postfix.org/SMTPD_POLICY_README.html
The "size" attribute value specifies the message size that the client
* Mart Pirita:
> So at the moment I have two choices, newer upgrade Dovecot or rollback
> the buffer_t changes and use latest version?
You can use Developer Toolset. It comes with newer GCC versions. I
don't know the precise CentOS repository layout, but there is a
devtoolset-7-gcc package
On Thu, 2021-07-29 at 14:33 +0300, Mart Pirita wrote:
> Hi,
>
>
> This is very bad news.
>
> I don't think that disto is old, if I can compile almost every
> software with it.
>
> So at the moment I have two choices, newer upgrade Dovecot or
> rollback the buffer_t changes and use latest
Hi,
This is very bad news.
I don't think that disto is old, if I can compile almost every software with it.
So at the moment I have two choices, newer upgrade Dovecot or rollback the
buffer_t changes and use latest version?
Mart
Timo Sirainen wrote:
> On 29. Jul 2021, at 7.21, Mart Pirita
On 29. Jul 2021, at 7.21, Mart Pirita wrote:
>
> Hello.
>
> So far I have successfully built Dovecot until v2.3.14 on Centos 4-6 (yes I
> know, they are old, but as they are remote servers, distros can't upgraded),
> and sometimes I have also met compilation issues, but after highlighting
>
Dne středa 28. července 2021 19:08:17 CEST, Dan Conway napsal(a):
> Yes Dovecot will proxy the connection to the real MTA. My question is
> why authentication is /always/ required on Dovecot when submission is
> used, as MTAs usually have an option to allow non-authenticated relaying.
I thought
Am 29.07.21 um 02:44 schrieb dove...@ptld.com:
- sending a test mail with SWAKS returns DUNNO
(swaks is an SMTP test tool)
the difference appears to be the "size=0" line that Postfix
sends if I use SWAKS.
Now im guessing, maybe because you are using a testing tool, maybe it is
not sending
27 matches
Mail list logo
