Minimally maintained

The PAM Auth module is based vaguely on a skeleton of the IMAP Auth module (http://drupal.org/project/imap_auth).

OG Contact provides a contact module style contact form for Organic Groups, and optionally provides a "Contact" tab on the group's main page.

Features

• Administrators can enable/disable group contact forms on a per group basis, or enable/disable contact forms for all groups at once.
• The recipients of form submissions can be the administrators of that Organic Group and/or a list of user defined recipients.
• Group admins can optionally be allowed to edit the information on their group's contact form, including recipients, and reply message.
• Contact form access can be restricted to a group's members.
• Group members be made contact form recipients if they have the "receive og contact submissions" permission.
• Administrators may create custom "Additional Info" text per group. Optionally, group administrators who can edit form settings may be allowed to add and edit this text as well.

Version for Drupal 7.x

There is D7 version in the works. Follow the D7 issue for updates.

Currently there is no supported upgrade path from 6.x to 7.x.

The D7 code is not ready for use in production. So far this is only available for testing, and may likely break.

Upgrading from 5.x to 6.x

The Role Contact module creates a "staff list" from the profiles of users in a particular role, e.g. "staff role". The user list is formatted via theme functions, with convenient header and footer fields. The sort order of users can be set via weights. A configurable subset of profile data is shown in the user list view, along with the user's picture along with a link to a per-user page, showing a (potentially different) subset of profile data. In addition, in both the list and per-user views, each user has a contact form - and is preallocated with a contact form category based on their name - that allows site visitors (both authenticated and anonymous) to send email to each user without revealing the user's email address.

The normal use case: a company or organisation wants to list a subset of its users as a "staff list". Some more senior staff members (e.g. CEO, president, directors, etc.) should be listed at the top, others alphabetically. Only some of each staff member's profile data should be shown - other data is only internally visible. It should be possible for site visitors to contact staff, but without revealing the staff member's email address directly to minimise snarfing of those addresses by spambots.

Note: this module has only been tested with MySQL.

The netFORUM Views module relies on the netFORUM xWeb Interface and netFORUM Dynamic Facade Nodes

Signatures for Forums tweaks signatures in ways inspired by other traditional forum software.

1. when a user changes their signature, all their posts will be updated;
2. signatures are automatically added to posts, instead of being inserted into the post text;
3. the administrator can choose the input filter for signatures, allowing BBCode -- if the BBCode module is installed -- or HTML to be used;
4. signatures are longer than the the Drupal default
5. conditional signatures, these are hidden, or rel=nofollow'd if a post is under a particular length;
6. show signature only once per conversation;

This module was developed for The Webmaster Forums (who have recently moved to Drupal--yes, we do like Drupal's forum!)