Re: How to backup maildir

2019-02-09 Thread Christoph Haas via dovecot 

Hello Robert,

- Nachricht von Robert Moskowitz via dovecot   
-

 Datum: Sat, 9 Feb 2019 22:50:24 -0500
   Von: Robert Moskowitz via dovecot 
Antwort an: Robert Moskowitz , Dovecot Mailing  
List 

   Betreff: How to backup maildir
An: Dovecot Mailing List 


I have been thinking, and reading, on how to back up my mailserver.  
I have not found any approach that seems ready to use.



I have run years without any backup, but would really like to have  
something in place.


you're a really lucky guy! - I've been struck in the past for such  
carelessness on the one or other machine with dataloss ;-)


  I figure I can attach a USB drive and backup to that, then from  
there rsync to something elsewhere.  Further if that USB drive is a  
full mailserver image, I actually have a 'hot backup' where I only  
have to put the backup drive into a system and boot up at the last  
backup.


But this means properly copying all of /home/vmail and probably  
/home/sieve plus the /var/lib/mysql




Are you aware of the dovecot command "dsync"? (man dsync or  
https://wiki.dovecot.org/Tools/Doveadm/Sync)

This could be an approach of using dsync:
dsync backup -o plugin/quota= -f -u $user backup  
maildir:/mnt/USB/dovecot-backup/Maildir/$user/mail


Are there good tools that nicely does this?  Or do I choose a time  
late at night (only I am sometimes in non-US timezones) to shut down  
all services and just use rsync?


And stopping services itself is thought provoking.  What if Dovecot,  
amavis, mysql, or whatelse is in the middle of writing out a mail  
file what happens to that file and restart.


Just scary stuff and, in part, why I have never tackled this in the past.

thanks for all feedback



- Ende der Nachricht von Robert Moskowitz via dovecot  
 -


It really depends on how important your data is to you ... But you  
should really think about a general backup-strategy!
"Mr. Google" can help you to get some ideas how YOUR backup-strategy  
could look like...
Also there is much input for backing up dovecot with it's different  
mail storage flavours.
- But you have to invest some effort on your own, to search, read,  
evaluate and finally choose what's fitting into YOUR setup!


But as an starting point:
I'm using a for _MY setup_ modified and adopted version of Klaus  
Tachtler's dovecot-backup script:

https://github.com/tachtler/dovecot-backup/blob/master/dovecot_backup.sh

... mixed it with Borg Backup:
https://www.borgbackup.org/

... some further encryption, cloud storage and ... and ... and other stuff.


But as above mentioned:
YOU have to think about the grade of your paranoia level, how  
importand the data is to you in case of an data loss, time and money  
you are willing to invest and build upon this YOUR PERSONAL backup  
strategy.

- Sadly there is no one-size-fits-all!

Last famous words:
I've looked at your vita and was wondering about your post - you were  
writing RFCs, but have no clue about backing up your mail-data???  
Strange ...



Nevermind! Just my 2ct - hope this helps
Christoph.


--
Christoph Haas


binxAAP3atXH5.bin
Description: Öffentlicher PGP-Schlüssel


pgpK9JwJk_0VA.pgp
Description: Digitale PGP-Signatur

Re: How to backup maildir

2019-02-09 Thread Richard Hector via dovecot 
On 10/02/19 4:50 PM, Robert Moskowitz via dovecot wrote:
> I have been thinking, and reading, on how to back up my mailserver. I
> have not found any approach that seems ready to use.
> 
> 
> I have run years without any backup, but would really like to have
> something in place.  I figure I can attach a USB drive and backup to
> that, then from there rsync to something elsewhere.  Further if that USB
> drive is a full mailserver image, I actually have a 'hot backup' where I
> only have to put the backup drive into a system and boot up at the last
> backup.
> 
> But this means properly copying all of /home/vmail and probably
> /home/sieve plus the /var/lib/mysql
> 
> Are there good tools that nicely does this?  Or do I choose a time late
> at night (only I am sometimes in non-US timezones) to shut down all
> services and just use rsync?
> 
> And stopping services itself is thought provoking.  What if Dovecot,
> amavis, mysql, or whatelse is in the middle of writing out a mail file
> what happens to that file and restart.

I use dirvish, which is based on rsync, and which only syncs changed
files but uses hardlinks to keep storage and bandwidth down - it leaves
me with a full copy of the tree for each date, with links between. I run
it on a machine at home.

I don't ususally worry about stopping services; maildir should be all
right. For databases, I use the backup tools provided to back up the
running database, then use dirvish on the backups (and skip the database
files themselves).

I do do it at night, to save load on the server (it's an LXC container
on a VPS).

I believe rdiffbackup does something similar to dirvish.

Richard

How to backup maildir

2019-02-09 Thread Robert Moskowitz via dovecot 
I have been thinking, and reading, on how to back up my mailserver. I 
have not found any approach that seems ready to use.



I have run years without any backup, but would really like to have 
something in place.  I figure I can attach a USB drive and backup to 
that, then from there rsync to something elsewhere.  Further if that USB 
drive is a full mailserver image, I actually have a 'hot backup' where I 
only have to put the backup drive into a system and boot up at the last 
backup.


But this means properly copying all of /home/vmail and probably 
/home/sieve plus the /var/lib/mysql


Are there good tools that nicely does this?  Or do I choose a time late 
at night (only I am sometimes in non-US timezones) to shut down all 
services and just use rsync?


And stopping services itself is thought provoking.  What if Dovecot, 
amavis, mysql, or whatelse is in the middle of writing out a mail file 
what happens to that file and restart.


Just scary stuff and, in part, why I have never tackled this in the past.

thanks for all feedback

Re: offtopic: rant about thoughtless enabling DMARC checks

2019-02-09 Thread Benny Pedersen via dovecot 

Noel Butler via dovecot skrev den 2019-02-10 01:51:


... and surely he does not expect those with a million plus users sit
here and whitelist the million plus mailing lists that exist around
the world, heh, like thats going to happen :)


fixing mailman will be the fail, solve it by letting opendkim and 
opendmarc not reject detected maillist will be solution, even if openarc 
comes or not, in cpan Mail::Milter::Authenticated its solved, but who 
use it other then fastmail.fm ? :=)

Re: offtopic: rant about thoughtless enabling DMARC checks [was: Re: Bounces?]

2019-02-09 Thread Benny Pedersen via dovecot 

A. Schulze via dovecot skrev den 2019-02-09 23:28:

Am 09.02.19 um 19:56 schrieb Aki Tuomi via dovecot:

I'll review the settings when we manage to upgrade to mailman3


before updating to mailman3 consider an simpler update to latest 
mailman2.


will any of this implement openarc sealing ? :=)


you're using 2.1.15, current mailman2 is 2.1.29
Your missing an /significant amount/ of DMARC fixes!


we all missing the point of missing opendmarc that can test for openarc 
sealing and be done with all the mess :(


or add a wiki to opendkim to make it autodetect maillists just like cpan 
Mail::Milter::Authenticated does it


if it cant be done in opendkim lua we loose all


and: more off-topic:
while my messages *to* the dovecot list are sent using STARTTLS,
messages *from*  wursti.dovecot.fi are sent without encryption.
any reason to stay on unencrypted SMTP?


maybe same reason dovecot have a mx record ? :=)

but good catch if in ip is same as out ip

Re: offtopic: rant about thoughtless enabling DMARC checks

2019-02-09 Thread Noel Butler via dovecot 
On 10/02/2019 07:38, Ralph Seichter via dovecot wrote:

> * Juri Haberland via dovecot:
> 
>> Blindly enabling DMARC checks without thinking about the consequences
>> for themselves should not be the problem of other well behaving
>> participants.
> 
> Can you judge if DMARC is enabled "blindly"? No, I thought not. Also,
> the issue was not on the receiving end, but the reject policy for the
> originating domain.
> 
> Personally, I choose to treat "reject" as if it was "quarantine",
> i.e. affected mail is rerouted to a specific folder.
> 
>> And Aki, please go back to "munge only if needed" - munging all
>> messages leads to a really bad "user experience".
> 
> Only speak for yourself please.
> 
> -Ralph

+1 (for entire post) 

... and surely he does not expect those with a million plus users sit
here and whitelist the million plus mailing lists that exist around the
world, heh, like thats going to happen :) 

-- 
Kind Regards, 

Noel Butler 

This Email, including any attachments, may contain legally 
privileged
information, therefore remains confidential and subject to copyright
protected under international law. You may not disseminate, discuss, or
reveal, any part, to anyone, without the authors express written
authority to do so. If you are not the intended recipient, please notify
the sender then delete all copies of this message including attachments,
immediately. Confidentiality, copyright, and legal privilege are not
waived or lost by reason of the mistaken delivery of this message. Only
PDF [1] and ODF [2] documents accepted, please do not send proprietary
formatted documents 

 

Links:
--
[1] http://www.adobe.com/
[2] http://en.wikipedia.org/wiki/OpenDocument

Re: offtopic: rant about thoughtless enabling DMARC checks [was: Re: Bounces?]

2019-02-09 Thread A. Schulze via dovecot 



Am 09.02.19 um 19:56 schrieb Aki Tuomi via dovecot:
> I'll review the settings when we manage to upgrade to mailman3

Hello Aki,

before updating to mailman3 consider an simpler update to latest mailman2.

you're using 2.1.15, current mailman2 is 2.1.29
Your missing an /significant amount/ of DMARC fixes!

and: more off-topic:
while my messages *to* the dovecot list are sent using STARTTLS,
messages *from*  wursti.dovecot.fi are sent without encryption.
any reason to stay on unencrypted SMTP?

Andreas

Re: offtopic: rant about thoughtless enabling DMARC checks

2019-02-09 Thread Ralph Seichter via dovecot 
* Juri Haberland via dovecot:

> Blindly enabling DMARC checks without thinking about the consequences
> for themselves should not be the problem of other well behaving
> participants.

Can you judge if DMARC is enabled "blindly"? No, I thought not. Also,
the issue was not on the receiving end, but the reject policy for the
originating domain.

Personally, I choose to treat "reject" as if it was "quarantine",
i.e. affected mail is rerouted to a specific folder.

> And Aki, please go back to "munge only if needed" - munging all
> messages leads to a really bad "user experience".

Only speak for yourself please.

-Ralph

Re: offtopic: rant about thoughtless enabling DMARC checks [was: Re: Bounces?]

2019-02-09 Thread Juri Haberland via dovecot 
On 09/02/2019 20:13, Michael A. Peters via dovecot wrote:
> On 2/9/19 10:48 AM, Juri Haberland via dovecot wrote:

>> Most people use OpenDMARC and there are patches to mark certain hosts as
>> mailing lists senders, so it is possible.
> 
> can you please let me know where to find those patches?

https://sourceforge.net/p/opendmarc/tickets/180/

Also have a look at http://batleth.sapienti-sat.org/projects/opendmarc/.

I have an Ubuntu-PPA where you can get a package with all of the above
patches (https://launchpad.net/~haberland/+archive/ubuntu/opendmarc).


Cheers,
  Juri

Re: offtopic: rant about thoughtless enabling DMARC checks [was: Re: Bounces?]

2019-02-09 Thread Michael A. Peters via dovecot 

On 2/9/19 11:13 AM, Michael A. Peters via dovecot wrote:

On 2/9/19 10:48 AM, Juri Haberland via dovecot wrote:

*snip*


Honestly I was sort of tempted to try and create my own DMARC validator 
(I was thinking one daemon that does both DKIM and DMARC - for postfix, 
Exim has DKIM native but I only use Exim for submission) that tried to 
sniff Mailman and not enforce it but it looks like it would be very time 
consuming.




What I wanted to do, was sniff mailman in headers and if it was sent by 
mail, reject if reverse DNS didn't match HELO/EHLO and white list from 
OpenDMARC enforcement if it did. That would prevent most spoofed that 
tried to look like Mailman since spoofed mail rarely has reverseDNS 
properly set up but Mailman admins tend to.

Re: offtopic: rant about thoughtless enabling DMARC checks [was: Re: Bounces?]

2019-02-09 Thread Michael A. Peters via dovecot 

On 2/9/19 10:48 AM, Juri Haberland via dovecot wrote:

On 09/02/2019 10:44, Aki Tuomi via dovecot wrote:

For some reason mailman failed to "munge from" for senders with dmarc policy ;(

It's now configured to always munge to avoid this again.


I'd say, let Mailman throw all people off the list that have enabled DMARC
checking without using exceptions for the lists they are on. It's a known
fact that DMARC does not cope well with mailing lists. Blindly enabling
DMARC checks without thinking about the consequences for themselves should
not be the problem of other well behaving participants.

Most people use OpenDMARC and there are patches to mark certain hosts as
mailing lists senders, so it is possible.


can you please let me know where to find those patches?

I ran DMARC in testing on one domain and had to disable it because over 
95% of the reports were false positives from mailing lists, and the few 
that were genuine spoofed would have easily been caught by spam/malware 
filters anyway.


However a project I am working on, DMARC is highly desired. Designing a 
white-list for known mailing lists is something I want to do.


Honestly I was sort of tempted to try and create my own DMARC validator 
(I was thinking one daemon that does both DKIM and DMARC - for postfix, 
Exim has DKIM native but I only use Exim for submission) that tried to 
sniff Mailman and not enforce it but it looks like it would be very time 
consuming.

Re: offtopic: rant about thoughtless enabling DMARC checks [was: Re: Bounces?]

2019-02-09 Thread Juri Haberland via dovecot 
On 09/02/2019 19:56, Aki Tuomi via dovecot wrote:
>> On 09 February 2019 at 20:48 Juri Haberland via dovecot < 
>> dovecot@dovecot.org 
>> > wrote:

>> Most people use OpenDMARC and there are patches to mark certain hosts as
>> mailing lists senders, so it is possible.

> Wonder how many would do this though?

Yeah, unfortunately not enough...

>> And everyone using p=reject should think about it as well - as I said,
>> DMARC does not play well with mailing lists, so setting p=reject on a
>> domain used to participate on mailing lists is not wise, to say the least.
>> You should not follow Yahoo and AOL - you know, why they did it, don't you?

> Unfortunately this is usually required by many common providers such as 
> microsoft and google, otherwise they refuse your mail.

That is definitely not true. They might require you to have DKIM and/or SPF
and maybe even a DMARC policy, but they definitely don't require p=reject!
Most of my domains have p=none and our mails are accepted by all major
providers...

> Hope you understand .

Understood. Had to write that mail anyway ;-)

  Juri

Re: offtopic: rant about thoughtless enabling DMARC checks [was: Re: Bounces?]

2019-02-09 Thread Aki Tuomi via dovecot 


 
 
  
   
  
  
   
On 09 February 2019 at 20:48 Juri Haberland via dovecot <
dovecot@dovecot.org> wrote:
   
   

   
   

   
   
On 09/02/2019 10:44, Aki Tuomi via dovecot wrote:
   
   

 For some reason mailman failed to "munge from" for senders with dmarc policy ;(


 


 It's now configured to always munge to avoid this again.

   
   
I'd say, let Mailman throw all people off the list that have enabled DMARC
   
   
checking without using exceptions for the lists they are on. It's a known
   
   
fact that DMARC does not cope well with mailing lists. Blindly enabling
   
   
DMARC checks without thinking about the consequences for themselves should
   
   
not be the problem of other well behaving participants.
   
   
  
  
   The problem is that it would drop all gmail users for a start, which there are plenty of. Also judging from the amount of bounces ww got it seemed like half the subscribers would drop out.
  
  
   
Most people use OpenDMARC and there are patches to mark certain hosts as
   
   
mailing lists senders, so it is possible.
   
   
  
  
   Wonder how many would do this though?
  
  
   
And everyone using p=reject should think about it as well - as I said,
   
   
DMARC does not play well with mailing lists, so setting p=reject on a
   
   
domain used to participate on mailing lists is not wise, to say the least.
   
   
You should not follow Yahoo and AOL - you know, why they did it, don't you?
   
   
  
  
   Unfortunately this is usually required by many common providers such as microsoft and google, otherwise they refuse your mail.
  
  
   
And Aki, please go back to "munge only if needed" - munging all messages
   
   
leads to a really bad "user experience".
   
   
  
  
   It does not seem to work correctly. I'll review the settings when we manage to upgrade to mailman3
  
  
   
Thanks.
   
   
  
  
   Hope you understand .
  
  
   
  
  
   Aki
  
  
   
   

   
   
Back to lurking,
   
   
Juri
   
  
  
   
  
  
   ---
   Aki Tuomi

offtopic: rant about thoughtless enabling DMARC checks [was: Re: Bounces?]

2019-02-09 Thread Juri Haberland via dovecot 
On 09/02/2019 10:44, Aki Tuomi via dovecot wrote:
> For some reason mailman failed to "munge from" for senders with dmarc policy 
> ;(
> 
> It's now configured to always munge to avoid this again.

I'd say, let Mailman throw all people off the list that have enabled DMARC
checking without using exceptions for the lists they are on. It's a known
fact that DMARC does not cope well with mailing lists. Blindly enabling
DMARC checks without thinking about the consequences for themselves should
not be the problem of other well behaving participants.

Most people use OpenDMARC and there are patches to mark certain hosts as
mailing lists senders, so it is possible.

And everyone using p=reject should think about it as well - as I said,
DMARC does not play well with mailing lists, so setting p=reject on a
domain used to participate on mailing lists is not wise, to say the least.
You should not follow Yahoo and AOL - you know, why they did it, don't you?

And Aki, please go back to "munge only if needed" - munging all messages
leads to a really bad "user experience".

Thanks.


Back to lurking,
  Juri

Re: assertion failed: (srcleft <= CHARSET_MAX_PENDING_BUF_SIZE)

2019-02-09 Thread Giacomo via dovecot 
I got a core file this morning.

opening it with gdb I get this:

(gdb) core imap.core
Core was generated by `dovecot/imap'.
Program terminated with signal 6, Aborted.
#0  0x11c1347a in ?? ()
(gdb) bt
#0  0x11c1347a in ?? ()
#1  0x11c13444 in ?? ()
#2  0x00018dee in ?? ()
#3  0x306db139575f3b0d in ?? ()
#4  0x7fffc144 in ?? ()
#5  0x in ?? ()

Doesn't look clean at all.

let me know if I should upload the file somewhere.

Thanks

Il giorno lun 21 gen 2019 alle ore 08:52 Giacomo  ha
scritto:

> I've just enabled core dumps on the involved FreeBSD system. Let's see if
> it dumps something..
>
> Il giorno dom 20 gen 2019 alle ore 19:16 Stephan Bosch <
> step...@rename-it.nl> ha scritto:
>
>> Hi Giacomo,
>>
>> Op 21/12/2018 om 16:16 schreef Giacomo:
>> > The bug happens not very often, it might need a week to get a core file.
>>
>> Any luck getting a core file?
>>
>> Regards,
>>
>> Stephan.
>> >
>> >
>> > Il giorno ven 21 dic 2018 alle ore 15:18 Aki Tuomi
>> > mailto:aki.tu...@open-xchange.com>> ha
>> > scritto:
>> >
>> >
>> > On 21.12.2018 14.49, Giacomo wrote:
>> > > I'm running the following:
>> > >
>> > > # 2.3.4 (0ecbaf23d): /usr/local/etc/dovecot/dovecot.conf
>> > > # OS: FreeBSD 11.2-RELEASE-p4 amd64
>> > > # FS: ZFS
>> > >
>> > > auth_mechanisms = plain login
>> > > auth_username_format = %Ln
>> > > listen = *
>> > > mail_location = maildir:~/Maildir
>> > > namespace inbox {
>> > >   inbox = yes
>> > >   location =
>> > >   mailbox Drafts {
>> > > auto = subscribe
>> > > special_use = \Drafts
>> > >   }
>> > >   mailbox Junk {
>> > > auto = subscribe
>> > > special_use = \Junk
>> > >   }
>> > >   mailbox Sent {
>> > > special_use = \Sent
>> > >   }
>> > >   mailbox Trash {
>> > > auto = subscribe
>> > > special_use = \Trash
>> > >   }
>> > >   prefix =
>> > > }
>> > > passdb {
>> > >   driver = pam
>> > > }
>> > > protocols = imap lmtp
>> > > service auth {
>> > >   unix_listener /var/spool/postfix/private/auth {
>> > > group = postfix
>> > > mode = 0666
>> > > user = postfix
>> > >   }
>> > >   user = dovecot
>> > > }
>> > > service imap-login {
>> > >   inet_listener imap {
>> > > port = 0
>> > >   }
>> > > }
>> > > service lmtp {
>> > >   unix_listener /var/spool/postfix/private/dovecot-lmtp {
>> > > group = postfix
>> > > mode = 0600
>> > > user = postfix
>> > >   }
>> > > }
>> > > service stats {
>> > >   unix_listener stats-reader {
>> > > group =
>> > > mode = 0600
>> > > user =
>> > >   }
>> > >   unix_listener stats-writer {
>> > > group = $default_internal_group
>> > > mode = 0666
>> > > user =
>> > >   }
>> > >   user = $default_internal_user
>> > > }
>> > > ssl_cert = > > > ssl_key = # hidden, use -P to show it
>> > > userdb {
>> > >   driver = passwd
>> > > }
>> > >
>> > > dmesg shows:
>> > >
>> > > pid 74441 (imap), uid 1002: exited on signal 6
>> > > pid 74784 (imap), uid 1002: exited on signal 6
>> > > pid 21471 (imap), uid 1002: exited on signal 6
>> > > pid 21470 (imap), uid 1002: exited on signal 6
>> > > pid 21464 (imap), uid 1002: exited on signal 6
>> > > pid 21731 (imap), uid 1002: exited on signal 6
>> > >
>> > > Sometimes the dovecot process serving an user crashes. He runs
>> > mostly
>> > > airmail on macOS and samsung mail on Android.
>> > >
>> > > Happens only to that particular user.
>> > >
>> > > The log shows the following: (maillog)
>> > >
>> > > Dec 16 14:52:35 mail dovecot: imap-login: Login: user=,
>> > > method=PLAIN, rip=79.12.201.157, lip=192.168.1.28, mpid=74779,
>> TLS,
>> > > session=
>> > > Dec 16 14:52:39 mail dovecot: imap(USER)<74441>:
>> > > Panic: file charset-iconv.c: line 83 (charset_to_utf8_try):
>> > assertion
>> > > failed: (srcleft <= CHARSET_MAX_PENDING_BUF_SIZE)
>> > > Dec 16 14:52:39 mail dovecot: imap(USER)<74441>:
>> > > Fatal: master: service(imap): child 74441 killed with signal 6
>> (core
>> > > not dumped - https://dovecot.org/bugreport.html#coredumps - set
>> > > service imap { drop_priv_before_exec=yes })
>> > >
>> > > I'm here if more info is needed.
>> > >
>> > > Thanks for taking a look.
>> >
>> >
>> > Can you somehow get a core file and get backtrace from it?
>> >
>> >
>> > Aki
>> >
>>
>>

Use sieve to move all mail automatically based on List-Id

2019-02-09 Thread Matthias Fechner via dovecot 
Dear all,

I currently use the following rule to automatically sort email into
folders based on mailing lists:

# split out the various list forms
# Mailman & other lists using list-id
if exists "list-id" {
    if header :regex "list-id" "<([a-z_0-9-]+)[.@]" {
    set :lower "listname" "${1}";
    fileinto :create "${listname}";
    } else {
    if header :regex "list-id" "^\\s*

it moves the email to the folder 142 as the regex matches inside the <> string 
till the none-letter/none-number/_/- is matching.
I do not understand the expresion [.@] so it is nearly impossible for my to 
extend that query.

What I would like to do is using the ID as folder name as fallback.
So in this case I would like that the email is moved to folder 
`mfechner/ci-test`.
I'm not sure if sieve can handle the `/` correctly.

Thanks a lot for any tip.

Gruß
Matthias

-- 

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the universe trying to
produce bigger and better idiots. So far, the universe is winning." --
Rich Cook

Can't sync mailbox XXX: Mailbox isn't selectable

2019-02-09 Thread Tamas Hegedus via dovecot 

Hi,

I have users with file system folders, which contain mbox files and 
dovecot indexes, in the ~/mail directory.


If I run dsync, I have an error message and the sync can not be completed:

Can't sync mailbox FOLDER_NAME: Mailbox isn't selectable

I could not find any solution via google or any hint what to do in this 
situation. Thanks for your help and suggestion,

Tamas

--
Tamas Hegedus, PhD
Senior Research Fellow
MTA-SE Molecular Biophysics Research Group
Hungarian Academy of Sciences  | phone: (36) 1-459 1500/60233
Semmelweis University  | fax:   (36) 1-266 6656
Tuzolto utca 37-47 | mailto:ta...@hegelab.org
Budapest, 1094, Hungary| http://www.hegelab.org

---
This email has been checked for viruses by AVG.
https://www.avg.com

Re: Bounces?

2019-02-09 Thread Aki Tuomi via dovecot 


 
 
  
   For some reason mailman failed to "munge from" for senders with dmarc policy ;(
  
  
   
  
  
   It's now configured to always munge to avoid this again.
  
  
   
  
  
   Aki
  
  
   
On 09 February 2019 at 11:21 "@lbutlr via dovecot" <
dovecot@dovecot.org> wrote:
   
   

   
   

   
   
I just got this
   
   

   
   
On 9 Feb 2019, at 00:00, 
dovecot-requ...@dovecot.org wrote:
   
   

 Your membership in the mailing list dovecot has been disabled due to


 excessive bounces The last bounce received from you was dated


 02-Feb-2019. You will not get any more messages from this list until


 you re-enable your membership. You will receive 1 more reminders like


 this before your membership in the list is deleted.


 


 To re-enable your membership, you can simply respond to this message


 (leaving the Subject: line intact), or visit the confirmation page at


 


 https://dovecot.org/mailman/confirm/dovecot/41881d…

   
   
When clicking the link I get "Bad confirmation sting" and something about maybe the link expired.
   
   

   
   
I see no connection attempts from dovecot.org over the last few days other than this message.
   
   

   
   

   
   
--
   
   
If at first you don't succeed, destroy all evidence that you tried.
   
   

   
  
  
   
  
  
   ---
   Aki Tuomi

Bounces?

2019-02-09 Thread @lbutlr via dovecot 
I just got this

On 9 Feb 2019, at 00:00, dovecot-requ...@dovecot.org wrote:
> Your membership in the mailing list dovecot has been disabled due to
> excessive bounces The last bounce received from you was dated
> 02-Feb-2019.  You will not get any more messages from this list until
> you re-enable your membership.  You will receive 1 more reminders like
> this before your membership in the list is deleted.
> 
> To re-enable your membership, you can simply respond to this message
> (leaving the Subject: line intact), or visit the confirmation page at
> 
>   https://dovecot.org/mailman/confirm/dovecot/41881d…

When clicking the link I get "Bad confirmation sting" and something about maybe 
the link expired.

I see no connection attempts from dovecot.org over the last few days other than 
this message.


-- 
If at first you don't succeed, destroy all evidence that you tried.