> Rocsca,
>
>> - After I finished my test, I have tried to return the the original
>> configuration. So I have dropped the '$inet_socket_bind = undef'
>> configuration line, and then I have restarted amavisd-new.
>> - Amavisd-new was correctly bound on local local port. But no connection
>> from
Rocsca,
> - After I finished my test, I have tried to return the the original
> configuration. So I have dropped the '$inet_socket_bind = undef'
> configuration line, and then I have restarted amavisd-new.
> - Amavisd-new was correctly bound on local local port. But no connection
> from postifix w
Mark,
On Thu, 17 Jan 2008 21:22:46 +0100, Mark Martinec
<[EMAIL PROTECTED]> wrote:
> Does the message when it reaches amavisd already contain a Received
> header field inserted by your Exim? If so, it can be used in place
> of your X-My-ClientAddr, and provides a standards-based solution.
Yes
>> > > $inet_socket_bind = undef;
>
>> Anyway, if I switch again to the amavisd-new conf without "
>> $inet_socket_bind = undef", amavisd refuse connection from postfix:
>> dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to
>> 127.0.0.1[127.0.0.1]: Connection refused)
>>
>> w
Richard,
> You therefore end up with an initial header being added by Exim which looks
> a bit like this:
> Received: from [190.67.164.205] (helo=estacion03) by
> my-amavis-server.local with smtp (Exim 4.63) (envelope-from
> <[EMAIL PROTECTED]>) id 1JH0Cw-0007yR-1j for
> [EMAIL PROTECTE
Rocsca,
> > > $inet_socket_bind = undef;
> Anyway, if I switch again to the amavisd-new conf without "
> $inet_socket_bind = undef", amavisd refuse connection from postfix:
> dsn=4.4.1, status=deferred (delivery temporarily suspended: connect to
> 127.0.0.1[127.0.0.1]: Connection refused)
>
> why
> > > I have set:
> > > $inet_socket_port = [10024,10027,9998];
> $interface_policy{'9998'} =
> > > 'AM.PDP'; $policy_bank{'AM.PDP'} = {
> > > protocol => 'AM.PDP',
> > > inet_acl => [qw( 127.0.0.1 [::1] 10.166.231.245
> )], }; For
> > > MailZU installation purpouse, i need to a
Mark,
>> After updating perl on my netbsd system, I encountered the same issue
>> with amavis indicating that Compress::Zlib was missing. The error
>> message is somewhat misleading. The module exists, it just fails to load.
>
> Right. I encountered such problems in the past. My simple attem
> > I have set:
> > $inet_socket_port = [10024,10027,9998]; $interface_policy{'9998'} =
> > 'AM.PDP'; $policy_bank{'AM.PDP'} = {
> > protocol => 'AM.PDP',
> > inet_acl => [qw( 127.0.0.1 [::1] 10.166.231.245 )], }; For
> > MailZU installation purpouse, i need to access to
> Amavis
Rocsca,
> I have set:
> $inet_socket_port = [10024,10027,9998];
> $interface_policy{'9998'} = 'AM.PDP';
> $policy_bank{'AM.PDP'} = {
> protocol => 'AM.PDP',
> inet_acl => [qw( 127.0.0.1 [::1] 10.166.231.245 )],
> };
> For MailZU installation purpouse, i need to access to Amavisd-ne
Hi Mark,
That's it. That was my new silly missconfiguration :( . In order for the
ultramonkey to work properly you have to tell amavis to listen to any
interface, cause it sends the data back through the loopback interface.
Thank you.
En/na Mark Martinec ha escrit:
> Jordi,
>
>
>> If from a
I have set:
$inet_socket_port = [10024,10027,9998];
.
.
.
$interface_policy{'9998'} = 'AM.PDP';
$policy_bank{'AM.PDP'} = {
protocol => 'AM.PDP',
inet_acl => [qw( 127.0.0.1 [::1] 10.166.231.245 )],
};
For MailZU installation purpouse, i need to access to Amavisd-new server
from
Jordi,
> If from another machine I perform a ping test, i get response from both
> the "high-available" ip address and the amavis main ip. However, if I
> perform a telnet test to the high-available ip, i get this message:
> telnet: Unable to connect to remote host: Connection refused
> 13:00:09.
Hi.
I would like to know if there is something reported about ultramonkey
and amavisd-new.
The thing is I managed to set up all the options I wanna to include in
my filtering system and now I want to go on to build a high-available
filtering system.
I've been using ultramonkey for quite a long
> > I have a frontend SMTP gateway that serves serveral domains. The
> > frontend spans trhough several server. Every server has the same
> > configuration/hardware. The platform of every server is
> > Postfix+MySQL+Amavisd-new.
> >
> > I would like to enhanche my system implementing a shared qua
> > @lookup_sql_dsn
> > It is worth to use it? What I have to put in amavis SQL database.
>
> If static lookups meet your needs, there is no advantage to
> enable SQL-based lookups.
>
> The main advantage of SQL-based (or LDAP-based) lookups is
> that changes in a database take effect immediate
16 matches
Mail list logo
