Date: Sat, 21 Aug 2010 17:35:57 +0200 From: Svein Skogen <svein@stillbilde.net> To: freebsd-questions@freebsd.org Subject: Parklogic making a mess Message-ID: <4C6FF25D.1090304@stillbilde.net>
next in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enigF5B57177268512A1BEB7CCBD Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Anybody else seem to get these header-falsified messages lately: ---- Return-Path: <anonymous@dusk.parklogic.com> X-Original-To: svein-listmail@stillbilde.net Delivered-To: svein-listmail@stillbilde.net Received: from dusk.parklogic.com (allmail.0b2.net [64.38.11.26]) by mail.stillbilde.net (Familien Skogens mail) with SMTP id B9E8E26 for <svein-listmail@stillbilde.net>; Sat, 21 Aug 2010 17:17:33 +0200 (CE= ST) Received: (qmail 26077 invoked by uid 511); 21 Aug 2010 14:56:12 -0000 Message-ID: <20100821145612.26076.qmail@dusk.parklogic.com> From: freebsd-questions@freebsd.org To: "Svein Skogen" <svein-listmail@stillbilde.net>(Listmail account) Subject: Re: FreeBSD, GPGPU and OpenCL/CUDA In-Reply-To: 4C6F84DD.3040007@stillbilde.net References: 4C666786.6000205@mail.zedat.fu-berlin.de 20100816141324.7de6d7b4@ukr.net 20100816134713.66411ai1w435q5wh@webmail.xroff.net 201008161618.35076.pieter@degoeje.nl 20100816173333.4a1bba57@ukr.net 20100816145001.GA90619@mech-cluster241.men.bris.ac.uk 20100818120455.10870.qmail@dusk.parklogic.com 4C6C085A.2010009@pathscale.com 4C6F84DD.3040007@stillbilde.net Date: Sun, 22 Aug 2010 00:56:12 +1000 MIME-Version: 1.0 Content-Type: text/html; boundary=3D"1282402572.8bad8C70.26046"; charset=3D"us-ascii" MIME-Version: 1.0 <html><body> <p>Dear Sir/Madam,<br /><br /> Your email was unable reach the intended person that you were sending it to.<br /> For more information on our business please click on the following link:<br /> <a href=3D"http://www.downwind.com.au/avdir/rd.php?id=3D7564">Click here = for our website</a><br /> We look forward to your continued business in the future.<br /><br /> Regards,<br /> Webmaster<br /> </p> </body></html> ---- I suspect the correct way of handling this would be to contact "Layered Technologies Ltd" and tell them that 64.38.0.0/18 will be null-routed until they have fixed their broken mailserver (if it's falsifying headers, it IS broken), wouldn't it? //Svein --=20 --------+-------------------+------------------------------- /"\ |Svein Skogen | svein@d80.iso100.no \ / |Solberg =D8stli 9 | PGP Key: 0xE5E76831 X |2020 Skedsmokorset | svein@jernhuset.no / \ |Norway | PGP Key: 0xCE96CE13 | | svein@stillbilde.net ascii | | PGP Key: 0x58CD33B6 ribbon |System Admin | svein-listmail@stillbilde.net Campaign|stillbilde.net | PGP Key: 0x22D494A4 +-------------------+------------------------------- |msn messenger: | Mobile Phone: +47 907 03 575 |svein@jernhuset.no | RIPE handle: SS16503-RIPE --------+-------------------+------------------------------- If you really are in a hurry, mail me at svein-mobile@stillbilde.net This mailbox goes directly to my cellphone and is checked even when I'm not in front of my computer. ------------------------------------------------------------ Picture Gallery: https://gallery.stillbilde.net/v/svein/ ------------------------------------------------------------ --------------enigF5B57177268512A1BEB7CCBD Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.14 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkxv8mEACgkQSBMQn1jNM7ZrZACgikfGL1DJhJkCFyoTdL9BsO9L bjQAoPG1zDAxkXYuN1Iim4OA+Rj6pORc =WrU6 -----END PGP SIGNATURE----- --------------enigF5B57177268512A1BEB7CCBD--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4C6FF25D.1090304>