similar to: Delivering locally through the Submission Server

> what should it do with the non local messages or local messages directly > at aliases? OK, so I gather that the Submission Server cannot do that (yet). My suggestion for a future version would then be: How about running dovecot-lda, if the user happens to be local, or a local alias? Or at least provide some sort of pattern matching: anything matching *@example.com , pass the message to

On Mon, Nov 02, 2020 at 09:33:08PM +0100, R. Diez wrote: > OK, so I gather that the Submission Server cannot do that (yet). And probably would never do. It isn't its job description. Actually, it is just a convenience/workaround feature, which comes handy only if your own MTA cannot handle dovecot's SASL authentication (must be something real strange) or there are some

On Sun, Oct 18, 2020 at 11:14:26PM +0200, John Fawcett wrote: > can you check if the missing emails are in the new directory on host B? I cannot now. I did not think about that possibility when listing the contents of directories and have not checked the new directory. > My guess is that the missing emails appeared on host A in new and were > replicated to host B in new. Then the imap

Op 12-12-2017 om 15:28 schreef Tanstaafl: > This is fantastic Stephan! Especially since I'll soon be rolling a new > Dovecot server to act as a backup for our current Office 365 mail, as > well as to be prepared in case I can ever talk the boss into migrating > back to dovecot (we were using Dovecot for a really long time until he > was convinced by others that we 'had'

> On December 20, 2017 at 4:39 PM Tanstaafl <tanstaafl at libertytrek.org> wrote: > > > On Sat Dec 16 2017 15:41:25 GMT-0500 (Eastern Standard Time), Tanstaafl > <tanstaafl at libertytrek.org> wrote: > > Ok, well, my ignorance is probably glaring here, but what I meant was, > > the make the BURL/URLAUTH pieces strictly between Dovecot and the > >

On 12/16/2017, 5:10:14 AM, Stephan Bosch <stephan at rename-it.nl> wrote: > Op 12/14/2017 om 6:07 PM schreef Tanstaafl: >> One other point. >> >> Adding support for something like this that also requires Clients to add >> support for it is just begging for a feature that never gets used. >> >> Stephan, are you sure there is no (fairly simple) way to

On 13.12.2017 21:41, Tanstaafl wrote: > On 12/12/2017, 1:39:08 PM, Stephan Bosch <stephan at rename-it.nl> wrote: >> However, keep in mind that for this particular feature we're just >> providing the "chicken" as it were. The "egg", i.e. client support, is >> still to come. Apart from Trojita (which I think is still not widely >> used), I

One other point. Adding support for something like this that also requires Clients to add support for it is just begging for a feature that never gets used. Stephan, are you sure there is no (fairly simple) way to make this an SMTP service that any email client that supports SMTP can use? On 12/14/2017, 10:57:44 AM, Tanstaafl <tanstaafl at libertytrek.org> wrote: > On 12/14/2017,

Hi, As some of you know, I started implementing the SMTP submission proxy a few years ago. It acts as a front-end for any MTA, adding the necessary functionality for an SMTP submission service, also known as a Mail Submission Agent (MSA) (https://tools.ietf.org/html/rfc6409). The main reason I created this, back then, was implementing the BURL capability (https://tools.ietf.org/html/rfc4468). The

Hi Everyone! I've setup dovecot 2.3.2.1 on a Gentoo server. I want to configure the submission service in order to replace the corresponding part in Postfix (which is my SMTP server). I configured submission it with just a few options different of the default ones: submission_client_workarounds = whitespace-before-path submission_relay_host = 127.0.0.1 submission_relay_port = 10026

On 02/11/2020 20:17, R. Diez wrote: > 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 a proxy in front of an MTA. You can't avoid having an MTA somewhere in your solution. https://doc.dovecot.org/admin_manual/submission_server/ > > The

Hi, I am a long-time dovecot user/admin for my family mail server, but I had ventured into configuring replication only recently and I am not sure about how it should work and what are the good practices. My intent for replication was to have another instance to switch to in a short time if something fails. I have daily backups, but it will take much more time to rebuild and restore than just to

Hi all! I am a long-time dovecot user/admin on my home server, but only recently tried to configure replication. Everything seems to work except sieve scripts replication. When I upload new one on the server A, it does not replicate to server B, even if it seemingly tries to, according to debug logs. The log antry says: Replication requested by 'sieve_storage_sync_transaction_begin',

On Sat, Oct 17, 2020 at 11:17:34PM +0200, John Fawcett wrote: > > I have observed my mail storage directories on both instances and have > > noticed that they diverge a little over time - the instance B not having > > all the updates. However the moment I connect another client to instance > > B and log in as a particular user, the state on instance B springs to the >

Hello, I'm setting up Dovecot 2.3.2.1 as a submission proxy to a Postfix backend server. Dovecot announces CHUNKING, but the Postfix backend does not support (or announce) it. HELO from Postfix: 220 backend.mydomain.com ESMTP Postfix (Ubuntu) ehlo test 250-backend.mydomain.com 250-PIPELINING 250-SIZE 104857600 250-VRFY 250-ETRN 250-STARTTLS

Hello, What would be the best way to implement "deliver mail to multiple maildirs" through LMTP in Dovecot? Like in Postfix virtual_maps. Thank you! Best wishes, Janis

Hi all, I have dockerized my dovecot setup. Everything works fine besides auto-responder using sieve. Issue is that the my dovecot docker image does NOT come with a SMTP which could be used for outgoing mail. My SMTP setup (postfix) is in another image/container. I want to keep it that way, so that dovecot and postfix have separate images. So basically I have 2 containers running in the

On 09/20/2018 12:56 PM, Robert Schetterer wrote: > Am 20.09.2018 um 11:04 schrieb Michael Goth: >> Hello, >> >> I'm setting up Dovecot 2.3.2.1 as a submission proxy to a Postfix >> backend server. Dovecot announces CHUNKING, but the Postfix backend >> does not support (or announce) it. >> >> HELO from Postfix: >> >> ?? 220

This is fantastic Stephan! Especially since I'll soon be rolling a new Dovecot server to act as a backup for our current Office 365 mail, as well as to be prepared in case I can ever talk the boss into migrating back to dovecot (we were using Dovecot for a really long time until he was convinced by others that we 'had' to be on Office 365). I'll also be setting up a shiny new VPS

Hello, I'm having trouble configuring the submission proxy. I have configured the submission service as follow: submission_host = smtp.example.com submission_relay_host = localhost submission_relay_port = 8587 submission_relay_rawlog_dir = /var/log/dovecot/ submission_relay_trusted = yes My main issue is that until I login, dovecot-submission won't connect to the backend and query the