Re: [Mimedefang] Weird Issue in mimedefang-filter.

2015-11-09 Thread Peter Benac
OK  I uninstalled minedefang and spamassassin.  Wiped all traces of both
from the system.  Reinstalled both and now everyone is happy..  Just a weird
system quirk 

-Original Message-
From: mimedefang-boun...@lists.roaringpenguin.com
[mailto:mimedefang-boun...@lists.roaringpenguin.com] On Behalf Of Peter
Benac
Sent: Monday, November 9, 2015 16:16
To: mimedefang@lists.roaringpenguin.com
Subject: Re: [Mimedefang] Weird Issue in mimedefang-filter.

Sorry Matt.  I am looking at the default mimedefang-filter and the variable
name was a typo on my part.   $req and $hits  are both nulled out.

-Original Message-
From: mimedefang-boun...@lists.roaringpenguin.com
[mailto:mimedefang-boun...@lists.roaringpenguin.com] On Behalf Of Matt
Garretson
Sent: Monday, November 9, 2015 15:05
To: mimedefang@lists.roaringpenguin.com
Subject: Re: [Mimedefang] Weird Issue in mimedefang-filter.

On 11/9/2015 2:57 PM, Peter Benac wrote:
> everything is getting marked as spam.   For some reason in the subroutine
> filter_end between the call to spam_assassin_check and the call to 
> action_delete_header the contents of $reg and $hits is being stomped 
> on (set


You haven't given us any of your code, but using the example filter as a
reference, the variable is "$req" rather than "$reg".  Is that the issue?




___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang
mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang
mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang


Re: [Mimedefang] Weird Issue in mimedefang-filter.

2015-11-09 Thread Peter Benac
This turned out to be some quirkiness with Perl.   

Had to temp store the variables in newer variable and everything is now
working

-Original Message-
From: mimedefang-boun...@lists.roaringpenguin.com
[mailto:mimedefang-boun...@lists.roaringpenguin.com] On Behalf Of Peter
Benac
Sent: Monday, November 9, 2015 16:16
To: mimedefang@lists.roaringpenguin.com
Subject: Re: [Mimedefang] Weird Issue in mimedefang-filter.

Sorry Matt.  I am looking at the default mimedefang-filter and the variable
name was a typo on my part.   $req and $hits  are both nulled out.

-Original Message-
From: mimedefang-boun...@lists.roaringpenguin.com
[mailto:mimedefang-boun...@lists.roaringpenguin.com] On Behalf Of Matt
Garretson
Sent: Monday, November 9, 2015 15:05
To: mimedefang@lists.roaringpenguin.com
Subject: Re: [Mimedefang] Weird Issue in mimedefang-filter.

On 11/9/2015 2:57 PM, Peter Benac wrote:
> everything is getting marked as spam.   For some reason in the subroutine
> filter_end between the call to spam_assassin_check and the call to 
> action_delete_header the contents of $reg and $hits is being stomped 
> on (set


You haven't given us any of your code, but using the example filter as a
reference, the variable is "$req" rather than "$reg".  Is that the issue?




___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang
mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang
mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang


Re: [Mimedefang] Weird Issue in mimedefang-filter.

2015-11-09 Thread Peter Benac
Sorry Matt.  I am looking at the default mimedefang-filter and the variable
name was a typo on my part.   $req and $hits  are both nulled out.

-Original Message-
From: mimedefang-boun...@lists.roaringpenguin.com
[mailto:mimedefang-boun...@lists.roaringpenguin.com] On Behalf Of Matt
Garretson
Sent: Monday, November 9, 2015 15:05
To: mimedefang@lists.roaringpenguin.com
Subject: Re: [Mimedefang] Weird Issue in mimedefang-filter.

On 11/9/2015 2:57 PM, Peter Benac wrote:
> everything is getting marked as spam.   For some reason in the subroutine
> filter_end between the call to spam_assassin_check and the call to 
> action_delete_header the contents of $reg and $hits is being stomped 
> on (set


You haven't given us any of your code, but using the example filter as a
reference, the variable is "$req" rather than "$reg".  Is that the issue?




___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com MIMEDefang
mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang

___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang


Re: [Mimedefang] Weird Issue in mimedefang-filter.

2015-11-09 Thread Matt Garretson
On 11/9/2015 2:57 PM, Peter Benac wrote:
> everything is getting marked as spam.   For some reason in the subroutine
> filter_end between the call to spam_assassin_check and the call to
> action_delete_header the contents of $reg and $hits is being stomped on (set


You haven't given us any of your code, but using the example filter as a
reference, the variable is "$req" rather than "$reg".  Is that the issue?




___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang


[Mimedefang] Weird Issue in mimedefang-filter.

2015-11-09 Thread Peter Benac
Greetings all,

   I just installed Mimedefang and SpamAssassin on a Debian (Jesse)
VM.   For the most part everything seems to be working correctly; however,
everything is getting marked as spam.   For some reason in the subroutine
filter_end between the call to spam_assassin_check and the call to
action_delete_header the contents of $reg and $hits is being stomped on (set
to NULL). 

  I can see the two values set correctly after the return from
spam_assassin_check.  I have gone as far as commenting out everything
between the two calls. Nothing seems to work here.

     Perl = 5.20.2
 Linux  = Debian 8u5 (jesse)
     MimeDefang = 2.75-1 installed by apt-get
 SpamAssassin = 3.4.1    installed from CPAN

 Admittedly It’s been a number of years since I have run my own mail
server and dug into anything Perl this deep, but I am not new to either.
   I searched the archives and only one thing was even close.  Back in Jan
2015 a user complained that the SpamAssassin.txt file was being attached to
all his email.  This happens in my case as well.   Simply removing the call
to attach the file doesn’t fix this issue.   I suspect it really didn’t fix
his either, but he was using a commercial version and ya’ll sent him to the
product support. I am not using anything commercial here.

    Any help here would be appreciated.

Regards
Pete



 

___
NOTE: If there is a disclaimer or other legal boilerplate in the above
message, it is NULL AND VOID.  You may ignore it.

Visit http://www.mimedefang.org and http://www.roaringpenguin.com
MIMEDefang mailing list MIMEDefang@lists.roaringpenguin.com
http://lists.roaringpenguin.com/mailman/listinfo/mimedefang