The answer to this one is that the password for the email account (pop3) is not set in the cron. Don't take it as gospel though.An addition to what I've posted above.
If there is just one account to process subscriptions, unsubscriptions and bounces, and the cron is set to check every 5 - 10 minutes, then most likely people will run into problems with all those processes going on.
I'll wait until your programmer comes in Kurt, but I'll still run tests on the script as it is.
John
>From: root@secure.y86.net (Cron Daemon)
>To: admin1@secure.y86.net
>Subject: Cron <admin1@secure>
>/home/virtual/site1/fst/var/www/cgi-bin/gbomb/zinebomb.cgi
>/cron/
>X-Cron-Env: <SHELL=/bin/sh>
>X-Cron-Env: <HOME=/home/virtual/site1/fst>
>X-Cron-Env: <PATH=/usr/bin:/bin>
>X-Cron-Env: <LOGNAME=admin1>
>
>ZineBomb - ERROR:
>cannot log in POP3 server
>Context: localhost
>Reason: Bad login
>Did I do something wrong ??
>
>Tasari
>Internet Marketing Warrior
>http://airline-tickets.bestsecrets.com/airline-tickets.html