Ipcop+copfilter /Spamassasin
Evan
evan_lsa at internode.on.net
Fri Nov 24 14:50:33 CST 2006
David Lloyd wrote:
Hi David,
I am buggered and your translation is correct but I didnt type it correctly.
When it doesn't work it simply stops all mail ie the relayin/proxying
isnt working and I assume it is interpretted as our mail server is down
by our isp server so it holds the emails until we stop the proxy and the
retries start coming through once we forward port 25 again to our
exchange server.
I had a quick look and it's a jumble of perl and bash scripts which are
hard to decypher.
>
> Evan,
>
>> Over the last few weeks we have deployed ipcop and more recently the
>> add on copfilter.
>>
>> Periodically we notice our mail just simply is passed through to our
>> exchange server. blocked by copfilter.
>
> I think this translates as:
>
> "The SMTP conversation periodically gets sent directly to the exchange
> server BUT copfilter intercepts it.".
>
>> I can only assume any attempts by our isp to hand the messsages over
>> is being blocked or rejected. As the process runs as an smtp proxy
>> When it runs it runs ok but the unreliability of it precludes its
>> long term use.
>
> This means:
>
> "When copfilter intercepts it AND works, it's fine. However it doesn't
> always function correctly.".
>
>> I was wondering if anyone has experienced this or better yet can we
>> deploy spamassasin instead on our gateway to do this. Bearing in mind
>> copfilter does use spamassasin but it has been tailored to fit into
>> ipcop configuration.
>
> What I think you're actually saying is:
>
> "How do I run Spamassassin on our gateway?"
>
> It may be late at night and it may be because I've just rewritten
> about 300 lines of spaghetti code into about 60 lines of code. All I
> can say is that embedding PHP into HTML must have seemed like a good
> idea at the time :(
>
> DSL
>
More information about the linuxsa
mailing list