https://bz.apache.org/SpamAssassin/show_bug.cgi?id=7195

Alex <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #2 from Alex <[email protected]> ---

> Splitting this bug into two bugs:
> 
> This bug will deal with this warning:
> 
> >> May 13 23:32:31 mail01 amavis[17306]: (17306-10) _WARN: plugin: eval
> >> failed: Undefined subroutine
> >> &Mail::SpamAssassin::Util::RegistrarBoundaries::trim_domain called at
> >> /usr/share/perl5/vendor_perl/Mail/SpamAssassin/Util.pm line 1236.
> 
> See bug 7196 for the second half.
> 
> From Mark:
> 
> Are you using some third-party SpamAssasin plugin that relies on the
> deprecated subroutine Mail::SpamAssassin::Util::uri_to_domain ?
> 
> Please try the patch below:
> 
> =======
> --- Mail/SpamAssassin/Util.pm~  2015-04-28 21:56:49.000000000 +0200
> +++ Mail/SpamAssassin/Util.pm   2015-05-14 16:26:23.198104251 +0200
> @@ -49,4 +49,5 @@
> 
>  use Mail::SpamAssassin::Logger;
> +use Mail::SpamAssassin::Util::RegistrarBoundaries;  # deprecated
> 
>  BEGIN {
> =======
> 
> 
> KAM: Please let us know if you are using a 3rd party plugin because we'd
> like to make sure the authors noticed the change in 3.4.1.

This patch silences the problem, but it turned out the source of the problem
was with DecodeShortURLs.pm. This patch fixes it.

--- DecodeShortURLs.pm.orig     2015-05-15 11:51:44.688835663 -0400
+++ DecodeShortURLs.pm  2015-05-15 11:39:35.020499066 -0400
@@ -486,7 +486,8 @@
     [Mail::SpamAssassin::Util::uri_list_canonify (undef, $uri)];

   foreach (@{$info->{cleaned}}) {
-    my ($dom, $host) = Mail::SpamAssassin::Util::uri_to_domain($_);
+    my ($dom, $host) = $info->{main}->{registryboundaries}->uri_to_domain($_);

     if ($dom && !$info->{domains}->{$dom}) {
       # 3.4 compatibility as per Marc Martinec

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to