Re: Random duplicated emails

[Битус Павел via dovecot]

Hello,

When using a sieve, there is no problem with duplicates, but it is 
impossible to transfer all users to a sieve.


10.09.2019 20:17, Francis via dovecot пишет:
Le lun. 9 sept. 2019 à 12:08, Francis > a écrit :


Hello,

I migrated our mail infrastructure to Dovecot on Ubuntu 18.04 some
months ago. It works fine, but recently some users told me that
they sometime receive duplicated emails. Same email content, same
headers including message-id.

I'm using two dovecot servers on two sites. Both server are in
cluster. We don't use shared folders. All users that reported this
issue so far are using the same server instance. The problematic 
emails are coming from local users on that instance too. The
examples they given to me was emails with many recipients (To/CC).
A specific message can be received twice (or more) by recipient A
but only once by recipient B. I didn't see anything in the logs
about sieve rules that redirect emails to others recipients.

Where should I look to diagnostic this issue?


Hello,

Thanks for your hints. The message from  Битус Павел in another thread 
today seem to be similar to my problem. I asked my users if the 
affected messages are processed by a local rules in Thunderbird and 
they said yes. I asked them to replaces theirs local rules by sieve 
rules instead. We'll see if it fixes the problem.


Thanks!

--
Francis

--


ROZETKA

Bitus Pavlo
System administrator
rozetka.ua 

Re: Off-site cloud backup (eg Amazon S3, Wasabi)

[Markus Raps via dovecot]

On 2019-09-09 15:47, James Brown via dovecot wrote:

I’d like to synchronise our mail store to an Amazon S3 bucket or
similar, for protection from ransomware.

Server is running on macOS with maildir.

Should I use a Dovecot process, rsync, a Mac app like Arq or Jungle
Disk, or something else?

Anyone have experience or opinions on this?

Thanks,

James.



check out rclone
https://rclone.org/s3/



--
Mit freundlichen Grüßen / best regards
Markus Raps

-
Web: rapsplace.de
Mail: m.r...@rapsplace.de
Mobile: +49 1787 80 50 42
-

Re: Quota and maildir does not work with subfolders of INBOX

[Niels Kobschätzki via dovecot]

> On 10. Sep 2019, at 22:09, Mark Moseley via dovecot  
> wrote:
> 
>> On Mon, Sep 9, 2019 at 8:57 PM Niels Kobschätzki via dovecot 
>>  wrote:
> 
>> On 9/9/19 6:18 PM, @lbutlr via dovecot wrote:
>> > On 9 Sep 2019, at 09:27, Niels Kobschätzki  wrote:
>> >> The moment I remove those folders, the size gets calculated correctly. 
>> >> Unfortunately those folders are generated by some clients automatically 
>> >> afaik (like .INBOX.Trash)
>> >> That sounds like a misconfiguration of the IMAP client. Someone has
>> gone in and improperly set INBOX as the IMAP path Prefix in their MUA.
>> 
>> The thing is that it worked before. Even when the user misconfigured
>> their client in such a way, the quota-plugin shouldn't just throw some
>> dice to get to a arbitrarily high quota the user has used instead of the
>> right amount.
>> 
>> > I used to have this problem with some users until I implemented repeated 
>> > and consistent application of a clue bat.
>> 
>> Some users is in my case (as far as I guess) like 0.5%
>> 
>> > I don’t know of a server-side setting to prevent users from screwing up 
>> > this setting, but maybe?
>> 
>> Wouldn't that break existing accounts?
>> 
> 
> Does it sound like this? 
> https://www.dovecot.nl/pipermail/dovecot/2019-March/115214.html
> 
> If so, in a direct email, Timo suggested using the 'count' quota (instead of 
> the Maildir++ quota). I've not yet been able to test that to verify, due to 
> the large amount of mailboxes and the reliance on maildirsize file for some 
> of our tools. 

This could be it but according to the documentation I don’t want to risk that 
performance hit. I have a high number of accounts as well and I don’t want to 
risk that performance hit when switching even though all boxes should be 
indexed. 

Niels 

Re: [Bug] Sieve vacation :addresses match only,> case-sensitive?

[Klaus Steinberger via dovecot]

> I want to have it case-insensitive again, like in Pigeonhole version 0.4.24

i would also plea for making it case-insensitive again! We were hit by this too,
and I never saw any mail system in which the local Part ist Case sensitive!

Sincerly,
Klaus Steinberger


-- 
Rechnerbetriebsgruppe / IT, Fakultät für Physik
Klaus Steinberger
FAX: +49 89 28914280
Tel: +49 89 28914287



signature.asc
Description: OpenPGP digital signature

Re: [Bug] Sieve vacation :addresses match only,> case-sensitive?

[Stephan Bosch via dovecot]

On 11/09/2019 21:25, Klaus Steinberger via dovecot wrote:

I want to have it case-insensitive again, like in Pigeonhole version 0.4.24

i would also plea for making it case-insensitive again! We were hit by this too,
and I never saw any mail system in which the local Part ist Case sensitive!


We're looking into this. Tracking internally as DOP-1424.

Regards,

Stephan.

Re: Sieve vacation :addresses match only case-sensitive?

[Stephan Bosch via dovecot]

On 02/09/2019 15:05, Philipp Faeustlin via dovecot wrote:
The recipients in the vacation :addresses String list are matched 
case-sensitive.


If the recipient gets a mail with wrong case, the message is discarded 
with:
"discarding vacation response for implicitly delivered message; no 
known (envelope) recipient address found in message headers"


I think the matching should be case-insensitive.

Is this a bug or do I miss some option?

I'm using Dovecot 2.3.7.2, Pigeonhole version 0.5.7.2.


We're looking into this. Tracking internally as DOP-1424.

Regards,

Stephan.

Re: Case sensitive problem for vacation with dovecot lmtp pigeonhole

[Stephan Bosch via dovecot]

On 09/06/2019 16:07, kadafax--- via dovecot wrote:

Hi list,

This issue was raised here by John Fawcett on 12/02/19 but got no 
response.

So, as I'm facing the same issue, I would like to try again:

When using the vacation sieve extension, if I send an email to 
user.n...@mydomain.com it will work, but not to 
user.n...@mydomain.com. Is there a way to make the user part case 
insensitive so that the vacation auto-reply is fired whatever the way 
user part is written ?


We're looking into this. Tracking internally as DOP-1424.

Regards,

Stephan.



doveconf -n output:

# 2.3.5.1 (7ec6d0ade): /usr/local/etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.5 (2483b085)
# OS: Linux 3.10.0-957.5.1.el7.x86_64 x86_64 CentOS Linux release 
7.6.1810 (Core)  ext4

# Hostname: myserver.mydomain.com
auth_master_user_separator = *
auth_username_chars = 
abcdefghijklmnopqrstuvwxyzABCDEFGHIJKLMNOPQRSTUVWXYZ01234567890.-_@*

auth_verbose = yes
debug_log_path = /var/log/dovecot-debug.log
default_client_limit = 10640
default_process_limit = 2128
default_vsz_limit = 0
hostname = mydomain.com
info_log_path = /var/log/dovecot.log
lda_mailbox_autocreate = yes
lda_mailbox_autosubscribe = yes
listen = *
log_path = /var/log/dovecot-error.log
login_greeting = Welcome
mail_gid = vmail
mail_location = maildir:/var/vmail/%Ln
mail_plugins = quota fts fts_lucene
mail_uid = vmail
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope 
encoded-character vacation subaddress comparator-i;ascii-numeric 
relational regex imap4flags copy include variables body enotify 
environment mailbox date index ihave duplicate mime foreverypart 
extracttext

namespace inbox {
  inbox = yes
  location = maildir:/var/vmail/%Ln
  mailbox Drafts {
    auto = subscribe
    special_use = \Drafts
  }
  mailbox Sent {
    auto = subscribe
    special_use = \Sent
  }
  mailbox "Sent Messages" {
    special_use = \Sent
  }
  mailbox Trash {
    auto = subscribe
    special_use = \Trash
  }
  prefix =
  type = private
}
passdb {
  args = /usr/local/etc/dovecot/deny-users
  deny = yes
  driver = passwd-file
}
passdb {
  args = /usr/local/etc/dovecot/master-users
  driver = passwd-file
  master = yes
  pass = yes
}
passdb {
  args = /usr/local/etc/dovecot/dovecot-ldap.conf.ext
  driver = ldap
}
plugin {
  fts = lucene
  fts_autoindex = yes
  fts_lucene = whitespace_chars=@.
  quota = maildir:User quota
  quota_rule = *:storage=30GB
  quota_rule2 = Trash:storage=+200M
  quota_warning = storage=95%% quota-warning 95 %u
  quota_warning2 = storage=80%% quota-warning 80 %u
  sieve = /var/sieve-scripts/%Ln.sieve
  sieve_dir = /var/vmail/%Ln/home/sieve
}
postmaster_address = postmas...@mydomain.com
protocols = imap pop3 lmtp sieve sieve
quota_full_tempfail = yes
service auth-worker {
  user = $default_internal_user
}
service auth {
  unix_listener /var/spool/postfix/private/auth {
    mode = 0777
    user = vmail
  }
}
service imap-login {
  inet_listener imaps {
    port = 993
    ssl = yes
  }
  process_min_avail = 10
}
service imap {
  process_limit = 2128
}
service lmtp {
  executable = lmtp -L
  process_min_avail = 15
  unix_listener /var/spool/postfix/private/dovecot-lmtp {
    group = postfix
    mode = 0600
    user = postfix
  }
}
service managesieve-login {
  inet_listener sieve {
    port = 4190
  }
}
service pop3-login {
  inet_listener pop3s {
    port = 995
    ssl = yes
  }
}
service quota-warning {
  executable = script /usr/local/bin/quota-warning.sh
  user = nobody
}
ssl_cert = 

Re: Subscribe to a fileinto :create mailbox?

[Stephan Bosch via dovecot]

On 08/09/2019 04:16, Larry Rosenman via dovecot wrote:

Is it possible in pigeonhole?

I.E.  I do a fileinto :create "some/mail/box"
How can I make it autosubscribe?


You cannot control this from within Sieve (there is no :subscribe 
argument). However, you can  auto-subscribe to *all* mailboxes created 
in Sieve by setting lda_mailbox_autosubscribe=yes, which is usually 
adequate.


Regards,

Stephan.




doveconf -n:
# 2.3.7.2 (3c910f64b): /usr/local/etc/dovecot/dovecot.conf
# Pigeonhole version 0.5.7.2 (7372921a)
# OS: FreeBSD 12.0-STABLE amd64
# Hostname: thebighonker.lerctr.org 
auth_default_realm = lerctr.org 
auth_mechanisms = plain login
auth_realms = lerctr.org  thebighonker.lerctr.org 
 tbh.lerctr.org 
 thejonesonair.com  
thejonesonair.net  why.net 

default_vsz_limit = 1 G
deliver_log_format = msgid=%m: %$ (subject=%s from=%f size=%w)
doveadm_password = # hidden, use -P to show it
first_valid_gid = 0
first_valid_uid = 0
lda_mailbox_autocreate = yes
listen = 192.147.25.65, ::
login_access_sockets = tcpwrap
mail_attribute_dict = file:%h/mail/.imap/dovecot-mail-attributes
mail_location = mbox:~/mail:INBOX=~/mail/INBOX
mail_log_prefix = "%s(%u/%p): "
mail_plugins = " fts fts_solr notify virtual"
mail_privileged_group = mail
mail_server_admin = mailto:l...@lerctr.org 
mail_server_comment = LERCTR Mail Server
managesieve_notify_capability = mailto
managesieve_sieve_capability = fileinto reject envelope 
encoded-character vacation subaddress comparator-i;ascii-numeric 
relational regex imap4flags copy include variables body enotify 
environment mailbox date index ihave duplicate mime foreverypart 
extracttext vacation-seconds editheader mboxmetadata servermetadata 
vnd.dovecot.debug imapsieve vnd.dovecot.imapsieve

namespace archive {
  hidden = no
  list = no
  location = mbox:~/MAIL-ARCHIVE
  prefix = ARCHIVE/
  separator = /
}
namespace inbox {
  inbox = yes
  location =
  mailbox Drafts {
    special_use = \Drafts
  }
  mailbox INBOX {
    auto = create
  }
  mailbox SENT {
    special_use = \Sent
  }
  mailbox SPAM {
    special_use = \Junk
  }
  mailbox "Sent Messages" {
    special_use = \Sent
  }
  mailbox Trash {
    special_use = \Trash
  }
  mailbox virtual/Flagged {
    special_use = \Flagged
  }
  mailbox virtual/all {
    special_use = \All
  }
  prefix =
  separator = /
}
namespace virtual {
  hidden = no
  list = yes
  location = virtual:~/MAIL-VIRTUAL
  prefix = Virtual/
  separator = /
}
passdb {
  args = /usr/local/etc/dovecot/dovecot-sql.conf.ext
  driver = sql
}
passdb {
  args = user=%Ln noauthenticate
  driver = static
  skip = authenticated
}
passdb {
  args = failure_show_msg=yes session=yes max_requests=20
  driver = pam
  override_fields = domain=lerctr.org 
  skip = authenticated
}
plugin {
  fts = solr
  fts_autoindex = yes
  fts_solr = url=http://thebighonker.lerctr.org:8983/solr/dovecot/
  fts_tika = http://localhost:9998/tika/
  imapsieve_mailbox1_before = 
file:/usr/local/share/dovecot-pigeonhole/sieve/report-spam.sieve

  imapsieve_mailbox1_causes = COPY
  imapsieve_mailbox1_name = SPAM
  imapsieve_mailbox2_before = 
file:/usr/local/share/dovecot-pigeonhole/sieve/report-ham.sieve

  imapsieve_mailbox2_causes = COPY
  imapsieve_mailbox2_from = SPAM
  imapsieve_mailbox2_name = *
  imapsieve_url = sieve://thebighonker.lerctr.org 

  mail_log_events = delete undelete expunge copy mailbox_delete 
mailbox_rename flag_change append

  mail_log_fields = uid box msgid size from subject vsize flags
  recipient_delimiter = +-_
  sieve = ~/.dovecot.sieve
  sieve_dir = ~/sieve
  sieve_execute_bin_dir = /usr/local/share/dovecot-pigeonhole/sieve
  sieve_extensions = +editheader +vacation-seconds +mboxmetadata 
+servermetadata +vnd.dovecot.debug

  sieve_global_extensions = +vnd.dovecot.pipe +vnd.dovecot.execute
  sieve_pipe_bin_dir = /usr/local/share/dovecot-pigeonhole/sieve
  sieve_plugins = sieve_imapsieve sieve_extprograms
}
postmaster_address = postmas...@lerctr.org 
protocols = imap pop3 lmtp sieve
recipient_delimiter = +-_
service anvil {
  unix_listener anvil {
    group = mail
    mode = 0666
  }
}
service auth {
  unix_listener auth-client {
    mode = 0666
  }
  unix_listener auth-master {
    mode = 0666
  }
}
service doveadm {
  inet_listener http {
    port = 8080
    ssl = yes
  }
}
service indexer-worker {
  drop_priv_before_exec = yes
}
service lmtp {
  inet_listener lmtp {
    address = 127.0.0.1
    port = 24
  }
}
service managesieve-login {
  inet_listener sieve {
    port = 4190
  }
  inet_listener sieve_deprecated {
    port = 2000
  }
}
service stats {
  unix_listener stats-reader {
    group = mail
    mode = 0666
    user =
  }
  unix_listener stats-writer {
  

Re: [Bug] Sieve vacation :addresses match only,> case-sensitive?

[Hendrik Boom via dovecot]

On Wed, Sep 11, 2019 at 09:25:54PM +0200, Klaus Steinberger via dovecot wrote:
> > I want to have it case-insensitive again, like in Pigeonhole version 0.4.24
> 
> i would also plea for making it case-insensitive again! We were hit by this 
> too,
> and I never saw any mail system in which the local Part ist Case sensitive!

Isn't the user name in the original Unix mail system (and presumably 
most of its descentants) case sensitive?  In which case it has to 
distinguish between mail sent to bob and to Bob?

- hendrik

Re: [Bug] Sieve vacation :addresses match only,> case-sensitive?

[Bernd Petrovitsch via dovecot]

On 11/09/2019 22:43, Hendrik Boom via dovecot wrote:
> On Wed, Sep 11, 2019 at 09:25:54PM +0200, Klaus Steinberger via dovecot wrote:
>>> I want to have it case-insensitive again, like in Pigeonhole version 0.4.24
>>
>> i would also plea for making it case-insensitive again! We were hit by this 
>> too,
>> and I never saw any mail system in which the local Part ist Case sensitive!

E.g.
https://stackoverflow.com/questions/9807909/are-email-addresses-case-sensitive
discusses this - including quotes from RFCs ...

> Isn't the user name in the original Unix mail system (and presumably 
> most of its descentants) case sensitive?  In which case it has to 
> distinguish between mail sent to bob and to Bob?

The local part of an email domain has absolutely nothing to do with any
(local or non-local) user account - and who says that there are any user
accounts/logins (apart from root and so-called system users) on the mail
system?
Yes, it *could* have something to do, and yes it actually may often be
the case but that's just a - intended or not intended - coincidence 

MfG,
Bernd
-- 
Bernd Petrovitsch  Email : be...@petrovitsch.priv.at
 LUGA : http://www.luga.at

Re: [Bug] Sieve vacation :addresses match only,> case-sensitive?

[Eray Aslan via dovecot]

On Wed, Sep 11, 2019 at 04:43:48PM -0400, Hendrik Boom via dovecot wrote:
> Isn't the user name in the original Unix mail system (and presumably 
> most of its descentants) case sensitive?  In which case it has to 
> distinguish between mail sent to bob and to Bob?

Message handling systems MUST preserve case, systems delivering messages
to a mailbox SHOULD ignore case.

RFCs, especially earlier ones, require local-part to be case senstive
but that was a poorly thought out directive and the world largely
ignored it.

-- 
Eray