On Thu, 2022-01-06 at 04:46 +0100, John Fawcett wrote:
> It looks like a mismatch between your dovecot and postfixadmin
> password ARGON2I in dovecot and are using a MD5-crypt scheme in
> postfixadmin. Therefore when you set the password in postfixadmin it
> is saving the password with a different
On 06/01/2022 04:20, Ken Wright wrote:
On Thu, 2022-01-06 at 03:44 +0100, John Fawcett wrote:
On 06/01/2022 01:16, Ken Wright wrote:
I've been having trouble logging into my email server (postfix
3.4.13, dovecot 2.3.7.2, postfixadmin 3.3.8). I decided to try the
doveadm auth test, and got the
On Thu, 2022-01-06 at 03:44 +0100, John Fawcett wrote:
> On 06/01/2022 01:16, Ken Wright wrote:
> > I've been having trouble logging into my email server (postfix
> > 3.4.13, dovecot 2.3.7.2, postfixadmin 3.3.8). I decided to try the
> > doveadm auth test, and got the following result:
> >
> >
On 06/01/2022 01:16, Ken Wright wrote:
I've been having trouble logging into my email server (postfix 3.4.13,
dovecot 2.3.7.2, postfixadmin 3.3.8). I decided to try the doveadm
auth test, and got the following result:
kwright@grace:~$ sudo doveadm auth test m...@mydomain.com
Password:
passdb:
I've been having trouble logging into my email server (postfix 3.4.13,
dovecot 2.3.7.2, postfixadmin 3.3.8). I decided to try the doveadm
auth test, and got the following result:
kwright@grace:~$ sudo doveadm auth test m...@mydomain.com
Password:
passdb: m...@mydomain.com auth failed
extra
Hello all,
Is there a way to enable push notifications for all users, rather than having
to enable them one by one?
My thinking was to set mail_attribute_dict to a static file but I can’t work
out what I would need to put in it.
(I’ve now realised that that will not allow me to have other
Bad recommendation, it WILL affect delivery if you start removing trace
fields.. (and not going to talk GDPR on list further ;)
On 2022-01-05 10:27 a.m., Sebastian Nielsen wrote:
MUA/browser based things are not considered be in scope for GDPR unless they
are truly unique.
So you do NOT need
MUA/browser based things are not considered be in scope for GDPR unless they
are truly unique.
So you do NOT need to hide user-agent/MUA for privacy reasons.
Received lines is only applicable (in scope for GDPR) if they identify the end
user. A good solution to this would be to just scrap every
On 05/01/2022 18:36, Sam Kuper wrote:
On Wed, Jan 05, 2022 at 06:00:31PM +0100, John Fawcett wrote:
my understanding of the GDPR legislation is that it defines what is
considered lawful processing. One of those items that makes the
processing lawful is consent.
Not necessarily.
An action that
On 05/01/2022 18:27, dc...@dvl.werbittewas.de wrote:
Am 05.01.22 um 18:00 schrieb John Fawcett:
my understanding of the GDPR legislation is that it defines what is
considered lawful processing. One of those items that makes the
processing lawful is consent. If I send an email to a public
On Wed, Jan 05, 2022 at 06:00:31PM +0100, John Fawcett wrote:
> my understanding of the GDPR legislation is that it defines what is
> considered lawful processing. One of those items that makes the
> processing lawful is consent.
Not necessarily.
An action that would not be lawful without
Am 05.01.22 um 18:00 schrieb John Fawcett:
> my understanding of the GDPR legislation is that it defines what is
> considered lawful processing. One of those items that makes the
> processing lawful is consent. If I send an email to a public mailing
> list I think it's fair to say that I am
Am 05.01.22 um 17:23 schrieb Michael Kliewe:
> In Postfix many privacy-friendly submission servers do the following:
[...]
nice feature, unfortunately we're currently not using postfix, because
none here has enough experience with it. maybe later...
but:
> The Received-Header is still
On 05/01/2022 17:44, Marc wrote:
Where people are sending email to public
mailing lists, there is no presumption of privacy.
I think the legislation is like this: the privacy is legislation is always
applicable, there are no conditions under which there is 'no presumption of
privacy'
Marc
> Where people are sending email to public
> mailing lists, there is no presumption of privacy.
>
I think the legislation is like this: the privacy is legislation is always
applicable, there are no conditions under which there is 'no presumption of
privacy'
On 05/01/2022 14:41, dc...@dvl.werbittewas.de wrote:
Am 04.01.22 um 08:39 schrieb Aki Tuomi:
We'll take a look at your patch. Can you please point out to some legal
information about the Received header's GDPR incompliance, I would be
interested to see it.
thanks for doing so.
the GDPR
Hi,
Am 03.01.2022 um 20:08 schrieb dc...@dvl.werbittewas.de:
@others: due to the importance of it for us, I'm currently trying to
implement it, but because that's my first deeper view in dovecots code,
maybe I'll need some help.
the patch for 2.3.17.1 is attached.
please let me know, if
Am 04.01.22 um 08:39 schrieb Aki Tuomi:
> We'll take a look at your patch. Can you please point out to some legal
> information about the Received header's GDPR incompliance, I would be
> interested to see it.
thanks for doing so.
the GDPR says about personal data:
- that only really
I've updated to version 2.3.17.1 (476cd46418) but problem still persists
- expunged messages reappearing.
Alex
On 12/13/21 10:45 AM, Joelly Alexander wrote:
Hi Claudio,
I've planned to upgrade them as well after Christmas - to hear you did
it already and the issues are gone is great news.
> On 10/12/2021 10:08 lujie wrote:
>
>
> hi, all,
> I need to filter email as follow rules:
> 1, delete the attachments;
> 2, replace some word in subject with code;
> 3, redirect to other email with the modified subject and original text in
> body.
>
> sieve and exrprograms used in my
> On 03/01/2022 10:51 he...@reox.at wrote:
>
>
> Hi!
>
> I have a dovecot installation, with the following configuration:
> mail_home = /var/vmail/%d/%n
> mail_location = maildir:~
>
> I would like to migrate the mail_location to maildir:~/mail, to get
> around the issues described in the
21 matches
Mail list logo
