-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On Thu, 21 Mar 2019, Yassine Chaouche via dovecot wrote:
On 3/21/19 4:13 PM, Aki Tuomi via dovecot wrote:
On 21 March 2019 17:05 Yassine Chaouche via dovecot
wrote:
[...]
While not very intuitive, I have :
mail_home = /var/mail/vmail/%d/%n/dovec
Thanks for the help.
This did solve my problem, and created a little hiccup.
Namely, all the users that had email account LOST their mail. I am just
starting migrating to this new mail server setup, so mostly just
insignificant testing emails.
I am sure there is a way to recover the old mails? D
Well,
so the right syntax (in my case) would be:
-o smtpd_recipient_restrictions =
reject_non_fqdn_recipient,reject_unknown_recipient_domain,permit_sasl_authenticated,reject,check_policy_service
inet:mailstore.example.com:12340
right??
I configured it before the "permit_sasl_authenticated" an
On 21 Mar 2019, at 10:51, Ralph Seichter via dovecot
wrote:
> * lty via dovecot:
>
>> foxmail will not have next step after sending {LIST "" *} command
>> action.
>
> Can you please stop this now? If Foxmail is broken, Foxmail needs to be
> fixed, not some kludges added to well-behaving Dovecot
* Rodolfo Gonzalez via dovecot:
> I just have a doubt in the technical side: is it safe to have the
> email in EFS?
"Safe" as in "storing and retreiving will work"? Probably.
I would not do it for privacy reasons, unless all data was encrypted on
a machine before storing it in any service operat
* lty via dovecot:
> foxmail will not have next step after sending {LIST "" *} command
> action.
Can you please stop this now? If Foxmail is broken, Foxmail needs to be
fixed, not some kludges added to well-behaving Dovecot.
-Ralph
On 3/21/19 4:13 PM, Aki Tuomi via dovecot wrote:
On 21 March 2019 17:05 Yassine Chaouche via dovecot wrote:
[...]
While not very intuitive, I have :
mail_home = /var/mail/vmail/%d/%n/dovecot
mail_location = maildir:~/..
Which works for me ^^'
Yassine.
Except it would have the same problem,
> On 21 March 2019 17:05 Yassine Chaouche via dovecot
> wrote:
>
>
> On 3/21/19 3:57 PM, Aki Tuomi via dovecot wrote:
> > This because you have a very common misconfiguration, which is that your
> > mail_home and mail_location are pointing to same directory, and that lead
> > into this pro
On 3/21/19 3:57 PM, Aki Tuomi via dovecot wrote:
This because you have a very common misconfiguration, which is that your
mail_home and mail_location are pointing to same directory, and that lead into
this problem.
Solution is of course to use:
mail_home = /var/mail/vmail/%d/%n
mail_location
This because you have a very common misconfiguration, which is that your
mail_home and mail_location are pointing to same directory, and that lead into
this problem.
Solution is of course to use:
mail_home = /var/mail/vmail/%d/%n
mail_location = maildir:~/Mail
Aki
> On 21 March 2019 16:48 E
Hello,
Config infos below.
Short version, I am getting this weird anomaly on my main email
account. Such that, "dovecot.sieve" is showing up as a mailbox in my
various email clients (e.g. k-9 (mobile), and Evolution).
I have tried deleting the "rogue folder" with doveadm, but it just
returns.
On 20 Mar 2019, at 23:33, Rodolfo Gonzalez via dovecot
wrote:
> AWS released one month ago a EFS system with administered life cycle, which
> means that files not accessed in the last 30 days are moved to a lower cost
> storage tier. Currently I hold my e-mail, delivered to Maildir++ folders by
> On 20 Mar 2019, at 18.17, Tom Sommer via dovecot wrote:
>
>
> On 2019-03-20 16:40, Sami Ketola via dovecot wrote:
>
>>> On 20 Mar 2019, at 17.13, Tom Sommer via dovecot
>>> wrote:
>>> I realize quota-service on Director is not supported, which is a shame.
>>> As a workaround I'm thinking
> On 21 Mar 2019, at 10.08, lty via dovecot wrote:
>
>
> Yes,
> Foxmail for mac client, after dovecot upgrade from 2.1.17 to new version,
> imap can't receive any email, I perform packet capture test, foxmail will not
> have next step after sending {LIST "" *} command action.
>
> Foxmail f
From: Urban Loesch
Hi,
Well,
so the right syntax (in my case) would be:
-o smtpd_recipient_restrictions =
reject_non_fqdn_recipient,reject_unknown_recipient_domain,permit_sasl_authenticated,reject,check_policy_service
inet:mailstore.example.com:12340
right??
I configured it before the "per
Yes,
Foxmail for mac client, after dovecot upgrade from 2.1.17 to new
version, imap can't receive any email, I perform packet capture test,
foxmail will not have next step after sending {LIST "" *} command
action.
Foxmail for mac client, dovecot version 2.1.17 can receive imap mail
normally, b
On 21 Mar 2019, at 6.22, lty via dovecot wrote:
>
> dovecot version
>
> v2.2.29
>
> v2.2.36
>
> v2.3.5
>
> LIST "" * The returned mailbox does not display quotes
>
> v2.1.17
> LIST "" * The returned mailbox shows quotation marks
>
> Why is the quotation mark removed in the new version?
>
17 matches
Mail list logo
