Thanks! We (and I) try our best to build an active community...
No doubt you all succed on it and I'm (we) are the ones to be thankfull.
OJS is becoming an extremally useful development and I must say that none of the questions were left without feedback.
a) When you enable the allow_envelope_sender option, the "Bounce Address" option on Setup page 1 will become active.
Yes, I found it, but I was reporting that this field is aways enabled (at least with my OJS 2.1.1 and Firefox 1.5), nevermind how I set the allow_envelope_sender variable. Probably it's just my installation, so don't worry about it.
b) The development version of OJS supports Captcha tests for user registration and anonymous comments. This won't guarantee that you have a valid email address, but if your concern is about spammers, this should provide at least a partial solution. I've successfully back-ported this into OJS 2.1.1 releases, so if it's a critical feature for you, I can provide instructions.
In any case, I'll bring up the email validation suggestion with the team; it certainly won't be part of the next release, but we may decide to include it in the future.
Thanks asmecher. Captcha will be a nice feature but I can wait util it will be officially released. Please, let me know if this requirement is finally accepted.
I reported all this to my fellows, and they answered that it's something mandatory for them to ensure (at least) the users' and commenters' emails before they open the magazine, so looks like I will need to find a an alternative solution.
As far as I'm the only one in a hurry... I will need to code this feature by by own (yes, you all must be affraid. I'm the worst coder in the world).
So any clue about which one could be the best approach to develop a kind of "traditional autentication" for OJS?
I though in a couple of solutions:
1) Patch (also called "dirty hack" ): Review your code and include some hacks in the authentification process, as well as a new attribute in the DB schema.
2) New Authorization plugin: The new authorization workflow will need some new logic and a new table (to avoid changing OJS schema and able to store the "still not accepted users"). Valid users will be transfered to the original OJS users' table.
Seams quite obvius that second choice is cleaner and nicer with OJS (and probably LDAP plugin could be a good example to follow), but I'm unsure about which one will take more time, if I can find further documentation or if I missed a third or forth approach to develop this feature as my fellows request.
Hummm... long mail again. Sorry for this.
Thanks a lot in advance for your unvaluable help,