I’m pretty happy with [...]]]> Well, I’ve finally deployed some production Openfiler ESA 2.99.1 machines as home-brew iSCSI boxes, primarily used for backups or low-stress virtual storage. Yes, they’re great — my basic write speeds on a Core 2 Duo box (recycled Dell Precision 390 workstation with 2GB of RAM and a single 1TB drive *no* RAID):

administrator@mail:/backup-iscsi$ sudo dd if=/dev/zero of=garbage bs=131072 count=20000
20000+0 records in
20000+0 records out
2621440000 bytes (2.6 GB) copied, 40.8493 s, 64.2 MB/s

I’m pretty happy with that. What I’m not please with is a 56MB log (/var/log/secure) filled with strange messages:

Jul 26 12:25:46 e0-002 sudo: openfiler : TTY=unknown ; PWD=/opt/openfiler/var/www/htdocs ; USER=root ; COMMAND=/usr/bin/uptime
Jul 26 12:25:46 e0-002 sudo: PAM unable to dlopen(/lib64/security/pam_gnome_keyring.so)
Jul 26 12:25:46 e0-002 sudo: PAM [error: /lib64/security/pam_gnome_keyring.so: cannot open shared object file: No such file or directory]
Jul 26 12:25:46 e0-002 sudo: PAM adding faulty module: /lib64/security/pam_gnome_keyring.so

Okay, so the first message isn’t strange. In fact, it’s normal. But I couldn’t figure out why a non-GUI (yes, it has a web interface, but no default window manager) distro was trying to load the Gnome keyring shared object. I still don’t know why. What I do know is how to get rid of this message:

1. Verify which PAM files reference this shared object:

1. [root@e0-002 pam.d]# cd /etc/pam.d/
   [root@e0-002 pam.d]# grep -i -n 'pam_gnome_keyring.so' *
   system-auth:5:# FL: Have (patched) pam_gnome_keyring.so grab the password before pam_unix.so
   system-auth:6:auth        optional      pam_gnome_keyring.so
   system-auth:16:password    optional      pam_gnome_keyring.so

2. In this instance, the ‘system-auth’ file contained these troublesome pam_gnome_keyring.so entries.
3. Fire-up your favorite text editor and comment those lines.
4. Reboot & enjoy a log without an absurd amount of irrelevant errors.

If you haven’t heard, RSTickets! is an advanced Joomla! Help Desk ticketing system that allows you (or a team of yous) to manage and keep track of your clients’ issues. It’s actually one of the few effective, useful Help Desk systems available for the Joomla! [...]]]>

If you haven’t heard, RSTickets! is an advanced Joomla! Help Desk ticketing system that allows you (or a team of yous) to manage and keep track of your clients’ issues. It’s actually one of the few effective, useful Help Desk systems available for the Joomla! 1.5+ framework that I would personally recommend. Unfortunately, it’s still under development and lacks certain features that one may desire, such as a read-only listing page that displays tickets already submitted to you or your department.

My Problem:

I noticed internal network clients were submitting several duplicate tickets related to a shared problem (i.e. printer trouble, network outages, etc.). I couldn’t blame them since they couldn’t view previously submitted tickets, so I decided to create a quick + dirty page that pulls “open,” or “on-hold,” tickets from a specific department’s table of submitted [active] tickets and displays them on a Joomla! article page (using the Sourcerer plug-in to execute custom PHP with {source} tags). Pasting this code into an article without the Sourcerer plug-in [or some sort of plug-in for executing PHP] will do nothing. Also note the include file for making a raw connection to your MySQL database. This is required (and should be stored in a directory with the appropriate permissions to prevent outside read access).

If you’d like to simply list the number (amount) of tickets (open, closed, on-hold) for all departments, you might want to check the unreleased version of RSJoomla!’s RSTicket Module.

{source}
<?php

include ("includes/connect_custom.php");

$result2 = mysql_query("SELECT * FROM jos_rstickets_tickets WHERE DepartmentId=3 AND (TicketStatus='open' OR TicketStatus='on-hold') ORDER BY TicketTime ASC") or die(mysql_error());

echo '<br />';

echo '<tr><td style="padding-bottom: 10px;" colspan="6">Please check the open, pending, or on-hold tickets listed below before submitting a support ticket. The list below can be utilized as an informal gauge for IT response times. If a duplicate support ticket is submitted, you may cancel it yourself or it will be deleted by the IT Department upon review. Thank you for your cooperation.</td></tr>';

echo '<tr><td style="font-size: 16px;font-weight: bold;padding-bottom: 10px;" colspan="6">SUBMITTED SUPPORT TICKETS:</td></tr>';

echo '<tr><td style="text-align:left; padding-bottom:7px;"><strong>Submitted:</strong></td><td style="padding-bottom:7px;"><strong>Username:</strong></td><td style="padding-bottom:7px;"><strong>Ticket Code:</strong></td><td style="padding-bottom:7px;"><strong>Subject:</strong></td><td style="padding-bottom:7px;"><strong>Status:</strong></td><td style="padding-bottom:7px;"><strong>Priority:</strong></td></tr>';

while($row = mysql_fetch_array($result2))

{

$custid =  $row['CustomerId'];
$userquery= mysql_query("SELECT name FROM jos_users WHERE id=$custid") or die(mysql_error());

$username = mysql_fetch_array($userquery);

echo '<tr style="font-size: 10px;vertical-align:top;"><td style="width: 102px; overflow: hidden;padding: 3px -10px 3px 3px;">' . date("Y-m-d H:m", $row['TicketTime']) .  '</td><td>' . $username['name'] . '</td><td>' . $row['TicketCode'] . '</td><td style="width: 235px; overflow: hidden;">' . $row['TicketSubject'] . '</td><td>' . strtoupper($row['TicketStatus']) . '</td>';

if ($row['TicketPriority']=='high'){

echo '<td style="background-color: red; color: white; font-weight: bold;padding-left: 5px;">';

} else if ($row['TicketPriority']=='normal'){

echo '<td style="background-color: blue; color: white; font-weight: bold;padding-left: 5px;">';

} else if ($row['TicketPriority']=='low'){

echo '<td style="background-color: yellow; font-color: black; font-weight: bold;padding-left: 5px;">';}

echo strtoupper($row['TicketPriority']) . '</td></tr>';

}

echo '<tr><td style="font-size:16px; padding-top: 20px; padding-bottom: 20px" colspan="6"><strong><a href="index.php?option=com_rstickets&Itemid=59"><img src="images/M_images/onsite_support1.jpg"></a><br /><a href="index.php?option=com_rstickets&Itemid=59">SUBMIT A NEW SUPPORT TICKET</a></strong></td></tr>';

echo '<br />';

?>
{/source}

connect_custom.php :

<?php

// Script:	connect_custom.php
// Author:	JR
// Date:	20080218
// Use:	    Utilized for custom DB connections to our current database for Fabrik Forms + Joomla 1.5

$hostname="localhost";
$mysql_login="thedude";
$mysql_password="sumpasswordhere";
$database="datablah";

if (!($db = mysql_pconnect($hostname, $mysql_login , $mysql_password))){
die("Can't connect to database server.");
}else{
if (!(mysql_select_db("$database",$db))){
die("Can't connect to database.");
}
}
?>

I had the pleasure of applying mandatory disclaimers [...]]]>

EDIT: I have since removed altermime after installing a MailScanner spam relay for our Zimbra server to use. Because, by default, MailScanner appends a default signature to all outbound email, it was very simple to modify the signature rules to accomodate our mandatory disclaimers for different domains.

I had the pleasure of applying mandatory disclaimers to all [outbound] emails at my workplace today… ~Joy~ … I had the assumption it’d be rather easy, but Altermime and Postfix were a bit finicky to work with. After editing the master.cf I ended up customizing my own ‘disclaimer’ shell script.

#!/bin/sh
INSPECT_DIR=/var/spool/filter
SENDMAIL=/opt/zimbra/postfix/sbin/sendmail

# Exit codes from
EX_TEMPFAIL=75
EX_UNAVAILABLE=69

# Clean up when done or when aborting.
trap "rm -f in.$$" 0 1 2 3 15

# Start processing.
cd $INSPECT_DIR || { echo $INSPECT_DIR does not exist; exit $EX_TEMPFAIL; }

cat > in.$$ || { echo Cannot save mail to file; exit $EX_TEMPFAIL; }

# Verify this mail is not incoming or internal-only
# We don't need disclaimers for either one of these cases.

# Debug:
#echo "output: $from_address" >> /tmp/tempoutput.txt

#Grab the from address:

from_address=`grep -m 1 "From:" in.$$ | cut -d "<" -f 2 | cut -d ">" -f 1`

#Verify whether your domain is in the from address.
#If it is, proceed to distinguish WHICH domain is sending outgoing mail and tag it appropriately:
#If not, then that would be incoming mail, so leave it alone:

#Additional (else if) conditional checks will be added to determine if the email is inner-office comm:
# to_address= `grep -m 1 "To:" in.$$ | cut -d "<" -f 2 | cut -d ">" -f 1`
# if [[ $from_address == *domain* && to_address == *domain* ]]; then ....
#
# This additional condition requires more debugging...

if [[ $from_address == *domain* ]]; then

# Debug:
#echo
#echo "FROM: $from_address" >> /tmp/tempoutput.txt
#echo "THIS GETS ALTERMIMED" >> /tmp/tempoutput.txt
#echo

#Check to see which domain is sending outgoing email,
#then tag it with the appropriate disclaimer:

if [[ $from_address == *subdomain.domain* ]]; then

# Debug		echo "THIS GETS APDD" >> /tmp/tempoutput.txt
/usr/bin/altermime --input=in.$$ \
--disclaimer=/opt/zimbra/postfix/conf/disclaimers/apd-disclaimer.txt \
--disclaimer-html=/opt/zimbra/postfix/conf/disclaimers/apd-disclaimer.txt \
--xheader="X-Public-Record:" || { echo Message content rejected; exit $EX_UNAVAILABLE; }
else
# Debug		echo "THIS GETS COAD" >> /tmp/tempoutput.txt
/usr/bin/altermime --input=in.$$ \
--disclaimer=/opt/zimbra/postfix/conf/disclaimers/coa-disclaimer.txt \
--disclaimer-html=/opt/zimbra/postfix/conf/disclaimers/coa-disclaimer.txt \
--xheader="X-Public-Record:" || { echo Message content rejected; exit $EX_UNAVAILABLE; }

fi
fi

# Might need to remove -i switch for truncation problems depending on your MTA version...

$SENDMAIL -i "$@" < in.$$

exit $?