Morikawa-san,
Your conf is wrong.
Should be:
quota_warning = storage = 95 %% quota-warning 95 %u
Your conf:
quota_warning = storage = 95 %% quota-warning 95% u
There's a space between % and u.
First of all, try the above and let us know if it changes.
Kouga
-Original Message-
Hi,Kouga-san
When quota-warning works normally
I'm sending an email to "From: to =
"
When it doesn't work
An email was sent to "From: to =
"
"Recipient address rejected: User unknown in local recipient table"
It will be.
cat /etc/dovecot/conf.d/90-quota.conf
And which email clients can do this?
A defacto standard needs to be adopted. If I don't provide SPF or DKIM, I am
likely to be deemed spammy, hence a defacto standard has been established. I
don't see this with TOTP.
I'm all for TOTP, but I'm not going to code my own.
Hi, all.
we use quota-warning emails to notify you of quotas.
In rare cases, the email address has changed to the logged-in user.
(Because the address of %u is passed as the logged-in user.)
So I couldn’t send the email with “Recipient address rejected: User
unknown in local recipient table”.
>>Whatever Gmail wants is essentially a defacto standard.
Gmail have solved it with a Oauth authorization scheme. Basically, first time
setting up mail, you are asked to authenticate by 2FA in a webview, then a
shared secret is established, that is used during SMTP and IMAP time.
Both Hotmail
I would have to also hack the email client since I don't enter my 20 character
high entropy password when I send or retrieve email.
You really need an email standard to integrate TOTP. To be realistic, you need
Gmail to use it. Whatever Gmail wants is essentially a defacto standard. I live
in
On Tue, 27 Oct 2020, Sebastian Nielsen wrote:
Kind of stupid that there doesn't exist some common standard for 2FA that
works in email clients.
You can bodge it for HOTP/TOTP hardware token generators. Dovecot allows
custom plugins to check passwords. The plugin can take passwords of
the
On 10/25/20 6:02 AM, Arjen de Korte wrote:
>
> # SSL/TLS support: yes, no, required.
> ssl = no
>
> !include_try 10-ssl.conf.ext
Thank you very much. This did exactly what I needed.
On Mon, Oct 19, 2020 at 12:08:05AM +0200, Piotr Auksztulewicz wrote:
> On Sun, Oct 18, 2020 at 11:14:26PM +0200, John Fawcett wrote:
> > can you check if the missing emails are in the new directory on host B?
>
> I cannot now. I did not think about that possibility when listing the
> contents of
> "lists" == lists writes:
lists> Ditto this. I pay for a VPS because I don't want my home facing
lists> the internet. If the VPS gets hacked, that is as far as they
lists> get.
Same here, I do this as well.
lists> You could do a mail server on a $5 Digital Ocean or Linode VPS
lists> if
>>EU have very strict laws on the security of email and the requirement to
keep it archived and to ensure the data cannot get out.
No.
GDPR is very organization-specific, meaning that a small organization or
non-profit with 5 employees, don't need the same security as a 100 employee
On 10/27/20 7:52 PM, Stephan Bosch wrote:
>
>
> On 27/10/2020 11:32, Gedalya wrote:
>> Hello,
>>
>> The documentation says imapsieve_url "has no effect on the
>> administrator-controlled Sieve scripts". However, when setting this item, I
>> get lines such as:
>>
>> Error: imapsieve: mailbox
1: I meant like this:
Without whitelisting, you can't login to SMTP or IMAP, password isn't valid
at all.
To enable SMTP and IMAP, you then either surf ro webmail, or the 2FA
gateway, and login with:
Username + password + 2FA code + captcha.
When all is valid, then your IP is whitelisted for
> On 26 Oct 2020, at 09:11, R. Diez wrote:
>
>>>
>>> I would not advice any company that is continuously being fined for
>>> breaking the law.
>
>> This is not only an overstatement, it is completely irrelevant. Given the
>> OP problem
>> statement (small business, part-time admin,
>> Running an unmaintained mail server is a BAD thing.
Of course. You maintain it.
>>I think you are confusing gmail and google apps (or whatever it is called
now, seems to change all the time).
Google apps uses the same restrictions. What I recall, you can disable SPF
and DKIM checks for
On 25 Oct 2020, at 22:51, Sebastian Nielsen wrote:
>>> why not just point them at a hosting service like google apps, and let
>> google keep things up to date?
>
> Costs money,
Yes. That is a *good* thing. Running an unmaintained mail server is a BAD thing.
> and also the problem is that gmail
On 25 Oct 2020, at 22:47, Sebastian Nielsen wrote:
> The second way, is to not have webmail at all, but instead have a
> authentication gateway in browser, where you must auth with 2FA and captcha.
> The only purpose of this gateway, is to authenticate users with 2FA before
> their IP is
Hello,
The documentation says imapsieve_url "has no effect on the
administrator-controlled Sieve scripts". However, when setting this item, I get
lines such as:
Error: imapsieve: mailbox INBOX: Failed to read /shared/imapsieve/script
mailbox attribute: Mailbox attributes not enabled
and
On 26 Oct 2020, at 21:04, Stephan Bosch wrote:
> On 23/10/2020 13:22, @lbutlr wrote:
>> On 22 Oct 2020, at 19:09, Stephan Bosch wrote:
>>> You need to include the extprograms plugin:
>> I have, and vnf.dovecot.pipe doesn't give the error.
>>
>> sieve_plugins = sieve_imapsieve
On 10/27/2020 7:56 AM, Aki Tuomi wrote:
On 27/10/2020 14:49 jayare-dcml at outlook.com wrote:
On 26/10/2020 19:25, John Fawcett wrote:
On 25/10/2020 17:19, jayare~dcml at videocoding.org wrote:
I've got a basic dovecot master-master replication setup between two
servers (imap1 and imap2).
> On 27/10/2020 14:49 Justin Ridge wrote:
>
>
> On 26/10/2020 19:25, John Fawcett wrote:
> > On 25/10/2020 17:19, jayare~dcml at videocoding.org wrote:
> >> I've got a basic dovecot master-master replication setup between two
> >> servers (imap1 and imap2). Actions such as deleting messages
> On 27/10/2020 14:49 Justin Ridge wrote:
>
>
> On 26/10/2020 19:25, John Fawcett wrote:
> > On 25/10/2020 17:19, jayare~dcml at videocoding.org wrote:
> >> I've got a basic dovecot master-master replication setup between two
> >> servers (imap1 and imap2). Actions such as deleting messages
On 26/10/2020 19:25, John Fawcett wrote:
> On 25/10/2020 17:19, jayare~dcml at videocoding.org wrote:
>> I've got a basic dovecot master-master replication setup between two
>> servers (imap1 and imap2). Actions such as deleting messages or moving
>> them between folders are replicated correctly
On 22/10/2020 10:23, John Fawcett wrote:
> On 21/10/2020 19:00, John Fawcett wrote:
>> On 21/10/2020 16:44, Patrik Peng wrote:
>>> On 16.10.20 18:34, Patrik Peng wrote:
On 16.10.20 18:00, Scott Q. wrote:
> This reminds me, the way I was able to reproduce this consistently
> was by
On 27/10/2020 11:32, Gedalya wrote:
Hello,
The documentation says imapsieve_url "has no effect on the administrator-controlled
Sieve scripts". However, when setting this item, I get lines such as:
Error: imapsieve: mailbox INBOX: Failed to read /shared/imapsieve/script
mailbox attribute:
Not sure what happens if you do that with Sieve refilter (UID FILTER) command
with imapc.
Are you sure you want to use imapc and not something like fetchmail here
instead?
Aki
> On 27/10/2020 11:52 David Tildesley wrote:
>
>
> Hi Aki ,
>
> I need to Sieve to match the message headers
Hi Aki ,
I need to Sieve to match the message headers TO, CC, BCC against a list of
email addresses. If it gets a match, I want Sieve to set the x-original-to
header to that email address (I think I can do that with Sieve extension).
Is this doable?
Thanks,David.
On Tuesday, 27 October
imap proxy is a "dumb proxy", it will just pass everything to google & back
after you've authenticated.
imapc allows you to use imap sieve to some extent. I'm not sure what kind of
Sieve manipulations you have in mind.
Aki
> On 27/10/2020 11:42 David Tildesley wrote:
>
>
> Hi Aki,
>
>
Hi Aki,
Thanks. I didn't know that about imapc - but by the way, I finally got it
working.
The reason why I am inserting Dovecot between my (single) client and our
Exchange server (eventually - I am still testing against imap.gmail.com) is to
that I can manipulate the email with Sieve due to
You know that imapc != imap proxy.
imapc is a thin client, which is a "mail storage provider" like maildir.
imap proxy is when you proxy the connection somewhere. this is done with proxy_
settings in passdb.
You need to specify
ssl_client_ca_dir = /etc/ssl/certs
to get cert verification
I solved that certificate problem (temporarily) by disabling cert check.
But now I get the following more obscure error:
Error: Couldn't drop privileges: User is missing UID (see mail_uid setting)
On Tuesday, 27 October 2020, 09:55:28 pm NZDT, David Tildesley
wrote:
I have solved the
I have solved the port problem by specifying it in the passdb section as
userdb_imapc_port=993
But:This is in the error log when I make a connection from the client:
Oct 27 08:49:16 imapproxy01 dovecot: auth: Fatal: passdb imap: Cannot verify
certificate without ssl_ca_dir or ssl_ca_file
@imapproxy01:/etc/dovecot/conf.d$ dovecot -n# 2.3.7.2 (3c910f64b):
/etc/dovecot/dovecot.conf# Pigeonhole version 0.5.7.2 ()# OS: Linux
5.4.0-1031-azure x86_64 Ubuntu 20.04.1 LTS# Hostname:
imapproxy01.trf04sdec2hu1b4wur4lazeo3f.px.internal.cloudapp.netauth_verbose =
> On 27/10/2020 10:08 David Tildesley wrote:
>
>
> Hi,
>
> Dovecot v2.3.7.2 on Ubuntu 18.04LTS
>
> I have configured for imap proxy to imap.gmail.com
>
> However whilst the imapc_host setting is working, imapc_port is not - it
> ignores the value I set and dovecot always tries to connect
Hi,
Dovecot v2.3.7.2 on Ubuntu 18.04LTS
I have configured for imap proxy to imap.gmail.com
However whilst the imapc_host setting is working, imapc_port is not - it
ignores the value I set and dovecot always tries to connect to gmail on port
143 (as per error log output).
I have the imapc
35 matches
Mail list logo
