Re: Problem with Bounce feature of Plugin Spam Buttons

View: New views
1 Messages — Rating Filter:   Alert me  

Re: Problem with Bounce feature of Plugin Spam Buttons

by Paul Lesniewski :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

>> here is a new set of headers from an email I just tried to bounce.
>>
>> The original sender was from info@....  According
>> to
>> my config.php file the mail should have been bounced to
>> ham@....  Instead I receieved another copy of the email.
>
> OK, thanks very much.  The immediate problem I see is that the TO: field
> was not changed.  Not sure why that'd be, but you might want to just
> uncomment one of the "ReSent" headers in bounce_send.php to see if it's
> even doing anything it should... around line 192:
>
> //$header[] = 'ReSent-Date: ' . $date . $rn;
>
> Uncomment it and see if that header appears in the message after it is
> bounced.
>
> In fact, just above that is a bunch of code that deals with the FROM:
> and TO: addresses, which appears to possibly be broken.  You can put in
> some echo lines there to see what's going on.  Also, spit out the value
> of $send_to (or $_GET, where it comes from).  In fact, that might be the
> problem.  The spam_buttons plugin modifies $_GET directly to fool the
> bounce code (stolen directly from the bounce plugin (which is why I am
> surprised that works but this plugin doesn't)) into using the correct
> sent_to address.  Line 317 of functions.php is where it does this, so
> you can dump out (sm_print_r()) the contents of $_GET before/after that
> and see if you are getting what you expect.
>
>   - paul
>
>> -- begin header --
>> Received: from stygia.stygianresearch.com (stygia.stygianresearch.com
>> [127.0.0.1])
>>      by stygia.stygianresearch.com (8.12.11/8.12.11) with ESMTP id
>> j5GKnkc1002901
>>      (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO)
>>      for <bradley@...>; Thu, 16 Jun 2005 16:49:46
>> -0400
>> Received: (from apache@localhost)
>>      by stygia.stygianresearch.com (8.12.11/8.12.11/Submit) id
>> j5GKnkv5002900;
>>      Thu, 16 Jun 2005 16:49:46 -0400
>> Received: from 208.3.193.194
>>      (SquirrelMail authenticated user bradley);
>>      by stygianresearch.com with HTTP;
>>      Thu, 16 Jun 2005 16:49:46 -0400 (EDT)
>> X-Received: from webserver2.rsglab.com (webserver2.rsglab.com
>> [69.20.10.82]
>>      (may be forged)) by stygia.stygianresearch.com (8.12.11/8.12.11)
>>      with SMTP id j5FFvvGT013354 for <bradley@...>; Wed,
>>      15 Jun 2005 11:57:57 -0400
>> X-Received: (qmail 14917 invoked by uid 524); 15 Jun 2005 14:56:55 -0000
>> Date: 15 Jun 2005 14:56:55 -0000
>> Message-ID: <20050615145655.14916.qmail@...>
>> To: bradley@...
>> Subject: Jeff Foxworthy - Blue Collar TV - RSVP
>> From: info@...
>> X-stygianresearch.com-MailScanner: Found to be clean, Found to be clean
>> X-stygianresearch.com-MailScanner-SpamCheck: not spam,
>>      SpamAssassin (score=1, required 6, NO_REAL_NAME 1.00), not spam,
>>      SpamAssassin (score=1.302, required 6, DATE_IN_PAST_24_48 0.30,
>>      NO_REAL_NAME 1.00)
>> X-stygianresearch.com-MailScanner-SpamScore: s, s
>> Status: RO
>> X-UID: 140
>> MIME-Version: 1.0
>> X-stygianresearch.com-MailScanner-Information: Please contact the ISP
>> for
>> more information
>> X-stygianresearch.com-MailScanner-From: bradley@...
>> Content-Length: 4013
>> X-Keywords:
>>
>> -- end  header --
>>
>>>>On Thu, June 16, 2005 3:50 pm, Paul Lesneiwski said:
>>>>
>>>>
>>>>>Bradley Leonard wrote:
>>>>>
>>>>>
>>>>>>Hi,
>>>>>>
>>>>>>I've installed and configured the "Spam Buttons" plug v1.0.  I have
>>>>>>been
>>>>>>able to configure the buttons to send email to my spam/not spam
>>>>>>accounts
>>>>>>as an attachment, but I'm unable to get the bounce feature to work.
>>>>>> If
>>>>>>I
>>>>>>set it up to bounce, I can see the email get generated but the email
>>>>>>just
>>>>>>gets sent off site, not to my spam/not spam accounts.
>>>>>>
>>>>>>If I use the bounce plugin v 0.5-1.4 and specify either my spam/not
>>>>>>spam
>>>>>>account, the message is send to the mailbox.
>>>>>>
>>>>>>I'm using squirrelmail v1.4.4 installed from rpm on FC2.
>>>>>>
>>>>>>Any help anybody can give, I'd appreciate it.  Thanks.
>>>>>
>>>>>Show headers of outgoing mail or anything else that tells us what the
>>>>>problem is.  It's too hard to guess what's going wrong when you don't
>>>>>show the details of the problem.
>>>>>
>>>>> - paul
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>------------------------------------------------------------------------
>>>>>>
>>>>>><?php
>>>>>>
>>>>>>global $show_spam_buttons_on_read_body,
>>>>>>$show_spam_buttons_on_message_list,
>>>>>>      $show_spam_link_on_read_body, $is_spam_shell_command,
>>>>>>$is_spam_resend_destination,
>>>>>>      $is_not_spam_shell_command, $is_not_spam_resend_destination,
>>>>>>      $show_not_spam_button, $spam_button_text,
>>>>>> $not_spam_button_text,
>>>>>>      $spam_report_email_method, $is_spam_subject_prefix,
>>>>>>$is_not_spam_subject_prefix,
>>>>>>      $show_is_spam_button, $spam_report_smtpServerAddress,
>>>>>>$spam_report_smtpPort,
>>>>>>      $spam_report_useSendmail, $spam_report_smtp_auth_mech,
>>>>>>$spam_report_use_smtp_tls,
>>>>>>      $sb_debug;
>>>>>>bindtextdomain('spam_buttons', SM_PATH . 'locale');
>>>>>>textdomain('spam_buttons');
>>>>>>
>>>>>>
>>>>>>
>>>>>>//
>>>>>> -------------------------------------------------------------------
>>>>>>//
>>>>>>// GENERAL OPTIONS
>>>>>>//
>>>>>>
>>>>>>
>>>>>>// You may change the button text, but if you do, there is a good
>>>>>>// chance that those buttons will ONLY be displayed in one language
>>>>>>//
>>>>>>$spam_button_text = _("Spam");
>>>>>>$not_spam_button_text = _("Not Spam");
>>>>>>
>>>>>>
>>>>>>
>>>>>>// You can turn either of the buttons on/off as needed
>>>>>>//
>>>>>>// 0 = don't display button, 1 = display button
>>>>>>//
>>>>>>$show_not_spam_button = 1;
>>>>>>$show_is_spam_button = 1;
>>>>>>
>>>>>>
>>>>>>
>>>>>>// Show spam buttons on message list page?
>>>>>>//
>>>>>>// 0 = no, 1 = yes
>>>>>>//
>>>>>>$show_spam_buttons_on_message_list = 1;
>>>>>>
>>>>>>
>>>>>>
>>>>>>// Show spam link when reading a message?
>>>>>>//
>>>>>>// 0 = no, 1 = yes
>>>>>>//
>>>>>>$show_spam_link_on_read_body = 1;
>>>>>>
>>>>>>
>>>>>>
>>>>>>// Show spam buttons when reading a message?
>>>>>>//
>>>>>>// NOTE: This is only functional as of
>>>>>>//       SquirrelMail 1.5.0
>>>>>>//
>>>>>>// 0 = no, 1 = yes
>>>>>>//
>>>>>>$show_spam_buttons_on_read_body = 1;
>>>>>>
>>>>>>
>>>>>>
>>>>>>// Debugging: Turning this on will dump out the command text, the
>>>>>>//            message body and the results of the spam report if
>>>>>>//            done using a shell command.
>>>>>>//            If reported via email (attachment method only), you
>>>>>>//            currently only get the destination address and a
>>>>>>//            parsed version of the message body being reported.
>>>>>>//
>>>>>>// Note that you will get more verbose output from a sa-learn
>>>>>>// command if you add the -D flag to the commands below (make sure
>>>>>>// to remove it when you are done debugging!).
>>>>>>//
>>>>>>// 0 = off, 1 = on
>>>>>>//
>>>>>>$sb_debug = 0;
>>>>>>
>>>>>>
>>>>>>
>>>>>>//
>>>>>> -------------------------------------------------------------------
>>>>>>//
>>>>>>// REPORT-BY-SHELL COMMAND OPTIONS
>>>>>>//
>>>>>>// Be sure if you use this that you have NOT turned on
>>>>>>// reporting by email.
>>>>>>//
>>>>>>
>>>>>>
>>>>>>// If you use a command-line utility for reporting spam/non-spam,
>>>>>>// this is where you set it up.  This plugin will append " < message"
>>>>>>// to the end of such a command (without the quotes), where "message"
>>>>>>// will be a file containing the full message as it was originally
>>>>>>// received.
>>>>>>//
>>>>>>// If you need to include any information about the user for which
>>>>>>// the report is being made, you can use these constants in your
>>>>>>command:
>>>>>>//
>>>>>>//    ###EMAIL_ADDRESS###            Will be replaced with the user's
>>>>>>//                                   full email address
>>>>>>//
>>>>>>//    ###USERNAME###                 Will be replaced with the
>>>>>> username
>>>>>>//                                   portion of the user's email
>>>>>>address
>>>>>>//
>>>>>>//    ###DOMAIN###                   Will be replaced with the domain
>>>>>>//                                   portion of the user's email
>>>>>>address
>>>>>>//
>>>>>>//
>>>>>>// Sample for CRM114:
>>>>>>//
>>>>>>//$is_spam_shell_command = '/usr/bin/crm -u /home/crm114
>>>>>> mailfilter.crm
>>>>>>--learnspam';
>>>>>>//$is_not_spam_shell_command = '/usr/bin/crm -u /home/crm114
>>>>>>mailfilter.crm --learnnonspam';
>>>>>>//
>>>>>>//
>>>>>>// Sample for SpamAssassin:
>>>>>>//
>>>>>>//$is_spam_shell_command = '/usr/bin/sa-learn --spam
>>>>>>--configpath=/etc/spamassassin -p /root/.spamassassin/user_prefs';
>>>>>>//$is_not_spam_shell_command = '/usr/bin/sa-learn --ham
>>>>>>--configpath=/etc/spamassassin -p /root/.spamassassin/user_prefs';
>>>>>>//
>>>>>>//
>>>>>>// Sample for SpamAssassin per-user configuration:
>>>>>>//
>>>>>>//$is_spam_shell_command = '/usr/bin/sa-learn --spam
>>>>>>--username=###EMAIL_ADDRESS###';
>>>>>>//$is_not_spam_shell_command = '/usr/bin/sa-learn --ham
>>>>>>--username=###EMAIL_ADDRESS###';
>>>>>>//
>>>>>>//
>>>>>>// Advanced sample for SpamAssassin:
>>>>>>//
>>>>>>// In order to make sure you are running sa-learn as the correct user
>>>>>>(else it will be
>>>>>>// run as the user that your web server runs as), you may need to run
>>>>>>the command with
>>>>>>// sudo.  In /etc/sudoers, you will want to set this:
>>>>>>//
>>>>>>// web_server_user   ALL=(sa_user) NOPASSWD: /usr/bin/sa-learn,
>>>>>>/usr/bin/spamassassin
>>>>>>//
>>>>>>// Where you need to change "web_server_user" to the actual userID of
>>>>>>the user running
>>>>>>// your web server, and "sa_user" to the user that should run
>>>>>> sa-learn
>>>>>>(or spamassasin).
>>>>>>//
>>>>>>// After that, one of the following command pairs should work for you
>>>>>>(remember to
>>>>>>// replace "sa_user" with the correct username):
>>>>>>//
>>>>>>//$is_spam_shell_command = 'sudo -u sa_user /usr/bin/sa-learn
>>>>>> --spam';
>>>>>>//$is_not_spam_shell_command = 'sudo -u sa_user /usr/bin/sa-learn
>>>>>>--ham';
>>>>>>//
>>>>>>//$is_spam_shell_command = 'sudo -u sa_user /usr/bin/spamassassin -r
>>>>>>--configpath=/etc/spamassassin -p /root/.spamassassin/user_prefs';
>>>>>>//$is_not_spam_shell_command = 'sudo -u sa_user /usr/bin/spamassassin
>>>>>>-k
>>>>>>--configpath=/etc/spamassassin -p /root/.spamassassin/user_prefs';
>>>>>>//
>>>>>>//
>>>>>>//
>>>>>>//$is_spam_shell_command = '';
>>>>>>//$is_not_spam_shell_command = '';
>>>>>>
>>>>>>//
>>>>>> -------------------------------------------------------------------
>>>>>>//
>>>>>>// REPORT-BY-EMAIL OPTIONS
>>>>>>//
>>>>>>// Be sure if you use this that you have NOT turned on
>>>>>>// reporting by shell command.
>>>>>>//
>>>>>>
>>>>>>
>>>>>>// If you resend the message in order to report it as spam/non-spam,
>>>>>>// specify the destination address here.
>>>>>>//
>>>>>>//$is_spam_resend_destination = 'spam_report';      // let SM append
>>>>>>user's domain automatically
>>>>>>//$is_not_spam_resend_destination = 'not_spam_report';
>>>>>>$is_spam_resend_destination = 'spam';
>>>>>>$is_not_spam_resend_destination = 'ham';
>>>>>>
>>>>>>
>>>>>>
>>>>>>// When reporting via email, should the message be resent (leaving
>>>>>>// all message headers intact), or should it be sent as an
>>>>>> attachment?
>>>>>>//
>>>>>>// resend = 'bounce'
>>>>>>// attach = 'attachment'
>>>>>>//
>>>>>>//$spam_report_email_method = 'bounce';
>>>>>>$spam_report_email_method = 'attachment';
>>>>>>
>>>>>>
>>>>>>
>>>>>>// When reporting via email (at least when sending as attachment),
>>>>>> you
>>>>>>// may indicate any extra subject information here (default empty)
>>>>>>//
>>>>>>// When set to "SPAM", the subject might end up looking like "[SPAM:
>>>>>>Buy
>>>>>>our product!]"
>>>>>>//
>>>>>>//$is_spam_subject_prefix = 'SPAM';
>>>>>>//$is_not_spam_subject_prefix = 'HAM';
>>>>>>$is_spam_subject_prefix = '';
>>>>>>$is_not_spam_subject_prefix = '';
>>>>>>
>>>>>>
>>>>>>
>>>>>>// You may also specify overrides for the SMTP server for the
>>>>>>// email only (see SquirrelMail's main configuration file or
>>>>>>// use config/conf.pl to understand what these settings normally
>>>>>>// are).
>>>>>>//
>>>>>>// Set to empty strings to use system defaults.
>>>>>>//
>>>>>>$spam_report_smtpServerAddress = '';
>>>>>>$spam_report_smtpPort = '';
>>>>>>$spam_report_useSendmail = '';
>>>>>>$spam_report_smtp_auth_mech = '';
>>>>>>$spam_report_use_smtp_tls = '';
>>>>>>
>>>>>>
>>>>>>
>>>>>>bindtextdomain('squirrelmail', SM_PATH . 'locale');
>>>>>>textdomain('squirrelmail');
>>>>>>?>
>>>>>

Anyone still having these problems?

--
Paul Lesniewski
SquirrelMail Team
Please support Open Source Software by donating to SquirrelMail!
http://squirrelmail.org/donate_paul_lesniewski.php

------------------------------------------------------------------------------
Crystal Reports - New Free Runtime and 30 Day Trial
Check out the new simplified licensing option that enables
unlimited royalty-free distribution of the report engine
for externally facing server and web deployment.
http://p.sf.net/sfu/businessobjects
-----
squirrelmail-plugins mailing list
Posting guidelines: http://squirrelmail.org/postingguidelines
List address: squirrelmail-plugins@...
List archives: http://news.gmane.org/gmane.mail.squirrelmail.plugins
List info (subscribe/unsubscribe/change options): https://lists.sourceforge.net/lists/listinfo/squirrelmail-plugins