similar to: RFC 4468

Hi Timo, There was another thread (it has come up at least a few times in the past few years I've been lurking) on the postfix list about having some kind of automatic 'Save to Sent' option to avoid the users mail client from having to upload messages twice (obviously the only ones of concern are ones with large attachments) - once to send it, and once to save the copy in the sent

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

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'

> 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 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

v2.2 hg now has support for NOTIFY extension. The only thing missing is support for SubscriptionChange events. Now would be a good time for IMAP clients to start implementing and testing it. :) I remember K9 developers at least said they were just waiting for Dovecot to support it first. v2.2 implements some other extensions also: BINARY, CATENATE and MOVE. Stephan has also implemented URLAUTH

Hello. I am not subscribed and new here, so first of all i want to thank you for dovecot. I personally do not use it in "production" (yet), but it is my sole point of interaction for testing the little MUA i maintain for quite some years. I also have used its code for affirmation purposes. (Interesting that OAUTHBEARER treats hostname and port as optional. I currently do

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,

Hello and good evening. Sorry for responding so late, it is midsummer and i spend as much time as possible on the outside (bicycle, mostly). (Just one more day, then 10 degrees colder!!) I Cc: Wietse Venema, because i quote a message of him. (this is "set quote-add-cc" here.) Aki Tuomi wrote in <84881193.5398.1597934431687 at appsuite-dev-gw2.open-xchange.com>: The dovecot

On 1/27/2016 1:30 AM, Steffen Kaiser <skdovecot at smail.inf.fh-brs.de> wrote: > Sending bandwitdh can be reduced by using BCC instead of the IMAP append > to the sent mailbox. Hi Steffen, Can you elaborate on this? I would have thought that the IMAP Append command would *save* bandwidth (as opposed to having the client save a copy to the Sent folder, thereby uploading the full

> 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

Thank you Timo for beginning the port of URLAUTH, BURL, and CATENATE from 1.2 to 2.0. Attached please find two patches that finish the port to 2.0. One patch updates the dovecot-2.0-urlauth branch and is based on the tip of that branch. The other patch adds the full support to dovecot-2.0.beta5. The resulting URLAUTH/BURL/CATENATE code is the same. Please let me know if you have any questions

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

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

> On 03/11/2020 12:31 Piotr Auksztulewicz <dcml at hasiok.net> wrote: > > > 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

Now that netflix is in Australia, I wouldn't mind giving it a burl. It's working fine on my fedora-21 lappy with chrome-40 but not on our centos-6 mythtv setup even with chrome-41. I understand the difference might be the version of NSS - fedora-21 has 3.17 while centos is stuck at 3.16. Other than that, I'm flumoxed. Anyone got netflix running on centos-6? Cheers Bob

Sigh, In the interest of moving forward on this project I've given up trying to get Dovecot to support mailboxes, rather I've tweaked around in qmail and had it deliver into a mail directory on a disk, that isn't NFS mounted. That got me past the various locking complaints and "operation not supported" on home directories that were mounted from the NetApp filer. Going as

Sorry if this seems elementary - but a question on implementation/usage/purpose of this.? My understanding is at this time the SMTP proxy server is only that - it does not implement any further functionality.? So its availability now is purely for testing purposes.? Is that accurate? I secondly assume that this intended for trusted clients only - so this is not intended for processing email

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On Mon, 24 Feb 2014, Charles Marcus wrote: > On 2/24/2014 3:58 AM, Steffen Kaiser <skdovecot at smail.inf.fh-brs.de> wrote: >> I would add a BCC recipient in the MTA. It's more save in such situation. >> See the thread about qmail and multiple recipients for one mail address. > > The only downside to this is all of