similar to: Doc pointer request

> On 18/04/2020 17:45 David Favor <david at davidfavor.com> wrote: > > > At one point seems like I found a write up in > the Dovecot docs about having Dovecot directly > listen on port 25 using Opportunistic TLS along > with port 587 authentication, so only Dovecot was > required to handle incoming email. > > Said another way, no requirement for Sendmail,

Hello everyone, it's my first post here on this mailing list and I hope, I make it right. I posted a question on https://serverfault.com/questions/1031441/dovecot-as-proxy-with-submission and nobody was able to answer it. So I decided to push that question here (I'm talking about any new dovecot version and I've tested it with 2.3.4.1 (f79e8e7e4)). I try to run a dovecot proxy

Hi Philon, now, it's time for "Mahlzeit" ;-) Sorry, that I read the wiki1 instead of wiki2. I thought the 1 means that it is server one of ... my fault. Also not reading the first line above the menu. My focus was really on the content. ;-) Also my problem with the doc of Dovecot2 proxy is, that the document https://doc.dovecot.org/configuration_manual/authentication/proxies/

Hi all: I am learning Dovecot step by step. I have enabled the Submission Server, in the hope that I would not need to learn other MTAs like Postfix. The Submission Server is very comfortable: it picks up the existing Dovecot configuration, so that you do not need to configure any user authentication separately. It is working fine on my test setup. My first thought was that, if the recipient

I've tried turning on mbox_very_dirty_syncs for myself (and a few other brave souls running 1.0-alpha3 rather than 1.0-stable) again to see what perfomance gain it gives (see thread http://www.dovecot.org/list/dovecot/2005-July/007956.html). Now we aren't running UW-IMAP at all, how safe is mbox_very_dirty_syncs assuming the only other process writing to mailboxes is our MTA (exim) which

Aki Tuomi wrote in <1907575568.4364.1597984769802 at appsuite-dev-gw1.open-xchange.com>: |> On 21/08/2020 02:17 Steffen Nurpmeso <steffen at sdaoden.eu> wrote: ... |> Wietse Venema wrote in |> <4BXSTk189nzJrP3 at spike.porcupine.org>: |> ... |>|Steffen Nurpmeso: |> ... |>|> until SASL says it is done?!. How could EXTERNAL ever work

Hi, As per my discussion with cmouse on irc, I'm currently just using dovecot for its auth mechanism, etc capabilities (alas, Exim does not support argon directly). Tis a fun little side project. :) I have the config pared down as far as I think is reasonable (see below) and all is working well except that dovecot is very silent. Errors hit the logs but I would appreciate seeing successful

Working out upgrade of old 1.x + 2.x Dovecot installs to latest 2.3.2.1 out of Ubuntu Bionic repositories. _______ https://wiki.dovecot.org/Services suggests Dovecot can be used for full mail infrastructure, avoiding the complexity of exim4 or other MTA setup/management. Let me know if I understand this correctly. 1) https://wiki.dovecot.org/Submission can be used to listen on port 25 +

If I read this correctly, starttls will fail due to the MITM attack. That is the client knows security has been compromised. Using SSL/TLS, the MITM can use SSL stripping. Since most Postifx conf use "may" for security, the message would go though unencrypted. Correct??? Is there something to enable for perfect forward security with starttls? ? Original Message ? From: s.arcus at

Goldmine seems to a compiled database application compiled in something likeClipper. Clipper applications record lock through ISAM like files (DBF). However, in Windows NT/2000/XP, Opportunistic locking is turned on by default in order to accelerate file transfer from file services. [Windows 95/98 did not Opportunisticly lock] However, opportunistic locking corrupts ISAM and ISAM like

Is there any package available for qmail? I am having hard time finding it.

Per the wiki page: http://wiki.dovecot.org/LDA Doing the following should create a Maildir directory structure in an arbitrary directory, deposit a message and create/update any dovecot indexes: mkdir /common/foo export HOME=/common/foo export PATH=/usr/libexec/dovecot:$PATH cat 1180102308.88215.4145.davidfavor.com:2,RS | deliver -f doda at foobar.com This gives an error

Hi, On 25/05/2020 23:04, Voytek wrote: > jumping here with a question, if I use 143 with STARTTLS, and, force > TLS/SSL in configuration, that's equivalent from security POV, isn't > it? and, same for 110 STARTTLS? Or am I missing something? Interesting point, after some googling, I think you are right, and as long as we have set "disable_plaintext_auth = yes" (and we

what does the output of: netstat -n | grep :587 run as root, show you? the -p will give the program and pid. > Date: Wednesday, July 11, 2018 21:51:09 +0000 > From: Larry Rosenman <larryrtx at gmail.com> > > Yep, you (probably) need to configure openSMTPD to listen on 587 > > (I run exim, so I can't help with that).

Hi all, I've never really wanted to create my own MTA, because I like Postfix quite a lot. And I always thought it would require a horribly lot of time to be able to create something that was anywhere even close to having Postfix's features. (I would shudder to even think about recreating Dovecot from scratch nowadays.) But slowly over time I've also been thinking of ways how things

Hi, I have done configuration dovecot/exim/samba4ad. I use dovecot-lda not exim to deliver mail. And dovecot to authentify users. I have users with mail address on AD. When i sent mail to user mail address, its working. I have distribution group or group with mail address on AD and users as member of this groups. But when i send mail to group mail address, its not working Dovecot-lda can

Good. I am going to focus on the IMAP configuration and worry about SMTP later. The following is the relevant documentation. This is very straightforward: https://doc.dovecot.org/admin_manual/ssl/dovecot_configuration/ My file 10-ssl.conf is untouched. However, this is the part that I would like to better understand: https://doc.dovecot.org/admin_manual/ssl/certificate_creation/ Before

Hi, I successfully configured dovecot using virtual users (and LDAP/AD). deliver is the LDA and verifies if the user exists (as recommended in the WIKI). However, the howtos in the Wiki say *nothing* about the case that the recipients should be verified *before* receiving the messages (prevent backscatter, ...). All configurations in the dovecot-Wiki (postfix and exim) just accept the mails

Had a surprising event on C 6.5. Exim was the only MTA installed. It was partially configured (with ACL, Router, Transport) and definitely not running. I was remotely testing a web page. A web page error condition invoked the embedded PHP mail() command. To my astonishment something in Centos woke-up Exim. Exim sent the email and then became inactive again. The Exim logs does not show any

I've found what I think is an inconsistency in the Maildir quota implementation. According to the Maildir++ quota specification at: http://www.inter7.com/courierimap/README.maildirquota.html Maildir++ quota can be specified as maximum size, or maximum number of messages, or even both. The size specification is supposed to be in bytes. So I could use '10000000S' to set a quota of