From: B. A. <bri...@am...> - 2011-01-21 10:26:25
|
Dear all, I just released the new version of wxSMTP. It now includes support for POP3 protocol. This is still a pre-release and shall still be tested on various platforms, with different configurations. Major modifications are : - pop3 protocol support - full support of mime format, thanks to the integration of the mimetic project. - partial encoding support for various charsets (shall be still completed for support for sent mails) - remodeling of the API for an integration of POP3 protocol. It is provided with two samples : one for example of SMTP protocol usage, and the second for POP3 usage. I am still waiting for an approval of renaming of the project. I really think that wxSMTP is now no more valid, as this project hanldes other mail protocol. I think that wxEMail would be more appropriate. I also have problems with SourceForge release mechanism. The one explained in the Maintainer Guide of wxCode site is no more valid. When users click on the 'dowload' button of the wxSMTP project page of the wxCode site, they do not go to proper download page of sourceForge site. Regards, Brice André |
From: Ulrich T. <ulr...@gm...> - 2011-01-22 09:04:42
|
Hello André, > I just released the new version of wxSMTP. It now includes support > for POP3 protocol. Great. > I am still waiting for an approval of renaming of the project. I > really think that wxSMTP is now no more valid, as this project > hanldes other mail protocol. I think that wxEMail would be more > appropriate. I agree. wxEMail is fine with me. I would propose to name the folder in the wxCode SVN just "email". > I also have problems with SourceForge release mechanism. The one > explained in the Maintainer Guide of wxCode site is no more valid. > When users click on the 'dowload' button of the wxSMTP project page > of the wxCode site, they do not go to proper download page of > sourceForge site. I'll check this issue as soon as possible. Regards, Ulrich |
From: B. A. <bri...@am...> - 2011-01-22 09:12:15
|
Hello Ulrich, First of all, thanks for your investment in your new role for the wx community. The proposed name in SVN is fine for me. Regards, Brice On Sat, 22 Jan 2011 10:04:27 +0100, Ulrich Telle <ulr...@gm...> wrote: > Hello André, > >> I just released the new version of wxSMTP. It now includes support >> for POP3 protocol. > > Great. > >> I am still waiting for an approval of renaming of the project. I >> really think that wxSMTP is now no more valid, as this project >> hanldes other mail protocol. I think that wxEMail would be more >> appropriate. > > I agree. wxEMail is fine with me. I would propose to name the folder in > the wxCode SVN just "email". > >> I also have problems with SourceForge release mechanism. The one >> explained in the Maintainer Guide of wxCode site is no more valid. >> When users click on the 'dowload' button of the wxSMTP project page >> of the wxCode site, they do not go to proper download page of >> sourceForge site. > > I'll check this issue as soon as possible. > > Regards, > > Ulrich > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better > price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > wxCode-users mailing list > wxC...@li... > https://lists.sourceforge.net/lists/listinfo/wxcode-users |
From: Ulrich T. <ulr...@gm...> - 2011-01-22 13:21:33
|
Hello André, > The proposed name in SVN is fine for me. Ok. I renamed your component's SVN repository from 'smtp' to 'email'. Please update the template 'index.php' in your component's website folder to reflect the name, location, purpose etc. of your component and inform me if you're done, since I have to manually execute an update script to reflect the changes on the wxCode website. Unfortunately SourceForge doesn't allow cron jobs to perform such tasks automatically. Even sending mail from website scripts is prohibited (at least at the moment). >>> I also have problems with SourceForge release mechanism. The one >>> explained in the Maintainer Guide of wxCode site is no more valid. I'm going to revise all wxCode guide pages, but that may take a while. In the meantime please don't hesitate to ask if something doesn't work as expected. >>> When users click on the 'dowload' button of the wxSMTP project page >>> of the wxCode site, they do not go to proper download page of >>> sourceForge site. I changed the download links to point to the wxCode 'Components' release package list. Regards, Ulrich |
From: B. A. <bri...@am...> - 2011-01-22 14:49:29
|
Hello Ulrich, Thanks for your fast answer. Sorry to bother you with all my questions, but as I am new with wxCode, there are a lot of small things I still do not master. I read your comment about website. In fact, I never wrote the website part of the component. I did not understood the part concerning the update of the wxCode site. When you say that you have to run a script to update the website, does it mean that each time I want to modify my component website page, you will have to re-run that script ? The problem is that I do not know exactly how to fill this index.php file (folder names, links, etc). Thus, if I have no way of testing it before you run your script, I will probably have to bother you several times before having something that works correctly... I will update all other stuff (library name in bakefile, upload of the doc on site, update of the links in wiki, forum, etc) as soon as possible, but it will probably take a few days as I am quite busy for the moment. Thanks for your help, Kind Regards, Brice On Sat, 22 Jan 2011 14:21:14 +0100, Ulrich Telle <ulr...@gm...> wrote: > Hello André, > >> The proposed name in SVN is fine for me. > > Ok. I renamed your component's SVN repository from 'smtp' to 'email'. > > Please update the template 'index.php' in your component's website > folder to reflect the name, location, purpose etc. of your component and > inform me if you're done, since I have to manually execute an update > script to reflect the changes on the wxCode website. > > Unfortunately SourceForge doesn't allow cron jobs to perform such tasks > automatically. Even sending mail from website scripts is prohibited (at > least at the moment). > >>>> I also have problems with SourceForge release mechanism. The one >>>> explained in the Maintainer Guide of wxCode site is no more valid. > > I'm going to revise all wxCode guide pages, but that may take a while. > In the meantime please don't hesitate to ask if something doesn't work > as expected. > >>>> When users click on the 'dowload' button of the wxSMTP project page >>>> of the wxCode site, they do not go to proper download page of >>>> sourceForge site. > > I changed the download links to point to the wxCode 'Components' release > package list. > > Regards, > > Ulrich > > > ------------------------------------------------------------------------------ > Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)! > Finally, a world-class log management solution at an even better > price-free! > Download using promo code Free_Logger_4_Dev2Dev. Offer expires > February 28th, so secure your free ArcSight Logger TODAY! > http://p.sf.net/sfu/arcsight-sfd2d > _______________________________________________ > wxCode-users mailing list > wxC...@li... > https://lists.sourceforge.net/lists/listinfo/wxcode-users |
From: Ulrich T. <ulr...@gm...> - 2011-01-22 15:52:34
|
Hello André, > Sorry to bother you with all my questions, but as I am new with > wxCode, there are a lot of small things I still do not master. Don't hesitate to ask. I'll try to answer as good as I can. (I have still to learn some of the administrative details, too.) > I read your comment about website. In fact, I never wrote the website > part of the component. I did not understood the part concerning the > update of the wxCode site. When you say that you have to run a > script to update the website, does it mean that each time I want to > modify my component website page, you will have to re-run that script > ? Well, when the wxCode project started SourceForge allowed to run cron jobs. The idea was, that each component maintainer maintains a webpage for his component in a subfolder 'website' of his component in SVN. The cron job copied the contents of those subfolders in SVN to the wxCode website. This was quite convenient since one had to deal only with a single location where to apply changes, namely SVN. Now that SourceForge doesn't allow cron jobs any more the process has to be done manually. The alternative would be that each component maintainer administrates his component's web pages within the wxCode website himself. Accessing the wxCode website should be possible for each registered maintainer via SFTP using host web.sourceforge.net and username <sf-userid>,wxcode (replace <sf-userid> by the maintainer's SourceForge user id) and his SourceForge password. It would require some effort and discipline from each maintainer, but would be certainly an option. What do the other component maintainers think about this? > The problem is that I do not know exactly how to fill this index.php > file (folder names, links, etc). Thus, if I have no way of testing it > before you run your script, I will probably have to bother you > several times before having something that works correctly... There are comments in the template and pointers to further documentation (although not all of it might be up-to-date). Example: Replace in the template MYCOMPNAME => wxEMail MYCOMPSUBDIR => email and inspect the corresponding files in other components. This should give you an impression what to do. In case of further questions just post on this list or send a private mail. Regards, Ulrich |
From: Ulrich T. <ulr...@gm...> - 2011-01-22 13:29:25
|
Hello André, one thing I forgot to mention: I renamed the file release package as well. So please change the download links accordingly for example in your wxForum announcement and wherever else you used the name wxSMTP. It's now wxEMail. Regards, Ulrich |