On Sat, Jul 28, 2007 at 01:04:54 +0200, Mark Martinec wrote:
> Since the problem is in Socket::SOMAXCONN, this is where it should
> be fixed, probably not in Net::Server. It is unlikely the Perl
> core module will be fixed, at least not for the current version.
> But certainly, if you'd be willing
On 7/27/07, David Schweikert <[EMAIL PROTECTED]> wrote:
...
> 1. amavisd-milter needs to be patched to work well with Postfix, because
>Postfix does give information about the queue-number only after the
>RCPT-TO-phase. I have attached a patch for that.
I will add it to the next release.
David Schweikert wrote:
> On Fri, Jul 27, 2007 at 17:52:58 +0200, Mark Martinec wrote:
> > >The problem is that even though I properly limited the number of
> > >amavisd connections in amavisd-milter, amavisd does have a listen
> > >backlog (queuing of connecting clients) of maximum 5
David,
> Maybe Net::Server should be fixed instead? It probably would be even
> better to fix Socket::SOMAXCONN...
Since the problem is in Socket::SOMAXCONN, this is where it should
be fixed, probably not in Net::Server. It is unlikely the Perl
core module will be fixed, at least not for the curr
On Fri, Jul 27, 2007 at 17:52:58 +0200, Mark Martinec wrote:
> >The problem is that even though I properly limited the number of
> >amavisd connections in amavisd-milter, amavisd does have a listen
> >backlog (queuing of connecting clients) of maximum 5 clients. That
> >is, if I hav
David,
> 2. amavisd-milter requires to use Unix domain sockets to communicate
>with amavisd. This is not really a problem except that when I was
>stress-testing my test setup with 10 backend amavisd processes, I
>noticed that, once in a while, amavisd-milter was getting a
>"Connect
The mailing-list doesn't seem to like attachments so here is the patch
for amavisd-milter inline:
--- amavisd-milter/mlfi.c.orig 2007-07-27 14:02:47.068396000 +0200
+++ amavisd-milter/mlfi.c 2007-07-27 14:02:53.058402000 +0200
@@ -929,6 +929,18 @@
return SMFIS_TEMPFAIL;
}
+
Hi,
I am using Postfix and am experimenting with the inline rejection of
virus mails using amavisd-new combined with amavisd-milter.
The reason for using the milter interface instead of smtpd_proxy_filter
is that if you do inline rejection with smtpd_proxy_filter, you need to
have as many amavisd
Bill wrote:
>> The FILTER action only replaces the current content_filter setting
>> and does not stop processing restrictions. Multiple FILTER
>> actions can all stick their value into a content_filter
>> one after another, whatever remains there when some restriction
>> finally does terminate pr
Mark Martinec wrote the following on 5/10/2007 4:27 PM -0800:
> On Friday May 11 2007 00:51:14 Bill Landry wrote:
>
>> So explain a situation where the first filter would *not* apply. As
>> written, it applies to everything and anything after
>> "check_client_access pcre:/etc/postfix/filter_out
Bill Landry wrote:
> Jeremy Laidman wrote the following on 5/10/2007 3:40 PM -0800:
>
>> Bill Landry wrote:
>>
>>
>>
smtpd_recipient_restrictions =
...
check_client_access pcre:/etc/postfix/filter_outbound
permit_mynetworks
per
On Friday May 11 2007 00:51:14 Bill Landry wrote:
> So explain a situation where the first filter would *not* apply. As
> written, it applies to everything and anything after
> "check_client_access pcre:/etc/postfix/filter_outbound" is useless, as
> everything will be sent to the first content_fil
Jeremy Laidman wrote the following on 5/10/2007 3:40 PM -0800:
> Bill Landry wrote:
>
>
>>> smtpd_recipient_restrictions =
>>> ...
>>> check_client_access pcre:/etc/postfix/filter_outbound
>>> permit_mynetworks
>>> permit_sasl_authenticated
>>> check_c
Bill Landry wrote:
>> smtpd_recipient_restrictions =
>> ...
>> check_client_access pcre:/etc/postfix/filter_outbound
>> permit_mynetworks
>> permit_sasl_authenticated
>> check_client_access pcre:/etc/postfix/filter_inbound
>> reject_unauth_destin
Gary V wrote the following on 5/10/2007 2:31 PM -0800:
> Bill wrote:
>
>
>> Gary V wrote the following on 5/10/2007 2:21 PM -0800:
>>
>>> Bill wrote:
>>>
>>>
>>>
mouss wrote the following on 5/10/2007 1:26 PM -0800:
> it is recommended to pass outb
Bill wrote:
> Gary V wrote the following on 5/10/2007 2:21 PM -0800:
>> Bill wrote:
>>
>>
>>> mouss wrote the following on 5/10/2007 1:26 PM -0800:
>>>
it is recommended to pass outbound mail through a virus checker. one way
to do this is to tell amavisd-new to listen on two por
Gary V wrote the following on 5/10/2007 2:21 PM -0800:
> Bill wrote:
>
>
>> mouss wrote the following on 5/10/2007 1:26 PM -0800:
>>
>>> it is recommended to pass outbound mail through a virus checker. one way
>>> to do this is to tell amavisd-new to listen on two ports (10024 and
>>> 105
Bill wrote:
> mouss wrote the following on 5/10/2007 1:26 PM -0800:
>> it is recommended to pass outbound mail through a virus checker. one way
>> to do this is to tell amavisd-new to listen on two ports (10024 and
>> 10586 for instance) and use
>> ... FILTER amavis:[127.0.0.1]:10586
>> for
mouss wrote the following on 5/10/2007 1:26 PM -0800:
> it is recommended to pass outbound mail through a virus checker. one way
> to do this is to tell amavisd-new to listen on two ports (10024 and
> 10586 for instance) and use
> ... FILTER amavis:[127.0.0.1]:10586
> for outbound mail (myne
Martin Schiøtz wrote:
> On 5/10/07, Jeremy Laidman <[EMAIL PROTECTED]> wrote:
>
>> Martin Schiøtz wrote:
>>
>>
>>> Is it possible with postfix only to send incoming mails to amavisd-new
>>> and outgoing mails without configuring two ip-addresses on the server?
>>>
>> I think you're a
On 5/10/07, Jeremy Laidman <[EMAIL PROTECTED]> wrote:
> Martin Schiøtz wrote:
>
> > Is it possible with postfix only to send incoming mails to amavisd-new
> > and outgoing mails without configuring two ip-addresses on the server?
>
> I think you're asking if outbound mails can bypass amavis.
>
> Ye
Martin Schiøtz wrote:
> Is it possible with postfix only to send incoming mails to amavisd-new
> and outgoing mails without configuring two ip-addresses on the server?
I think you're asking if outbound mails can bypass amavis.
Yes you can. Assuming second postfix is listening on localhost port
Hi
Is it possible with postfix only to send incoming mails to amavisd-new
and outgoing mails without configuring two ip-addresses on the server?
If this is possible can I then use the
'lmtp_send_xforward_command=yes' functionality or similar for outgoing
mails (pen pals functionality with amavisd
hello list, I am in some problems with amavisd-new I wait they can
help me, we want to block some users that don't send extensions exe,
pif, bat , and can the rest of the domain send what wants, by mail
this is possible with amavisd-new?
I am using suse 10.0 with postfix+amavisd-new+clamav
right
Carl wrote:
>> @bypass_spam_checks_maps = (1); # uncomment to DISABLE anti-spam code
> OK, so that doesn't influence amavis' internal spamchecks, and is only
> related to SA?
Amavisd-new has no internal "spam" checks so this will disable "spam"
checking. It will still allow the other three typ
On 1/16/07, Gary V <[EMAIL PROTECTED]> wrote:
> > - What to comment out in amavisd.conf in order to entirely disable
> > anything related to spamassassin ? (oh how I hate typing the word, even)
>
> I don't use CentOS so I can't precisely answer most of your questions
> but this one is your main con
- wrote:
> Hi,
> I've been reading and searching everywhere, but because of the hard
> search option "without spamassassin" it is almost impossible
> to find useful answers. I found some on the web, but none were
> complete or clear. So, I'm asking again, and hope for an answer
> that actually wo
Hi,
I've been reading and searching everywhere, but because of the hard
search option "without spamassassin" it is almost impossible
to find useful answers. I found some on the web, but none were
complete or clear. So, I'm asking again, and hope for an answer
that actually works and makes sense to
Michael wrote:
> Hello Noel,
> But i have another problem - i hoped to solve it with the spamc-problem. ;-)
> My SA will not be started / used from amavis.
> Anybody knows or see any problem in my configuration?
> Michael
One possibility is you have disabled spam scanning. This should be com
At 04:25 PM 8/9/2006, Michael Post wrote:
>But i have another problem - i hoped to solve it with the
>spamc-problem. ;-)
>
>My SA will not be started / used from amavis.
>Anybody knows or see any problem in my configuration?
If amavisd-new doesn't seem to be using SpamAssassin, first
look at the
Hello,
Michael Post schrieb:
> Hello Jim,
> oder besser Hallo ;-)
>
> Jim Knuth schrieb:
>
>> why?
>>
>>
> because the performance will be better for mailserver with a high flow.
>
Ok. Sorry. I do not have read the paragraph too detailed with the
information.
It is equal if you proceed
Hello Noel,
Noel Jones schrieb:
> At 03:03 PM 8/9/2006, Michael Post wrote:
>
>> Ok. Amavisd-new should work perfect with spamassassin by
>> calling the
>> process for every email but i want to create a system
>> which talks with
>> "spamd" over "spamc".
>> And here you can find my little pro
Hello Jim,
oder besser Hallo ;-)
Jim Knuth schrieb:
> why?
>
because the performance will be better for mailserver with a high flow.
> you must set in brackets => [127.0.0.1]
>
Where is the difference? Currently it works fine.
Later comment: It works although fine with brakes.
Michael
--
At 03:03 PM 8/9/2006, Michael Post wrote:
>Ok. Amavisd-new should work perfect with spamassassin by
>calling the
>process for every email but i want to create a system
>which talks with
>"spamd" over "spamc".
>And here you can find my little problem.
>
>How can i say amavisd-new that he should ta
Heute (09.08.2006/22:03 Uhr) schrieb Michael Post,
> Hello group,
> i am new on this mailinglist.
> I have installed and configured a postfix + mysql + tls + amavisd-new +
> cyrus system and it works fine.
> Now i want add the spamassassin-part for this system.
> Ok. Amavisd-new should work per
Hello group,
i am new on this mailinglist.
I have installed and configured a postfix + mysql + tls + amavisd-new +
cyrus system and it works fine.
Now i want add the spamassassin-part for this system.
Ok. Amavisd-new should work perfect with spamassassin by calling the
process for every email bu
Hi!
I know myself that multidrop is quite bad ..
but skipping amavis everything works fine ... using amavis ... the header is
malformed ... although I can't reconstruct the error ...
Philipp
---
This SF.net email is sponsored by: Splunk Inc.
Philipp,
> I know myself that multidrop is quite bad ..
> but skipping amavis everything works fine ... using amavis ... the header
> is malformed ... although I can't reconstruct the error ...
When you collect the evidence, we will be able to examine it.
Make sure to collect the full non-mangled
Hi!
I know myself that multidrop is quite bad ..
but skipping amavis everything works fine ... using amavis ... the header is
malformed ... although I can't reconstruct the error ...
Philipp
---
This SF.net email is sponsored by: Splunk Inc.
Hi!
We are using amavisd-new-20030616-p10 (Debian) to scan our emails.
Now we got a new user having a multidrop-mailbox called [EMAIL PROTECTED]
collecting all the mails vor domain.net. These mails (from [EMAIL PROTECTED])
are
fetched by fetchmail and then delivered locally to an MS Exchange Serv
Philipp,
> Now we got a new user having a multidrop-mailbox called [EMAIL PROTECTED]
> collecting all the mails vor domain.net. These mails (from [EMAIL PROTECTED])
> are fetched by fetchmail and then delivered locally to an MS Exchange
> Server
Using multidrop mailboxes is asking for trouble. Ex
Hi!
We are using amavisd-new-20030616-p10 (Debian) to scan our emails.
Now we got a new user having a multidrop-mailbox called [EMAIL PROTECTED]
collecting all the mails vor domain.net. These mails (from [EMAIL PROTECTED])
are
fetched by fetchmail and then delivered locally to an MS Exchange Serv
Gary wrote:
> Jiří wrote:
>> <[EMAIL PROTECTED]>: Command died with status 255: "/usr/sbin/amavisd-new".
>> Command output: Subroutine AUTOLOAD redefined at /etc/perl/IO/Zlib.pm line
>> 84. Subroutine isaFilehandle redefined at /etc/perl/IO/Zlib.pm line 99.
>> Subroutine isaFilename redefined at
Jiří wrote:
> Hello,
> I´ve following problem with amavisd-new. I´m trying to use it on debian
> (sarge)
> machine (perl 5.8.7) with postfix. But when I try to run amavisd-new debug,
> i receive this:
> gate:/home/ogeen# amavisd-new debug
> Subroutine AUTOLOAD redefined at /etc/perl/IO/Zlib.pm li
Ji?í ?ervenka <[EMAIL PROTECTED]> wrote:
| Hello,
| I?ve following problem with amavisd-new. I?m trying to use it on debian
(sarge)
| machine (perl 5.8.7) with postfix. But when I try to run amavisd-new debug,
| i receive this:
| gate:/home/ogeen# amavisd-new debug
| Subroutine AUTOLOAD redefined
Hello,
I´ve following problem with amavisd-new. I´m trying to use it on debian
(sarge)
machine (perl 5.8.7) with postfix. But when I try to run amavisd-new debug,
i receive this:
gate:/home/ogeen# amavisd-new debug
Subroutine AUTOLOAD redefined at /etc/perl/IO/Zlib.pm line 84.
Subroutine isaFile
Hi List,
I am trying to find a solution to probably a database Join issue.
in postfix I vrfy an users email trough Ldap, if (OK) i add the user to
the local mysql table so i do not have to do any LDap queries in the
"cache ldap" timeframe, so far so good .
now the point is I also want users in t
47 matches
Mail list logo
