![]() ![]() Once it is working then you can create a pull request back to the source, and Martin can decide what happens from there. I think that if delivery queue is important enough for you to want to fork on github and then implement, then just do it. we don't help spammers (eg silent installs of SMTP sending only) ![]() easy to use, and default configurations both reasonable and safeĦ. customisable, so that other features can be added via scripting where only some users will use the featureĥ. backwards compatible (don't break stuff when you upgrade)Ĥ. StartTLS is excellent, and was very high on the list until it got added, but there are heaps of other good ideas waiting to happen.īeing number 4 doesn't need we need to do the other three first.ģ. I like this program, and love supporting it, but we need to keep development moving forward. Would love the help and assistance from a real programmer or two (I'm talking to both Dravion and SorenR, and any others who may be watching). I'm currently building a dedicated development machine, and once that is sorted I will be looking more and more at this code, and plan to bring some of these these feature requests to implementation. I do an OK job with VB, but my C++ skills are pretty poor. Not all of Bill's fixes made it into the official builds (In fact we weren't using GitHub at first, but SVN. The problem we had then was that the modified source were hard to get. This is what Bill was doing for a few years while Martin was absent, from here - busy with life. Dravion wrote:I think we can fork hMailServer and enque fix/feature-patches if needed and compile our own builds.Absolutely ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |