<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Alain Spineux wrote:
<blockquote
cite="mid:71fe4e760801301032m506626d0lb0a090690d0a4326@mail.gmail.com"
type="cite">
<pre wrap="">On Jan 30, 2008 5:54 PM, Tobias Oed <a class="moz-txt-link-rfc2396E" href="mailto:tobias.oed@octant-fr.com"><tobias.oed@octant-fr.com></a> wrote:
</pre>
<blockquote type="cite">
<pre wrap=""> Hello, I have a mynetworks set to 192.168.X.X/24 and would like emails from
clients on that network
to not be scanned for spam.
</pre>
</blockquote>
<pre wrap=""><!---->
Only SPAM or bypass all the amavis filter ?
</pre>
</blockquote>
Only spam, I still would like to bounce viruses.<br>
<blockquote
cite="mid:71fe4e760801301032m506626d0lb0a090690d0a4326@mail.gmail.com"
type="cite">
<pre wrap="">Maybe you could share with us why you want to do that ?
</pre>
</blockquote>
I can't configure authentication on the clients the day the migration
is done. There are too many of them, and I can't have the users mail
disapearing as spam.<br>
Also, I have several servers that send mail using the mail/php/whatnot
command in various obscure scripts. Some of them will be flagged as
spam and I don't want to lose that mail. <br>
<blockquote
cite="mid:71fe4e760801301032m506626d0lb0a090690d0a4326@mail.gmail.com"
type="cite">
<blockquote type="cite">
<pre wrap="">So I copied the MYUSERS policy of
amavis.conf.template to MYNETS
and now all spam goes thourgh.
This is because kolabfilter acts before amavis and the IP address of the
client gets lost in the
comunication between kolabfilter and postfix (missing XFORWARD ?).
So I was wondering what one can do about that and also how the MYUSERS part
of the amavis
config is supposed to work.
This is with kolab-2.1
</pre>
</blockquote>
<pre wrap=""><!---->
If you want to bypass amavis you could try to add this line to
/kolab/etc/postfix/master.cf (do it in the template :-)
192.168.X.X:11025 inet n - n - -
smtpd -o content_filter=
!!! there is nothing after the =
and setup your client to use 192.168.X.X:11025 instead of just 192.168.X.X
</pre>
</blockquote>
That could be a temporary workaround, but I'd still have to go around
and change the config on each client... That's why I'm looking for a
solution on the server side. <br>
I don't think the question is entierly out of place since the postfix
master file contains the xforward that are necessary for amavis, and
kolabfilter prints the clients ip correctly, while kolabmailboxfilter
prints 127.0.0.1 instead. I think the ip gets lost when kolabfilter
reinjects the mail back into postfix.<br>
Thanks, cheers<br>
Tobias<br>
<br>
<div class="moz-signature">
<div id="sig"
style="border-top: 1px dotted rgb(153, 153, 153); border-bottom: 1px dotted rgb(153, 153, 153); margin: 6px 0pt; padding: 8px; line-height: 13px; font-family: 'Lucida Grande',Verdana,Arial,Sans-Serif; font-size: 11px; color: rgb(51, 153, 153);"><strong
style="color: rgb(51, 153, 153);">Tobias Oed</strong> - <a
href="http://www.octant-fr.com" title="visit octant-fr.com"
style="border-bottom: 1px dotted rgb(153, 153, 153); color: rgb(51, 153, 153); text-decoration: none;">Octant
Informatique</a><br>
contact | <a href="mailto:tobias.oed@octant-fr.com"
style="border-bottom: 1px dotted rgb(153, 153, 153); color: rgb(51, 153, 153); text-decoration: none;">tobias.oed@octant-fr.com</a>
- 04 76 50 82 38
</div>
<img src="http://www.octant-fr.com/signatures/tobias.oed.jpg"
alt="image" moz-do-not-send="true">
</div>
</body>
</html>