Unzustellbar: [SPAM] - Re: Why does this connection stop being tr acked? - Sending mail server found on relays.ordb.org (fwd)

["R. DuFresne" <dufresne@sysinfo.com>]

[-- Attachment #1: Type: TEXT/PLAIN, Size: 1555 bytes --]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



will the folks responsible for maintaining the list please remove these 
clueless ones from the list;


http://ordb.org/lookup/?host=sysinfo.com

Lookup
This host is not listed in ORDB as an open mail relay

Main database status for sysinfo.com (70.61.80.19)
Look up this host in non-ORDB RBL's (May take a while to load)
The host sysinfo.com is not in the main database


- ---------- Forwarded message ----------
From: Systemadministrator <postmaster@echtzeit.com>
Subject: Unzustellbar: [SPAM] - Re: Why does this connection stop being tr
     acked? - Sending mail server found on relays.ordb.org
Date: Wed, 15 Jun 2005 18:06:14 +0200
To: dufresne@sysinfo.com

Your message

   To:      Andy Smith
   Cc:      netfilter@lists.netfilter.org; Jozsef Kadlecsik
   Subject: [SPAM] - Re: Why does this connection stop being tracked? -
Sending mail server found on relays.ordb.org
   Sent:    Wed, 15 Jun 2005 18:07:52 +0200

did not reach the following recipient(s):

phergenhahn@echtzeit.de on Wed, 15 Jun 2005 18:06:13 +0200
     Der Name des Empfängers wurde nicht erkannt.
 	Die MTS-ID der ursprünglichen Nachricht ist: c=de;a= ;p=echtzeit
gmbh ? ;l=EZMXS0506151606M1PANQGT
     MSEXCH:IMS:Echtzeit GmbH & Co. KG:ECHTZEIT:EZMXS 0 (000C05A6)
Unbekannter Empfänger


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCsGQsst+vzJSwZikRAt1LAJ9xL9l5z9fKn8BZzQimgpQvYqJPrgCfbRVe
qncoDiq+Lfi4bv2DkQkG2pA=
=L99R
-----END PGP SIGNATURE-----

[-- Attachment #2: Type: MESSAGE/RFC822, Size: 3409 bytes --]

Message-ID: <Pine.LNX.4.60.0506151154340.25078@darkstar.sysinfo.com>
From: "R. DuFresne" <dufresne@sysinfo.com>
To: Andy Smith <andy@strugglers.net>
Cc: netfilter@lists.netfilter.org, Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Subject: [SPAM] - Re: Why does this connection stop being tracked? - Sendi
	ng mail server found on relays.ordb.org
Date: Wed, 15 Jun 2005 18:07:52 +0200
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
X-MS-Embedded-Report: 
List-Help: <mailto:netfilter-request@lists.netfilter.org?subject=help>
List-Subscribe: <https://lists.netfilter.org/mailman/listinfo/netfilter>,
	<mailto:netfilter-request@lists.netfilter.org?subject=subscribe>
List-Unsubscribe: <https://lists.netfilter.org/mailman/listinfo/netfilter>,
	<mailto:netfilter-request@lists.netfilter.org?subject=unsubscribe>
Content-Type: text/plain;
	charset="iso-8859-1"

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


 	[SNIP]

>>
>> You have two choices: either disable TCP SACK support on all your
>> real/virtual machines behind your firewall, or upgrade the kernel on the
>> firewall.
>
> Do you have any instructions or a pointer to documentation onhow to
> temporarily disable SACK?  If it was a /proc setting that would be
> ideal; I don't really want to have to recompile kernels though.
>

why?  you are certainly missing out on how to fix and patch a systems when 
bugs in the kernel affect it, to the ability to add features that your 
dist maintainer has not enabled by default, or to change params in the 
kernel such as moving away or to kernel modules as opposed to stack 
functionality mapping.  Not to mention the abilities to streamline the 
kernel to fit your requirements and remove all the xtra trash that gets 
loaded in to make a kernel fit all purposes/needs/enduser-requirements.

basically, you are defeating one of the finer points in the linux realm <as 
well as the BSD's net, open, free>  you are avoiding taking actually 
control of what you are playing with <smile>.  Granted one does not do 
this sort of thing in a prod env on the fly, one tests such things on a 
dev server or desktop emulating what might be in prod. but, it's not all 
that tough to master, and certainly will likely be required at one time or 
another to get things working that were not originally provided, move to a 
newer cleaner kernel, or even to fix problems encountered over the 
stresses of time and all that.  The recipe for doing such is not all that 
complex, and if one backsup the old kernel and properly runs lilo to 
include it in the potential boot process, not all that damaging should on 
finger-fart and make a bed new kernel on first draft. but all admins in 
the free *nix-like realm should learn the particulars of rebuilding 
kernels, it will  at one time or another save their asses.

No salt for the avoiders.

Thanks,

Ron DuFresne
- -- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
         admin & senior security consultant:  sysinfo.com
                         http://sysinfo.com
Key fingerprint = 9401 4B13 B918 164C 647A  E838 B2DF AFCC 94B0 6629

...We waste time looking for the perfect lover
instead of creating the perfect love.

                 -Tom Robbins <Still Life With Woodpecker>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCsFJdst+vzJSwZikRAiaQAKCWHlgggJUxBXu9/CeR//pLYbzHGACfRVev
kG/17gNRcUin+Dk63ai8gCA=
=2VQV
-----END PGP SIGNATURE-----

From: "R. DuFresne" <dufresne@sysinfo.com>
To: Andy Smith <andy@strugglers.net>
Cc: netfilter@lists.netfilter.org, Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>
Subject: [SPAM] - Re: Why does this connection stop being tracked? - Sendi ng mail server found on relays.ordb.org
Date: Wed, 15 Jun 2005 18:07:52 +0200
Message-ID: <Pine.LNX.4.60.0506151154340.25078@darkstar.sysinfo.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


 	[SNIP]

>>
>> You have two choices: either disable TCP SACK support on all your
>> real/virtual machines behind your firewall, or upgrade the kernel on the
>> firewall.
>
> Do you have any instructions or a pointer to documentation onhow to
> temporarily disable SACK?  If it was a /proc setting that would be
> ideal; I don't really want to have to recompile kernels though.
>

why?  you are certainly missing out on how to fix and patch a systems when 
bugs in the kernel affect it, to the ability to add features that your 
dist maintainer has not enabled by default, or to change params in the 
kernel such as moving away or to kernel modules as opposed to stack 
functionality mapping.  Not to mention the abilities to streamline the 
kernel to fit your requirements and remove all the xtra trash that gets 
loaded in to make a kernel fit all purposes/needs/enduser-requirements.

basically, you are defeating one of the finer points in the linux realm <as 
well as the BSD's net, open, free>  you are avoiding taking actually 
control of what you are playing with <smile>.  Granted one does not do 
this sort of thing in a prod env on the fly, one tests such things on a 
dev server or desktop emulating what might be in prod. but, it's not all 
that tough to master, and certainly will likely be required at one time or 
another to get things working that were not originally provided, move to a 
newer cleaner kernel, or even to fix problems encountered over the 
stresses of time and all that.  The recipe for doing such is not all that 
complex, and if one backsup the old kernel and properly runs lilo to 
include it in the potential boot process, not all that damaging should on 
finger-fart and make a bed new kernel on first draft. but all admins in 
the free *nix-like realm should learn the particulars of rebuilding 
kernels, it will  at one time or another save their asses.

No salt for the avoiders.

Thanks,

Ron DuFresne
- -- 
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
         admin & senior security consultant:  sysinfo.com
                         http://sysinfo.com
Key fingerprint = 9401 4B13 B918 164C 647A  E838 B2DF AFCC 94B0 6629

...We waste time looking for the perfect lover
instead of creating the perfect love.

                 -Tom Robbins <Still Life With Woodpecker>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFCsFJdst+vzJSwZikRAiaQAKCWHlgggJUxBXu9/CeR//pLYbzHGACfRVev
kG/17gNRcUin+Dk63ai8gCA=
=2VQV
-----END PGP SIGNATURE-----