RE: Email issues, relay failure, perhaps Jails is causing it.

2012-02-27 Thread Bender, Chris
Hello

Can anybody assist me with pfctl on freebsd?
I have pfctl running as adaptive. It is blocking some smtp mail. 
I am uncertain about flushing the states or machining some of the 
TIMEWAITING constraints go away. Which is really blocking my email.

Can anyone assist?

Thanks

-Original Message-
From: Bernt Hansson [mailto:b...@bananmonarki.se] 
Sent: Sunday, February 26, 2012 2:20 AM
To: Bender, Chris
Cc: freebsd-questions@freebsd.org
Subject: Re: Email issues, relay failure, perhaps Jails is causing it.

2012-02-26 00:54, Bender, Chris skrev:
 Hi Brent

 Yes the system we are calling X, is jailed by another system.

 Here is the jailer system:

 zs1#  netstat -aptcp | grep smtp
 tcp4   0  0 tools2.smtp10.156.31.20.45081
 SYN_RCVD
 tcp4   0  0 tools2.smtp*.*
LISTEN
 tcp4   0  0 rt3.smtp   *.*
LISTEN
 tcp4   0  0 npims.smtp *.*
LISTEN
 tcp4   0  0 wiki.smtp  *.*
LISTEN
 tcp4   0  0 localhost.smtp *.*
LISTEN

Here is about jails;

http://www.uk.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html

Have you tried to telnet into the other jailed hostnames and
ip-addresses, like telnet rt3.* 25

What does it say? Can you connect?

There seems to be either a jail problem or a routing problem

You can look at your routing table with netstat -r
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


RE: Email issues, relay failure, perhaps Jails is causing it.

2012-02-27 Thread Bender, Chris
Does anybody have an idea on how to clear the bruteforCE TABLE ON PFCTL
?
An adaptive fw or pftcl device is blocking some of my email?

Thanks

-Original Message-
From: Bernt Hansson [mailto:b...@bananmonarki.se] 
Sent: Sunday, February 26, 2012 2:20 AM
To: Bender, Chris
Cc: freebsd-questions@freebsd.org
Subject: Re: Email issues, relay failure, perhaps Jails is causing it.

2012-02-26 00:54, Bender, Chris skrev:
 Hi Brent

 Yes the system we are calling X, is jailed by another system.

 Here is the jailer system:

 zs1#  netstat -aptcp | grep smtp
 tcp4   0  0 tools2.smtp10.156.31.20.45081
 SYN_RCVD
 tcp4   0  0 tools2.smtp*.*
LISTEN
 tcp4   0  0 rt3.smtp   *.*
LISTEN
 tcp4   0  0 npims.smtp *.*
LISTEN
 tcp4   0  0 wiki.smtp  *.*
LISTEN
 tcp4   0  0 localhost.smtp *.*
LISTEN

Here is about jails;

http://www.uk.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html

Have you tried to telnet into the other jailed hostnames and
ip-addresses, like telnet rt3.* 25

What does it say? Can you connect?

There seems to be either a jail problem or a routing problem

You can look at your routing table with netstat -r
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Email issues, relay failure, perhaps Jails is causing it.

2012-02-26 Thread Daniel Staal
--As of February 26, 2012 8:20:14 AM +0100, Bernt Hansson is alleged to 
have said:



http://www.uk.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html

Have you tried to telnet into the other jailed hostnames and
ip-addresses, like telnet rt3.* 25

What does it say? Can you connect?

There seems to be either a jail problem or a routing problem

You can look at your routing table with netstat -r


--As for the rest, it is mine.

This is my strong suspicion as well.

To separate out what the problem is:

'su' to root in the jailed system.  Shut down postfix.  (`postfix stop`, or 
`/etc/rc.d/postfix stop`)  Then run `nc -l 25`.  This will echo anything 
that comes in on port 25 direct to your terminal.  Then try telneting to 
it.  If it works, the problem is postfix.  If it doesn't, restart postfix 
and ignore it: It's not the problem.


Daniel T. Staal

---
This email copyright the author.  Unless otherwise noted, you
are expressly allowed to retransmit, quote, or otherwise use
the contents for non-commercial purposes.  This copyright will
expire 5 years after the author's death, or in 30 years,
whichever is longer, unless such a period is in excess of
local copyright law.
---
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


RE: Email issues, relay failure, perhaps Jails is causing it.

2012-02-25 Thread Bender, Chris
Hi Brent

Yes the system we are calling X, is jailed by another system. 

Here is the jailer system:

zs1#  netstat -aptcp | grep smtp
tcp4   0  0 tools2.smtp10.156.31.20.45081
SYN_RCVD
tcp4   0  0 tools2.smtp*.*LISTEN
tcp4   0  0 rt3.smtp   *.*LISTEN
tcp4   0  0 npims.smtp *.*LISTEN
tcp4   0  0 wiki.smtp  *.*LISTEN
tcp4   0  0 localhost.smtp *.*LISTEN

I see smtp running on several systems it has jailed including system X.
I see above a smtp conversation between system X and 10.156.31.20.
But that is never delivered from what I have seen. I am not sure about
the queues
Or how to see in postfix what exactly is happening?

I think a lot of this stopped working after we rebooted the jailer
system. Jails really should have no affect on
This it is a virtual machine essentially, at least that is my thoughts.

What happen to your thought that snmp needs to run as a non mailer
system?

Thanks

regards

-Original Message-
From: Bernt Hansson [mailto:b...@bananmonarki.se] 
Sent: Saturday, February 25, 2012 6:11 PM
To: Bender, Chris
Cc: freebsd-questions@freebsd.org; Jon Radel
Subject: Re: Email issues, relay failure

2012-02-25 23:29, Bender, Chris skrev:
 Hi Brent,
 Thanks for that, I am still digesting it.

 tools2# uname -a
 FreeBSD tools2 8.2-RELEASE-p2 FreeBSD 8.2-RELEASE-p2 #

 So I put a 0 in the first two octets of the ip address below, but  
 that IP address is A.
 I am not sure what that means. I was horsing around and tried to start

 sendmail On X then I tried to send an email from A. I have no  idea 
 what all that means.

 Here is netstat results:
 netstat: kvm not available: /dev/mem: No such file or directory
 tcp4   0  0 tools2.smtp0.0.81.10.33679
SYN_RCVD
 tcp4   0  0 tools2.smtp*.*
LISTEN

Ok. I'm stabbing in the dark here, but didn't you say that X was a jail
system?

Is every postfix process in a jail?

I have never used a jailed system. So my WILD guess it's a something
with jail, or jail setup.


 What is non $mail_owner privileges or how to determine that?

 tools2# postconf -d | grep mail_version mail_version = 2.7.0 
 milter_macro_v = $mail_name $mail_version

 I am still not sure about the non mail owner issue yet, but I would 
 think because this has run in the past that it wouldn't have changed.
 And how do I run smtp as a non mail user when I am root?

 Hopfully we are getting somewhere.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org


Re: Email issues, relay failure, perhaps Jails is causing it.

2012-02-25 Thread Bernt Hansson

2012-02-26 00:54, Bender, Chris skrev:

Hi Brent

Yes the system we are calling X, is jailed by another system.

Here is the jailer system:

zs1#  netstat -aptcp | grep smtp
tcp4   0  0 tools2.smtp10.156.31.20.45081
SYN_RCVD
tcp4   0  0 tools2.smtp*.*LISTEN
tcp4   0  0 rt3.smtp   *.*LISTEN
tcp4   0  0 npims.smtp *.*LISTEN
tcp4   0  0 wiki.smtp  *.*LISTEN
tcp4   0  0 localhost.smtp *.*LISTEN


Here is about jails;

http://www.uk.freebsd.org/doc/en_US.ISO8859-1/books/handbook/jails.html

Have you tried to telnet into the other jailed hostnames and 
ip-addresses, like telnet rt3.* 25


What does it say? Can you connect?

There seems to be either a jail problem or a routing problem

You can look at your routing table with netstat -r
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org