Sure, np; I added the following rule: -A INPUT -p tcp -m tcp --dport 783 -j ACCEPT
And all is well; P.S. I've been running qmail without a iptables on this box for over a month. Aaron -----Original Message----- From: Eric "Shubes" [mailto:[EMAIL PROTECTED] Sent: Monday, August 28, 2006 11:29 AM To: [email protected] Subject: Re: [qmailtoaster] qmail and iptables Glad you figured it out. I don't understand 'spamassign traffic'. Care to elaborate? Bliss, Aaron wrote: > I figured out what was happening, I had to allow spamassassign traffic > thru. > > Aaron > > -----Original Message----- > From: jeremy [mailto:[EMAIL PROTECTED] > Sent: Sunday, August 27, 2006 12:15 PM > To: [email protected] > Subject: Re: [qmailtoaster] qmail and iptables > > easiest way to tell is what eric said, just do IPTABLES -F > try to connect, if that doesnt work IPTABLES stop > > Jeremy > > ----- Original Message ----- > From: "Eric "Shubes"" <[EMAIL PROTECTED]> > To: <[email protected]> > Sent: Saturday, August 26, 2006 11:20 PM > Subject: Re: [qmailtoaster] qmail and iptables > > >> Good catch, Jeremy. Port 110 is for pop3 though, not incoming (smtp) > mail. >> I use the firewall.sh from the main toaster site. Nick has written > some >> pretty good rules there. I'd try that firewall and see how it works > for >> you. >> >> From what I can see, I still believe your problem isn't with the > firewall. >> jeremy wrote: >>> wheres port 110 in the rules? >>> >>> i dont see it >>> ----- Original Message ----- From: "Eric "Shubes"" <[EMAIL PROTECTED]> >>> To: <[email protected]> >>> Sent: Saturday, August 26, 2006 4:07 PM >>> Subject: Re: [qmailtoaster] qmail and iptables >>> >>> >>>> Aaron Bliss wrote: >>>>> Hi everyone, >>>>> I'm having some trouble with iptables blocking incoming mail; I'm > not >>>>> sure where it's getting blocked, as I'm able to telenet to port 25; > any >>>>> idea what is wrong with my rules? Thanks. >>>>> >>>>> Aaron >>>>> >>>>> *filter >>>>> :INPUT ACCEPT [1217:129358] >>>>> :FORWARD ACCEPT [0:0] >>>>> :OUTPUT ACCEPT [847:246130] >>>>> -A INPUT -p tcp -m tcp --dport 53 -j ACCEPT >>>>> -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT >>>>> -A INPUT -p tcp -m tcp --dport 80 -j ACCEPT >>>>> -A INPUT -p tcp -m tcp --dport 443 -j ACCEPT >>>>> -A INPUT -p tcp -m tcp --dport 25 -j ACCEPT >>>>> -A INPUT -p tcp -m tcp --dport 143 -j ACCEPT >>>>> -A INPUT -j REJECT --reject-with icmp-port-unreachable >>>>> -A OUTPUT -m state --state NEW,RELATED,ESTABLISHED -j ACCEPT >>>>> COMMIT >>>>> >>>> That looks a bit loose to me, but I don't see why smtp wouldn't be >>>> getting through. What makes you think it's the firewall? If you stop > >>>> iptables, does mail come through? >>>> >>>> -- >>>> -Eric 'shubes' >>>> >> >> -- >> -Eric 'shubes' >> -- -Eric 'shubes' --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Confidentiality Notice: The information contained in this electronic message is intended for the exclusive use of the individual or entity named above and may contain privileged or confidential information. If the reader of this message is not the intended recipient or the employee or agent responsible to deliver it to the intended recipient, you are hereby notified that dissemination, distribution or copying of this information is prohibited. If you have received this communication in error, please notify the sender immediately by telephone and destroy the copies you received. --------------------------------------------------------------------- QmailToaster hosted by: VR Hosted <http://www.vr.org> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
