 |
There are over a million messages in root's email box on web1. There is a python script (cron) that generates mail every two minutes of the day. "/var/spool/mail/root": 1,288,345 messages 330,475 new 1,288,345 unread |
|
|
The poller.py script is generating an error and runs every two minutes. It was touched in 2014, and the only thing the cron entry does is call poller.py (no notes) rpm -qf /usr/share/rhn/virtualization/poller.py tells us that the file comes from rhn-virtualization-host-5.4.54-2.el5sat package rpm -qi rhn-virtualization-host shows us details about the package yum remove rhn-virtualization-host Took care of the problem by removing the package and it's corresponding cron job that was doing nothing. If we want to setup virtualization at some point, then we can do so. Subject: Cron <root@d905-1> python < /usr/share/rhn/virtualization/poller.py libvir: Xen Daemon error : unable to connect to 'localhost:8000': Connection refused |
|
|
Mail messages are going out as expected from the Wiki Jun 21 14:57:12 d905-1 postfix/pickup[27492]: 2C88C855ECF: uid=0 from=<root> |
 |
Nice work question: do you know if additional user could be added as wgConfirmAccountContact ? Should we create a google group ? See https://www.mediawiki.org/wiki/Extension:ConfirmAccount#Usage |
|
|
Archiving email sent to Greg: I didn't get the email either. Looking at the code, it looks like there are other options: Adding users to a group with "confirmaccount-notify" should do the job: |
|
|
Thanks JC, I did that actually. I assigned the 'confirmaccount-notify' permission to the sysop group so that all Administrators would get notified. And I also set myself to be the named contact in $wgConfirmAccountContact to simultaneously test the 'single user notification method'. Then I made a fake request to test it. User "Foo" I don't have permission to see the results in http://wiki.slicer.org/slicerWiki/index.php/Special:ConfirmAccounts but I can tell you that I did NOT receive the notification email. This is especially curious because email does work. If the $wgConfirmAccountContact setting is not working, then it won't matter if that is a single person or a Google Groups list. As an aside, I tried to use the maintenance script of createAndPromote to make myself a member of the bureaucrat group, but the script fails silently (even after I adjusted it for the fact that we're running an older version of PHP). So, the issue might be bigger than just a setting. I believe the settings are all appropriate now. $wgGroupPermissions['sysop']['confirmaccount-notify'] = true; So, to summarize the current status: Requestor receives email notification / chance to verify email address The problem is that nobody is notified internally of the account request... Bureaucrats must still manually check http://wiki.slicer.org/slicerWiki/index.php/Special:ConfirmAccounts Also, the bio page of the user does not seem to be created by the form (grundlett bio was >50 words on the account request yet is empty in the wiki) |
|
|
User "grundlett" has been added to the bureaucrat group. Let me know if you would like to also be added to the Administrator group.
This is indeed confirmed by looking at http://wiki.slicer.org/slicerWiki/index.php/Special:ListGroupRights
Looking at the code in [1], it is executed only "if this token is in the pending requests". Now, if I look at your user rights or mine, I can see that there is a: "Implicit member of: Autoconfirmed users" In your case, I could read that before adding you to the "Bureaucrat" group. Could the issue be incorrect settings associated with https://www.mediawiki.org/wiki/Manual:Autoconfirmed_users ? |
|
|
I set $wgMakeUserPageFromBio = true so that something useful would appear in User pages by default for new users. Since we require a 50 word Bio in the account sign-up process, I think the user would assume that it is used. When the setting is 'false' then the Bio is hidden away in the database and not shown on the user's User:page. (FYI, you can lookup a user Biography at http://wiki.slicer.org/slicerWiki/index.php/Special:UserCredentials) In the account review process, if an account is legitimate (thus approved), but there is some content that is explicitly or generally frowned upon (promotional copy) in the bio, then the reviewer/approver should make an edit to the user page with an explanation. The bio is plain text in the form. p.s. I'm just hacking on the system and promoting what I think are reasonable best practices. I'm not the authority on how the Slicer wiki should operate. If anything I do is counter to SPL/Slicer standard practices then by all means let me know. |
|
|
Sounds very reasonable. In the mean time, I added an entry in the FAQ to document what you reported: Consider updating as you see fit. We will review and discuss them during the upcoming Developer hangout. |
|
|
The ConfirmAccount process appears to be working as intended now. I've confirmed that the data is correctly loaded into the database [Extension is working] I've confirmed that the email sub-system is working. Direct mail is nearly instantaneous. (I also cleared the root user's mbox backlog which was not an issue on web2 where slicer wiki lives, but was an issue on web1 -- the /var/spool/mail/root file was huge) Here is an example of a /var/log/maillog entry: There was only one 'ConfirmAccount' message delivered/received by all Administrators (for new user "LiorG"). All other test requests were not received. The difference seems to be that LiorG verified his email address. Then I tested this assumption by requesting an account for 'runman' / admin@rundlett.com. This Account Request worked flawlessly. Below, I've included the source of the one delivered message (in response to the email address verification event). The SPF is neutral -- which indicates we can improve the SPF records for this domain. There is some intermediary spam filtering taking place (X-IronPort-Anti-Spam-Filtered), and that process is opaque. There could be some spam filter at Partners which could potentially filter ConfirmAccount or other messages before they are delivered to intended recipients. Delivered-To: greg@equality-tech.com "LiorG" has requested an account and is waiting for confirmation. |
|
|
The next request that comes in where the requestor verifies his/her email address should be received by all Users in the Administrator group. This enables the team to act on New Account requests in a timely manner. |
|
|
Nice detective work :) and thanks for the report. I confirm I receive account requests. Closing. |
|
|
The wording on the Account Reqest page was a bit off looking up the interface message keys I found the key for the initial field group and edited the instructions describing the process, as well as adding a parenthetical comment to the bio section https://www.slicer.org/slicerWiki/index.php/MediaWiki:Requestaccount-acc-text |
- Anonymous
