I'm using RHEL4, and I have testet to put the rule before the localhost
accept rule and it works.
But, maybe anyone could answer why this is important to do this ?
I think it is normal that some processes connect to spamassassin via port
783, or is the toaster setup using some pipe mechanism to activate
spamassassin ?
Nick, can you help us with some more info about this issue ??
Thanks,
Christian.
----- Original Message -----
From: "Erik Espinoza" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, January 10, 2006 12:58 PM
Subject: Re: [qmailtoaster] Spamassassin blocking Port 783
If you are using CentOS or Fedora of some sorts then the default rules
wil allow all localhost connections. You can put the block rule before
the '-i lo' rules if you like.
Not entirely sure about the Spamassassin, since I haven't done
anything extra to it on my system.
Erik
On 1/10/06, Christian Schmied <[EMAIL PROTECTED]> wrote:
Hi Erik,
I also block everything from outside to my qmail box. But I understand the
original post from Nick, that the spamassassin process try to communicate
with itself on that port. I also read that if this port is not blocked
(recjected) then spamassassin consume a little bit more time because of
the
communication to localhost port 783.
If this is not the issue, the everything is fine for me, because outside
traffic is blocked by default, except the necessary ports for mail.
But Nick's post says :
> > Spamassassin needs this closed or it chokes communicating
> > on 127.0.0.1:783
So I am a little bit confused....
Thanks,
Christian.
----- Original Message -----
From: "Erik Espinoza" <[EMAIL PROTECTED]>
To: <[email protected]>
Sent: Tuesday, January 10, 2006 11:49 AM
Subject: Re: [qmailtoaster] Spamassassin blocking Port 783
I don't block it, my iptables blocks everything by default. If you
want t block it, you may want to show us what your current firewall
looks like so that we don't screw up your rules.
Thanks,
Erik
On 1/10/06, Christian Schmied <[EMAIL PROTECTED]> wrote:
> Hey guys,
>
> Has nobody an answer to this ???
>
> How do you block this port on your machine ??
>
> Thank you!
> Christian.
>
>
> ----- Original Message -----
> Hi,
>
> I am confused about blocking the port 783 as Nick wrote:
>
> > Second, close firewall port tcp 783
>
> > Spamassassin needs this closed or it chokes communicating
> > on 127.0.0.1:783
>
>
> Please can someone explain me what I should block exactly ??
>
> I have put this line to my iptables script:
>
> -A INPUT -i lo -p tcp -m tcp --dport 783 -j REJECT
>
> Is this OK, I am not sure if this rule blockes connections from
> localhost to localhost (I think this is what Nick means..)
>
> Tnx,
> Christian.
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
