FYI, for a backwards and forwards compatibility workaround until a fix is distributed, I was able to utilize the Amavis::Custom functionality to "patch" the core code. Put the following code at the end of a config file that amavisd-new loads, or otherwise load a file with the end code in it. For example:
50-user:
use strict;
#
# Place your configuration directives here. They will override those in
# earlier files.
#
# See /usr/share/doc/amavisd-new/ for documentation and examples of
# the directives you can use in this file
#
# Your configuration stuff here
#------------ Do not modify anything below this line -------------
1; # ensure a defined return
# Make sure the originating flag is up-to-date.
package Amavis::Custom;
use strict;
BEGIN {
import Amavis::Conf qw(c);
}
sub new {
my($class,$conn,$msginfo) = @_;
$msginfo->originating(c('originating'));
}
FYI, for a backwards and forwards compatibility workaround until a fix is distributed, I was able to utilize the Amavis::Custom functionality to "patch" the core code. Put the following code at the end of a config file that amavisd-new loads, or otherwise load a file with the end code in it. For example:
50-user:
use strict;
# doc/amavisd- new/ for documentation and examples of
# Place your configuration directives here. They will override those in
# earlier files.
#
# See /usr/share/
# the directives you can use in this file
#
# Your configuration stuff here
#------------ Do not modify anything below this line -------------
1; # ensure a defined return
# Make sure the originating flag is up-to-date.
package Amavis::Custom;
use strict;
BEGIN {
import Amavis::Conf qw(c);
}
sub new { $class, $conn,$ msginfo) = @_; >originating( c('originating' ));
my(
$msginfo-
}
1;