Re: dbmail configuration

--===============4419854677835093180==
Content-Type: multipart/alternative;
 boundary="=_a587691ac2b0592e39712e355f8edd94"

--=_a587691ac2b0592e39712e355f8edd94
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8

I have to say I had no issues with 2.4 to 3.0 to 3.1 and 3.2 either.
worked fine for me (but i have only 3 users .. although my database is
>100GB anyway since I keep all my old mails (except the junk mail of course). 

that said .. who is still using it and would be interested  in merging
stuff / .. ? so far I count 3 people maybe 4? 

I certainly want to keep using it if I can since I like the concept..
though some things do need fixing (like the slow folder list
fetching,..) 

I do plan to try writing a STored Procedure for the folder list fetching
and test that at some point but i don't have an ETA for that .. the
"risk" is that I would likely only do it for postgresql since that is
what I am using.. 

On 2020-04-06 11:05, Andrea Brancatelli wrote:

> I'm talking about latest commits, not about 3.0 to 3.1 
> 
> BTW I did all the transitions from 2.4 to 3.0 to 3.1 quite smoothly so I don't exactly get all your stress about this topic. 
> 
> And, like you do, in our company we have a lot of custom code relying on the SQL base os dbmail so I understand the cost of dealing with the SQL base changing. Yet again in our pro/cons valuations, it's cheaper to adapt our software to the evolutions than to adopt a new mail server. 
> 
> Do your balances and act accordingly. 
> 
> ---
> 
> Andrea Brancatelli
> 
> On 2020-04-06 10:52, Reindl Harald wrote: 
> 
> Am 06.04.20 um 10:44 schrieb Andrea Brancatelli: There are no upgrade for the SQL base coming in, so you'll be able go
> just upgrade the software without any issue. 
> this is simply not true at all
> 
> there is some sequence colum added and i can't find my mail from years
> ago how to handle it in my admin backend which has capabilities to move
> messages from the admin backends between folders and even users
> 
> otherwise clients will go out of sync
> 
> Am 06.04.20 um 10:38 schrieb Andrea Brancatelli: You all realise there are a lot of commit coming in on GitHub, right?
> 
> https://github.com/dbmail/dbmail/commits/master 
> if nobody manages releases tha don't help much
> 
> given my expierience back when upgrade to 3.0 and especially 3.1 that#s
> the reason that i even don't consider update to 3.2
> 
> in both cases 3ö0 and 3.1 we had massive issues like completly empty
> mails with pop3, all sort of broken mails over imap depending on the
> mail body at reconstruction and it#s even unclear if all the bugfix fopr
> latest 3.1 made it to github
> 
> when i face similar issues as with the latest point update swith a non
> existent upstream making quick bugfiox releases i can commit suicide
> 
> On 2020-04-06 10:25, Daniel Urstöger wrote:
> 
> if you can that esaily.... and the uqaliuty of dovecot is also
> shitty, i
> know one which swicthed, just other rpoblems and never update short
> after a release
> 
> i have implemented 6000 lines of code for backends, automation and
> infrastructure integration back in 2009 and spent hundrest of ours to
> get the fucking 3.0 and 3.1 versions debugged and then upstream
> disappears from one day to another 
> I understand that people are very upset but by now everyone should
> realize that Paul has dropped the project and moved on. Dbmail came
> free and is open source so be happy while it lasted and be grateful to
> Paul, he made an awesome product!
> 
> So whilst the move to GitHub was brilliant its just one of the
> projects which is hard to maintain, as IMAP, LMTP, etc. are not easy
> to understand protocols so it never got much traction there and to be
> honest there are surely not so many C-savvy  people out there these
> days as well as the few pull request that came in didn't get merged
> and there wasn't a successful fork.
> 
> Also since there are alternatives out there that work really well, I
> used courier for many years now and moved to dovecot later on, well,
> there is not much demand for dbmail and if Paul doesn't make a grand
> return, lets face it: dbmail won't progress.
> 
> So, I also spent a great deal of time with dbmail setups and I even
> wrote a whole webmail application for it, which specifically blew away
> roundcube and others because it could fetch data directly from the
> database layer, but well, thats the past lets move on.
 _______________________________________________
DBmail mailing list
[email protected]
https://lists.nfg.nl/cgi-bin/mailman/listinfo/dbmail 
_______________________________________________
DBmail mailing list
[email protected]
https://lists.nfg.nl/cgi-bin/mailman/listinfo/dbmail
--=_a587691ac2b0592e39712e355f8edd94
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3DUTF-8" /></head><body style=3D'font-size: 10pt; font-family: Verdana,Gen=
eva,sans-serif'>
<p>I have to say I had no issues with 2.4 to 3.0 to 3.1 and 3.2 either. wor=
ked fine for me (but i have only 3 users .. although my database is &gt;100=
GB anyway since I keep all my old mails (except the junk mail of course).</=
p>
<p>that said .. who is still using it and would be interested&nbsp; in merg=
ing stuff / .. ? so far I count 3 people maybe 4?</p>
<p>I certainly want to keep using it if I can since I like the concept.. th=
ough some things do need fixing (like the slow folder list fetching,..)</p>
<p>I do plan to try writing a STored Procedure for the folder list fetching=
 and test that at some point but i don't have an ETA for that .. the "risk"=
 is that I would likely only do it for postgresql since that is what I am u=
sing..</p>
<p>On 2020-04-06 11:05, Andrea Brancatelli wrote:</p>
<blockquote type=3D"cite" style=3D"padding: 0 0.4em; border-left: #1010ff 2=
px solid; margin: 0"><!-- html ignored --><!-- head ignored --><!-- meta ig=
nored -->
<p>I'm talking about latest commits, not about 3.0 to 3.1</p>
<p>BTW I did all the transitions from 2.4 to 3.0 to 3.1 quite smoothly so I=
 don't exactly get all your stress about this topic.</p>
<p>And, like you do, in our company we have a lot of custom code relying on=
 the SQL base os dbmail so I understand the cost of dealing with the SQL ba=
se changing. Yet again in our pro/cons valuations, it's cheaper to adapt ou=
r software to the evolutions than to adopt a new mail server.</p>
<p>Do your balances and act accordingly.</p>
<p><br /></p>
<div>---<br />
<pre><strong>Andrea Brancatelli
<span style=3D"color: #ff0000;"></span></strong></pre>
</div>
<p>On 2020-04-06 10:52, Reindl Harald wrote:</p>
<blockquote style=3D"padding: 0 0.4em; border-left: #1010ff 2px solid; marg=
in: 0;">
<div class=3D"pre" style=3D"margin: 0; padding: 0; font-family: monospace;"=
><br /> <br /> Am 06.04.20 um 10:44 schrieb Andrea Brancatelli:
<blockquote style=3D"padding: 0 0.4em; border-left: #1010ff 2px solid; marg=
in: 0;">There are no upgrade for the SQL base coming in, so you'll be able =
go<br /> just upgrade the software without any issue.</blockquote>
<br /> this is simply not true at all<br /> <br /> there is some sequence c=
olum added and i can't find my mail from years<br /> ago how to handle it i=
n my admin backend which has capabilities to move<br /> messages from the a=
dmin backends between folders and even users<br /> <br /> otherwise clients=
 will go out of sync<br /> <br />
<blockquote style=3D"padding: 0 0.4em; border-left: #1010ff 2px solid; marg=
in: 0;">
<blockquote style=3D"padding: 0 0.4em; border-left: #1010ff 2px solid; marg=
in: 0;">Am 06.04.20 um 10:38 schrieb Andrea Brancatelli:
<blockquote style=3D"padding: 0 0.4em; border-left: #1010ff 2px solid; marg=
in: 0;">You all realise there are a lot of commit coming in on GitHub, righ=
t?<br /> <br /> <a href=3D"https://github.com/dbmail/dbmail/commits/master"=
 target=3D"_blank" rel=3D"noopener noreferrer">https://github.com/dbmail/db=
mail/commits/master</a></blockquote>
<br /> if nobody manages releases tha don't help much<br /> <br /> given my=
 expierience back when upgrade to 3.0 and especially 3.1 that#s<br /> the r=
eason that i even don't consider update to 3.2<br /> <br /> in both cases 3=
&ouml;0 and 3.1 we had massive issues like completly empty<br /> mails with=
 pop3, all sort of broken mails over imap depending on the<br /> mail body =
at reconstruction and it#s even unclear if all the bugfix fopr<br /> latest=
 3.1 made it to github<br /> <br /> when i face similar issues as with the =
latest point update swith a non<br /> existent upstream making quick bugfio=
x releases i can commit suicide<br /> <br />
<blockquote style=3D"padding: 0 0.4em; border-left: #1010ff 2px solid; marg=
in: 0;">On 2020-04-06 10:25, Daniel Urst&ouml;ger wrote:<br /> <br />
<blockquote style=3D"padding: 0 0.4em; border-left: #1010ff 2px solid; marg=
in: 0;">
<blockquote style=3D"padding: 0 0.4em; border-left: #1010ff 2px solid; marg=
in: 0;">if you can that esaily.... and the uqaliuty of dovecot is also<br /=
> shitty, i<br /> know one which swicthed, just other rpoblems and never up=
date short<br /> after a release<br /> <br /> i have implemented 6000 lines=
 of code for backends, automation and<br /> infrastructure integration back=
 in 2009 and spent hundrest of ours to<br /> get the fucking 3.0 and 3.1 ve=
rsions debugged and then upstream<br /> disappears from one day to another<=
/blockquote>
<br /> I understand that people are very upset but by now everyone should<b=
r /> realize that Paul has dropped the project and moved on. Dbmail came<br=
 /> free and is open source so be happy while it lasted and be grateful to<=
br /> Paul, he made an awesome product!<br /> <br /> So whilst the move to =
GitHub was brilliant its just one of the<br /> projects which is hard to ma=
intain, as IMAP, LMTP, etc. are not easy<br /> to understand protocols so i=
t never got much traction there and to be<br /> honest there are surely not=
 so many C-savvy &nbsp;people out there these<br /> days as well as the few=
 pull request that came in didn't get merged<br /> and there wasn't a succe=
ssful fork.<br /> <br /> Also since there are alternatives out there that w=
ork really well, I<br /> used courier for many years now and moved to dovec=
ot later on, well,<br /> there is not much demand for dbmail and if Paul do=
esn't make a grand<br /> return, lets face it: dbmail won't progress.<br />=
 <br /> So, I also spent a great deal of time with dbmail setups and I even=
<br /> wrote a whole webmail application for it, which specifically blew aw=
ay<br /> roundcube and others because it could fetch data directly from the=
<br /> database layer, but well, thats the past lets move on.</blockquote>
</blockquote>
</blockquote>
</blockquote>
_______________________________________________<br /> DBmail mailing list<b=
r /> <a href=3D"mailto:[email protected]">[email protected]</a><br /> <=
a href=3D"https://lists.nfg.nl/cgi-bin/mailman/listinfo/dbmail" target=3D"_=
blank" rel=3D"noopener noreferrer">https://lists.nfg.nl/cgi-bin/mailman/lis=
tinfo/dbmail</a></div>
</blockquote>
<!-- html ignored --><br />
<div class=3D"pre" style=3D"margin: 0; padding: 0; font-family: monospace">=
_______________________________________________<br /> DBmail mailing list<b=
r /> <a href=3D"mailto:[email protected]">[email protected]</a><br /> <=
a href=3D"https://lists.nfg.nl/cgi-bin/mailman/listinfo/dbmail" target=3D"_=
blank" rel=3D"noopener noreferrer">https://lists.nfg.nl/cgi-bin/mailman/lis=
tinfo/dbmail</a></div>
</blockquote>
<p><br /></p>

</body></html>

--=_a587691ac2b0592e39712e355f8edd94--

--===============4419854677835093180==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: base64
Content-Disposition: inline

X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KREJtYWlsIG1h
aWxpbmcgbGlzdApEQm1haWxAbGlzdHMubmZnLm5sCmh0dHBzOi8vbGlzdHMubmZnLm5sL2NnaS1i
aW4vbWFpbG1hbi9saXN0aW5mby9kYm1haWwK

--===============4419854677835093180==--