Displaying 20 results from an estimated 3000 matches similar to: "v2.2 status update: IMAP NOTIFY extension and more"
2010 Jun 11
1
Patch: 2.0 support for URLAUTH, BURL, CATENATE
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
2010 Apr 09
4
Patch: support URLAUTH, BURL, CATENATE
Hello Dovecot community,
Below please find a patch that adds support to dovecot-1.2.11 for:
- RFC 4467 - IMAP URLAUTH Extension
- RFC 4468 - Submission BURL
- RFC 4469 - IMAP CATENATE Extension
URLAUTH
URLAUTH is added as a plugin so it can be disabled to satisfy site
security requirements.
Each user's URLAUTH keys for all mailboxes are stored in a file named
2013 Feb 25
2
v2.2.rc1 released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc1.tar.gz
http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc1.tar.gz.sig
A few fixes since beta2. Also added tcp and tcps (=tcp+ssl) targets for
dsync, where the destination needs to be a doveadm-server listener.
I'm planning on releasing v2.2.0 in 1-2 weeks if no major problems are
found. Please test and report any bugs found.
BTW. I've
2013 Feb 25
2
v2.2.rc1 released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc1.tar.gz
http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc1.tar.gz.sig
A few fixes since beta2. Also added tcp and tcps (=tcp+ssl) targets for
dsync, where the destination needs to be a doveadm-server listener.
I'm planning on releasing v2.2.0 in 1-2 weeks if no major problems are
found. Please test and report any bugs found.
BTW. I've
2010 Mar 04
5
Saving Sent Messages to Sent Folder
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
2013 Jun 16
5
v2.2.3 released
http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz
http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz.sig
This is a pretty important upgrade for v2.2 users, because of the IMAP
ENVELOPE reply fix.
* LDA/LMTP: If new mail delivery first fails with "temporary
failure", tempfail the whole delivery instead of falling back to
delivering the mail to INBOX. (Requires new Pigeonhole
2013 Jun 16
5
v2.2.3 released
http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz
http://dovecot.org/releases/2.2/dovecot-2.2.3.tar.gz.sig
This is a pretty important upgrade for v2.2 users, because of the IMAP
ENVELOPE reply fix.
* LDA/LMTP: If new mail delivery first fails with "temporary
failure", tempfail the whole delivery instead of falling back to
delivering the mail to INBOX. (Requires new Pigeonhole
2012 Oct 29
1
v2.2.alpha1 released
http://dovecot.org/releases/2.2/alpha/dovecot-2.2.alpha1.tar.gz
http://dovecot.org/releases/2.2/alpha/dovecot-2.2.alpha1.tar.gz.sig
I wanted to start stabilizing v2.2 release some months ago already, but
I somehow got stuck adding more and more features. Now it looks like all
of the necessary API changes are done, so everything I'm planning on
near future can still be added to v2.2 without
2012 Oct 29
1
v2.2.alpha1 released
http://dovecot.org/releases/2.2/alpha/dovecot-2.2.alpha1.tar.gz
http://dovecot.org/releases/2.2/alpha/dovecot-2.2.alpha1.tar.gz.sig
I wanted to start stabilizing v2.2 release some months ago already, but
I somehow got stuck adding more and more features. Now it looks like all
of the necessary API changes are done, so everything I'm planning on
near future can still be added to v2.2 without
2013 Mar 19
1
v2.2 status update
So, I'm still planning on getting v2.2.0 out Really Soon now.
Unfortunately I've had to quickly develop some rather large features
still at this stage. I was initially planning on leaving them for v2.3,
but they were a requirement for one project and implementing them now to
v2.2 was the least amount of trouble for me.
(And yes, I'm aware I haven't replied to a lot of emails in
2017 Dec 22
2
New Dovecot service: SMTP Submission (RFC6409)
> 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
> >
2017 Dec 12
2
New Dovecot service: SMTP Submission (RFC6409)
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'
2013 Apr 04
0
v2.2.rc4 released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc4.tar.gz
http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc4.tar.gz.sig
A lot of small random fixes. Some last minute major cleanups/fixes to
lib-http and lib-ssl-iostream error handling, which makes them much
easier to debug if something goes wrong (so e.g. if https site has
invalid certificate, the caller gets error message saying that,
including
2013 Apr 04
0
v2.2.rc4 released
http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc4.tar.gz
http://dovecot.org/releases/2.2/rc/dovecot-2.2.rc4.tar.gz.sig
A lot of small random fixes. Some last minute major cleanups/fixes to
lib-http and lib-ssl-iostream error handling, which makes them much
easier to debug if something goes wrong (so e.g. if https site has
invalid certificate, the caller gets error message saying that,
including
2017 Dec 14
2
New Dovecot service: SMTP Submission (RFC6409)
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
2013 Jan 07
2
v2.2.beta1 released
http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta1.tar.gz
http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta1.tar.gz.sig
Lots of fixes since 2.2.alpha1, especially related to dsync. Also dsync
now supports syncing private message flags when INDEXPVT is used.
Here's again the list of all the major changes in v2.2:
* When creating home directories, the permissions are copied from the
2013 Jan 07
2
v2.2.beta1 released
http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta1.tar.gz
http://dovecot.org/releases/2.2/beta/dovecot-2.2.beta1.tar.gz.sig
Lots of fixes since 2.2.alpha1, especially related to dsync. Also dsync
now supports syncing private message flags when INDEXPVT is used.
Here's again the list of all the major changes in v2.2:
* When creating home directories, the permissions are copied from the
2017 Dec 14
2
New Dovecot service: SMTP Submission (RFC6409)
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,
2017 Dec 16
3
New Dovecot service: SMTP Submission (RFC6409)
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
2017 Dec 11
5
New Dovecot service: SMTP Submission (RFC6409)
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