- dovecot - dovecot.org

IMAP ghost login
by Jos Chrispijn 25 Apr '20

25 Apr '20

Would it be possible to generate a user list that Dovecot permits to fetch mail from? Thanks, Joz

1 0

Dovecot Load balancing - Please Please Please help me
by Kishore Potnuru 24 Apr '20

24 Apr '20

I need your help on my issue very badly. I have the dovecot version 2.0.9 installed on RHEL linux 6.10 version. It's a single Live server. I need to add a load balancer by adding another server for resilience. I cannot upgrade the dovecot version at this time as it is a single live server. If something goes wrong, I will be in trouble. Basically the requirement/issue is: a) it's a single live dovecot POP3/IMAP server b) people are accessing their emails from microsoft outlook (by giving the same server name as IMAP and SMTP server). But more than 100000 emails will be travelled/routed. c) This server is not rebooted from couple of years. d) Now they are worried about, just in case if the server is having any issues during the reboot or if something goes wrong with the server in any case, there will be huge issues. e) They would like to create resilience by adding another server and emails will be travelled from both the servers. If one server is having any issues due to any technical issue and if it doesn't come back easily, then the emails will be travelled through the other server and there will no disturbance to the emails. atleast it travels from the other server. I have very less knowledge on this. Could you please help me providing the best solution for this. I will wait for your reply. Please please please help me. Thanks, Kishore Potnuru

4 8

Batching quota clone updates
by micah anderson 23 Apr '20

23 Apr '20

Hi, I like the quota count+clone configuration. However, I'm wondering if the cloning process could batch its updates into chunks, or spread them out over time? The clone updates happen whenever the quota is updated, typically this is fine, but when a tsunami of spam comes resulting in delivery to every user on the system, then can be quite overwhelming for a sql server to do an update for every user. Thanks! -- micah

1 0

Help with Shared Mailboxes
by Alan Stevens 23 Apr '20

23 Apr '20

dovecot version = 2.2..27 I have a running debian server ( jessie-backports ) supporting email for three different domains. It is working fine. My boss has asked me to look into using Shared folders/mailboxes - for instance, he wants selected users of Domain-A to be able to see the shared Inbox of the user "support" who is also in Domain-A. Sorry if my questions are basic, but here goes:- 1. Can I simply change the relevant dovecot configuration files and introduce Shared mailboxes into an already running system? Very basically, add the imap-acl plugin, the shared namespace, the dict file and restart dovecot? 2. If I can do this, would it wipe out the tens of thousands of existing emails I have on the system now? i.e. Does Sharing have to be introduced when new email server is being brought up? Can it be added on-the-fly to my working server? Would the emails in /var/mail/vmail/Domain-A/alan/mail seemlessly populate /var/mail/vmail/Domain-A/Shared/alan/mail after making such changes? 3. If adding the Sharing to my running system is possible, can I add it on only one of my three domains? I have a test domain with one user. My principle domain ( Domain-A ) has many users, and as I stated previously, very very many stored emails. Emails I absolutely cannot afford to lose. Any insights are appreciated. Alan Stevens ---||--- alanrstevens(a)yahoo.com https://www.linkedin.com/in/alanrstevens

1 0

Testing COI
by lists＠mlserv.org 23 Apr '20

23 Apr '20

Hi, I am playing around with the COI plugin and try to get things working. I followed the Dovecot docs and also got the source from Github (dovecot/coi). I have compiled and installed coi successfully. IMAP seems to be fine, but LMTP has some errors in the logs, so I removed imap_coi for the moment: Apr 23 17:05:16 mx dovecot: lmtp(10752): Fatal: Couldn't load required plugin /usr/lib64/dovecot/lib11_imap_coi_plugin.so: dlopen() failed: /usr/lib64/dovecot/lib11_imap_coi_plugin.so: undefined symbol: client_add_capability I am running Dovecot 2.3.10 and coi at the same version. Am I missing something here? Thanks in advance Christian -- Rößner-Network-Solutions Karl-Bröger-Str. 10, 36304 Alsfeld Fax: +49 6631 78823409, Mobil: +49 171 9905345 USt-IdNr.: DE225643613, https://roessner.website PGP fingerprint: 658D 1342 B762 F484 2DDF 1E88 38A5 4346 D727 94E5

2 2

Re-to-archived-thread: Dict issue with PostgreSQL for last_login plugin (duplicate key)
by lists＠mlserv.org 23 Apr '20

23 Apr '20

Hi, I have tried to implement last_login with PostgreSQL and I found an old thread from June 2019. I have found a simple solution that I want to share with you: I followed the instructions on how to set up a last_login on the official documentation. Therefor I creates a very simple table having userid and last_login fields. Added plugin and dict information. I received the duplicate key errors and I did this trick for now, which seems to solve this issue: CREATE OR REPLACE RULE insert_to_update AS ON INSERT TO users WHERE EXISTS (SELECT userid FROM users WHERE userid = NEW.userid) DO INSTEAD UPDATE users SET last_login = NEW.last_login WHERE userid = NEW.userid With this rule in place, INSERTs are changed to UPDATEs, if a userid entry already exists. No ned to patch code. Feel free to comment :-) Christian Thread online: https://www.dovecot.org/list/dovecot/2019-May/115921.html -- Rößner-Network-Solutions Karl-Bröger-Str. 10, 36304 Alsfeld Fax: +49 6631 78823409, Mobil: +49 171 9905345 USt-IdNr.: DE225643613, https://roessner.website PGP fingerprint: 658D 1342 B762 F484 2DDF 1E88 38A5 4346 D727 94E5

1 0

Recommendations on intrusion prevention/detection?
by Johannes Rohr 23 Apr '20

23 Apr '20

Dear all, what are the key strategies for intrusion prevention and detection with dovecot, apart from installing fail2ban? It is a pity that the IMAP protocol does not support 2 factor authentication, which seems to stop 90% of intrusion attempts in their tracks. Without it, if someone has obtained your password and reads your mail without modifying it, you will hardly ever notice. Is there a reasonable way of detecting and preventing logins from unusual IP ranges? Or are there other strategies you would recommend? Cheers, Johannes

10 13

Dovecot and thunderbird authentication issue?
by David Mehler 23 Apr '20

23 Apr '20

Hello, I'm using Dovecot 2.2, Postfix 3.5, and am atempting to get the latest version of Thunderbird to work. I tried account autoconfig which did not work, so I had to manually enter information and correct other information. On my server dovecot supports plane and login authentication methods but only over starttls i've got a letsencrypt certificate. My thunderbird configuration looks good, right hosts for incoming and outgoing mail, right ports, 143 starttls, and 587 smtp submission, and thunderbird has the authentication method set for normal password. This I interpreted to mean thunderbird is going to starttls then send the username and password. Thunderbird is giving me this error: imap server does not support the selected authentication method I realize this is vague, any suggestions? Thanks. Dave.

2 2

sieve question
by mj 23 Apr '20

23 Apr '20

Hi, We are trying to auto-reply to emails that still use one of our old domains. To do this, I have setup a catch-all mailbox for anything sent to that old domain using postfix virtual: @old.domain.com catch-all(a)new.domain.com Then I defined a sieve script for catch-all(a)new.domain.com, like: > require ["vacation"]; > if allof ( not exists ["list-help", "list-unsubscribe", "list-subscribe", "list-owner", "list-post", "list-archive", "list-id", "Mailing-List"] ) > > { vacation text: > This message is sent automatically, and your message has NOT been read nor forwarded. > > Please update your addressbooks! > > All the best! :-) > . > ; > } However, sieve never sends any auto-reply, because it logs: > discarding vacation response for implicitly delivered message; no > known (envelope) recipient address found in message headers > (recipient=<catch-all(a)new.domain.com>, and no additional `:addresses' > are specified) I have googled this, but adding :addresses in this case will not work, as we are trying to answer (basically) emails sent to any email addresses sent to that domain, and thus I cannot define specific :addresses Can anyone suggest what to do here? Thanks and stay healthy! MJ

5 11

Still interested in SMTPUTF8 support
by David Bürgin 22 Apr '20

22 Apr '20

I haven’t seen this term on the mailing list for a while. I don’t know if you’re tracking this somewhere, in any case I’m curious if you are still planning to add support for SMTPUTF8. Cheers,

2 1