search for: burl

...enting 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 main application of that capability -- together with IMAP URLAUTH -- is avoiding a duplicate upload of submitted e-mail messages; normally the message is both sent through SMTP and uploaded to the "Sent" folder through IMAP. Using BURL...

...hers that we 'had' to be on Office 365). > > I'll also be setting up a shiny new VPS for my own private mail server, > to provide better service that I currently get from my shared Dreamhost > account. > > But can you confirm... > > Would this also be called 'BURL' support? > > And will this initial implementation work with current Postfix to > provide the basic Save-To-Sent feature? > > I seem to recall there was some minor code required on the Postfix side, > and Wietse seemed to not have a problem implementing it, but had asked >...

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

...ort 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? > > It already is a normal compliant SMTP submission server. Just the BURL > part is something that requires additional client support. Ok, well, my ignorance is probably glaring here, but what I meant was, the make the BURL/URLAUTH pieces strictly between Dovecot and the backend SMTP server, make it invisible to the Client...

...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 > > backend SMTP server, make it invisible to the Client... > > So, I take it the no response to this means that there is no way to put > the BURL/URLAUTH parts such that only server support is needed, nothing > special on the clien...

...ever, 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 know of no IMAP client supporting BURL/URLAUTH for message >> submission. I'd expect to see it first for clients that can truly >> benefit; i.e., mobile clients such as K9. > Oh... bummer... > > I thought this was simply going to be an SMTP like service that any SMTP > client could utilize, keeping the BURL...

...i at dovecot.fi> wrote: >> On 13.12.2017 21:41, Tanstaafl wrote: >>> On 12/12/2017, 1:39:08 PM, Stephan Bosch <stephan at rename-it.nl> wrote: >>> I thought this was simply going to be an SMTP like service that any SMTP >>> client could utilize, keeping the BURL/URLAUTH pieces working only >>> between Dovecot and the MTA it works with. Meaning, instead of >>> connecting an SMTP service provided by Postfix, you connect to one >>> provided by Dovecot. I guess there is a good reason it couldn't be made >>> to work this...

...ong 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 for my own private mail server, to provide better service that I currently get from my shared Dreamhost account. But can you confirm... Would this also be called 'BURL' support? And will this initial implementation work with current Postfix to provide the basic Save-To-Sent feature? I seem to recall there was some minor code required on the Postfix side, and Wietse seemed to not have a problem implementing it, but had asked about any IMAP Clients supporting...

You know, I was thinking: wouldn't it be nice to have RFC 4468 (Message Submission BURL Extension) support in dovecot? Maybe we should ask the guys from Apple to contribute some support for it, I have a gut feeling they would gladly do so ;) Kind regards -- Erik.

...ission 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 main application of that > capability -- together with IMAP URLAUTH -- is avoiding a duplicate > upload of submitted e-mail messages; normally the message is both sent > through SMTP and uploaded to the "Sent" folder thro...

...e connection doesn't come from localhost. This causes issues with some smtp clients which authenticate (python smtpclient). When I telnet the submission service from localhost I get: 220 (protected hostname) Dovecot ready. EHLO L 250-(protected hostname) 250-8BITMIME 250-AUTH PLAIN LOGIN 250-BURL imap 250-CHUNKING 250-ENHANCEDSTATUSCODES 250-SIZE 250-STARTTLS 250 PIPELINING quit 221 2.0.0 Bye But when I do the same from another host other than the one running dovecot (telnetting the submission port): 220 (protected hostname) Dovecot ready. EHLO L 250-(protected hostname) 250-8BITMIME 250...

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

...n to exploitation this way, unless the > address is 127.0.0.1, in which case you can simply set up SASL over > Unix sockets, which is as secure as your host server is. > Submission service is not only a proxy, it - provides authentication natively from Dovecot - provides features like BURL, and maybe in future outbound Sieve but it does require real MTA behind. -- Aki

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

...te: > 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 know of no IMAP client supporting BURL/URLAUTH for message > submission. I'd expect to see it first for clients that can truly > benefit; i.e., mobile clients such as K9. Oh... bummer... I thought this was simply going to be an SMTP like service that any SMTP client could utilize, keeping the BURL/URLAUTH pieces working on...

...ients 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? It already is a normal compliant SMTP submission server. Just the BURL part is something that requires additional client support. Regards, Stephan. > > > On 12/14/2017, 10:57:44 AM, Tanstaafl <tanstaafl at libertytrek.org> wrote: >> On 12/14/2017, 3:03:41 AM, Aki Tuomi <aki.tuomi at dovecot.fi> wrote: >>> On 13.12.2017 21:41, Tans...

...hich which provides a forum for learning about the R package development process." (Double "which"). If this was not the proper list or the proper way to report such minor typos, please do let me know so that I will know better in the future. Thank you! Best, ----- Marie-Helene Burle (Marie) PhD candidate (Centre for Wildlife Ecology) R Data Peer (Research Commons) Writing Facilitator (Student Learning Commons) Data and Software Carpentry instructor RStudio Community sustainer Scientific Programming Study Group admin ----- Simon Fraser University (+1) 778 782-5618 http://www....

...ogin, dovecot-submission won't connect to the backend and query the capabilities and so won't report the right capabilities. That mean that the first EHLO message don't get the right capabilities list. " EHLO example.com 250-smtp.example.com 250-8BITMIME 250-AUTH PLAIN LOGIN 250-BURL imap 250-CHUNKING 250-ENHANCEDSTATUSCODES 250-SIZE 250 PIPELINING " This list don't contains VRFY, DNS, and SIZE is not specified (all of these is present in backend EHLO response). After login, if I send an new EHLO command, everything is properly reported. The raw log shows that unlike...

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

...DSTATUSCODES >> ?? 250-8BITMIME >> ?? 250 DSN >> >> >> HELO from Dovecot proxy: >> >> ?? 220 proxy.mydomain.com Dovecot ready. >> ?? ehlo test >> ?? 250-proxy.mydomain.com >> ?? 250-8BITMIME >> ?? 250-AUTH PLAIN LOGIN >> ?? 250-BURL imap >> ?? 250-CHUNKING >> ?? 250-ENHANCEDSTATUSCODES >> ?? 250-SIZE >> ?? 250-STARTTLS >> ?? 250 PIPELINING >> >> >> When a client sends BDAT, Postfix closes the connection. Here's a log >> snippet from Postfix: >> >> ?? < M...