vBouncer : Change thread subscribtion options for members with bouncing emails

Update April 5th: Step 2A for vBulletin 3 Gold added.

What vBouncer does
vBouncer will reduce your server load, bandwidth, and your forum admin in-box, by unsubscribing members who keep bouncing their emails back to your forum admin email, which may bomb your mail box if you have a busy forum with many members who subscribe to many threads, but their emails are either invalid, inbox full, or have ISP problems.

Screen shots
None, this is a command line script, with some changes in functions.php

Who may want to use this?
1. Very busy sites, with thousands of notifications a day.
2. Your admin box gets too many bouncing emails
3. You use Postfix or Sendmail. I'm not sure how this works on other mail servers, please let me know if this works with QMail, or Exism.

Caution
This may drive some of your members mad If their email bounces a lot, this script will modify their subscriptions from their favourite threads. They will have to fix their email account, and then modify their subscribtion manually to each thread again... This may not be due to bad emails, just ISP-side problems.

Use at your own risk. I'm sharing this since some indicated interest at vBulletin.com in this thread:
http://www.vbulletin.com/forum/showt...threadid=71496
I'd be glad to help answer questions, but as with most hacks, it is your responsibility....

Installation
1. Create a unique email address on your server, dedicated to catch bouncing emails. Do not use adminemail, or any other existing email that you want to receive through a POP account. This email will be used only to catch bouncing emails.

Recommended name (makes for less editing): subscriber_notify

2. For vB 3.0.3 (older versions below, steps 2a or 2b)

I have yet to upgrade to 3.0.3, so this is contributed by ScottA:

Originally Posted by ScottA

I got this running on 3.0.3. IIRC, what you need to do is open mail.php and look for this:

PHP Code:

    function Mail($toemail, $subject, $message, $headers, $fromemail, $minusf = false)
        {
            if ($minusf)
            {
             $this->success = @mail($toemail, $subject, $message, trim($headers), "-f $fromemail");
            }
            else
            {
             $this->success = @mail($toemail, $subject, $message, trim($headers));
            }
        } 


And change it to this:

PHP Code:

    function Mail($toemail, $subject, $message, $headers, $fromemail, $minusf = false)
        {
            if ($minusf)
            {
             $this->success = @mail($toemail, $subject, $message, trim($headers), "-f subscriber_notify@yourdomain.com");
            }
            else
            {
             $this->success = @mail($toemail, $subject, $message, trim($headers), "-f subscriber_notify@yourdomain.com");
            }
        } 


Note: You need to replace "subscriber_notify@yourdomain.com" with the email created in step 1.

2a. For vB3 gold
Edit functions.php

Find:

PHP Code:

       if ($vboptions['needfromemail'])
       {
         @mail($toemail, $subject, $message, trim($header), "-f $vboptions[webmasteremail]");
       }
       else
       {
           @mail($toemail, $subject, $message, trim($header));
       } 


Replace with (replace subscriber_notify@example.com with the email from step 1:

PHP Code:

   @mail($toemail, $subject, $message, trim($header), "-fsubscriber_notify@example.com"); 


2b. For older, vB3 beta versions
Edit functions.php

Find:

PHP Code:

                   // send those mails
                 if ($vboptions['needfromemail'])
                   {
                     @mail($email['toemail'], $email['subject'], $email['message'], trim($email['header']), "-f $vboptions[webmasteremail]");
                   }
                   else
                   {
                     @mail($email['toemail'], $email['subject'], $email['message'], trim($email['header']));
                   } 


Replace with (replace subscriber_notify@example.com with the email from step 1:

PHP Code:

                   // vBouncer hack
                 // Replace subscriber_notify email@example.com with the email from step 1
                 mail($email['toemail'], $email['subject'], $email['message'], trim($email['header']), "-fsubscriber_notify@example.com");
                   // end hack 


3. Copy vBouncer.pl.txt to a directory on your server above apache level. vBouncer.pl.txt is attached below.

Rename it to vBouncer.pl by typing:

mv vBounver.pl.txt vBouncer.pl

Make it executable by typing:

chmod +x vBouncer.pl

4. Edit the configuation section of vBouncer.pl

   #! /usr/bin/perl -w
   #
   # USAGE: ./vBouncer.pl -bounce : to unsubscribe threads from members with bouncing email
   #        ./vBouncer.pl : with no parameters to see (test) who will be unsubscribed
   #
   
   # Config:
   my $bouncelimit = 10;   # how many bounced emails are allowed, before taking actions
   my $downgrade = 0;      # What subscription level you will assign to bouncing members?
                           # 0 = No email, member will check subscribed thread through usercp
                           # 1 = Instant email, bad choice!
                           # 2 = Daily
                           # 3 = Weekly
   
 my $clearmailfile = 1;	# delete the mail file for bounced email when done (only deletes when -bounce option is used)
   
   my $bouncefile = "/var/spool/mail/subscriber_notify";
                           # the path/to/bouncing emails file. "subscriber_notify is the email name, you need
                           # to change it to the email name you chose for bouncing emails.
   
   
   my $db="database";        # mysql database name
   my $db_host="localhost";                # mysql host
   my $db_username="username";             # mysql username
   my $db_password="password";             # mysql password
   # end of config

5. Once a day or once a week (depending on the size of the spool size), you can run the scropt manually, or through a cron job. When done, you have to clear the email file, otherwise it will keep unsubscribing members whos emails no longer bounce.

To run the script in test mode, type:

./vBounver.pl

To run the script in bouncer mode, type:

./vBounver.pl -bouncer

To clear the mail box, use:
cat /dev/null > subscriber_notify
(or set the option in the script to do it)

Changes
Feel free to modify and post changes here or as new hacks, no credir or permission required. I may eventually add some features when I have the time.

Notes

1. The script assumes that Perl is installed @ /usr/bin/perl

If you have Perl installed elsewhere, you just need to update the first line of the script with the cirrect path:

#! /usr/bin/perl -w

2. You need to login to your server with a username that has write access to the mail spool, like a root/admin level user.

3. When run in test mode, ignore the warning "Use of uninitialized value in string eq at ./vBouncer.pl line 49" It just means you did not pass a parameter.

[kmike]

My point is, there're too many MTAs sending out non-RFC compliant DSN's out there. For some insight, look at the Mail:eliveryStatus::BounceParser perl module source. I guess eventually you'll write something similar using PHP
Here's qmail bounce I was speaking of:

From MAILER-DAEMON  Wed Jun 22 08:27:25 2005
Return-Path: <MAILER-DAEMON>
Received: from mxavas2.aruba.it (mx3.aruba.it [62.149.128.132] (may be forged))
        by xxxxxxxxxxxx with SMTP id j5MDR182012646
        for xxxxxxxxxxxxxxx; Wed, 22 Jun 2005 08:27:07 -0500
Message-Id: xxxxxxxxxxxx
Received: (qmail 2289 invoked for bounce); 22 Jun 2005 13:26:56 -0000
Date: 22 Jun 2005 13:26:56 -0000
From: MAILER-DAEMON@mxavas2.aruba.it
To: xxxxxxxxxx
Subject: failure notice

Hi. This is the qmail-send program at mxavas2.aruba.it.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<lmasali@demo.eu.blackberry.net>:
193.109.81.50 does not like recipient.
Remote host said: 550 5.2.1 <lmasali@demo.eu.blackberry.net>... Mailbox disabled
 for this recipient
Giving up on 193.109.81.50.

--- Below this line is a copy of the message.

Return-Path: xxxxxxxxxxx
.....................

Here's one from MS exchange:

From MAILER-DAEMON  Wed Jun 22 13:23:23 2005
Return-Path: <MAILER-DAEMON>
Received: ...........
Received: from huey.opc.bbhc ([10.2.18.30])
 by txuspipas004.unitedsurgical.com (SMSSMTP 4.1.4.30) with SMTP id M20050622131
85703364
 for xxxxxxxxxx; Wed, 22 Jun 2005 13:18:58 -0500
Received: by huey.unitedsurgical.com with Internet Mail Service (5.5.2653.19)
        id <M04CR85P>; Wed, 22 Jun 2005 13:19:15 -0500
Message-ID: <514220978E9FD211B11000805F0D0A79217BF258@huey.unitedsurgical.com>
From: System Administrator <postmaster@ortholink.net>
To: xxxxxxxxxx
Subject: Undeliverable: Reply to post 'Mountain Models Sportana Biplane'
Date: Wed, 22 Jun 2005 13:19:14 -0500
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-MS-Embedded-Report: 
Content-Type: Text/Plain

Your message

  To:      stahlmangc@ortholink.net
  Subject: Reply to post 'Mountain Models Sportana Biplane'
  Sent:    Wed, 22 Jun 2005 13:12:17 -0500

did not reach the following recipient(s):

stahlmangc@ortholink.net on Wed, 22 Jun 2005 13:19:10 -0500
    The recipient name is not recognized
        The MTS-ID of the original message is: c=us;a=
;p=ortholink;l=HUEY0506221819M04CR853
    MSEXCH:IMS:Ortholink:Information Technologies:HUEY 0 (000C05A6) Unknown
Recipient

Also, some MTAs send X-Failed-Recipients header instead of standard one.

[tamarian]

Good luck with re-writing the script.

My request for help still stands, if anyone here has a decent sized sample for their server's bounced emails, please send them my way. If I can't scan/test them, I won't be able to support them. Currently can identify Postfix, Sendmail, QMail and Exim based on samples files I received. Windows still a mystery.