From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 5488D13877A for ; Sat, 28 Jun 2014 09:49:54 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 69B94E093E; Sat, 28 Jun 2014 07:55:57 +0000 (UTC) Received: from mail-wi0-f179.google.com (mail-wi0-f179.google.com [209.85.212.179]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 435D9E0825 for ; Sat, 28 Jun 2014 07:55:20 +0000 (UTC) Received: by mail-wi0-f179.google.com with SMTP id cc10so3794559wib.6 for ; Sat, 28 Jun 2014 00:55:13 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:reply-to:to:subject:date:user-agent:references:in-reply-to :mime-version:content-type:content-transfer-encoding:message-id; bh=r16eEJjWX7eug0TjUyNlPFSSh7wfMNtv+fO3opMM6nw=; b=T5aGkh1g+gSg1wbGBNVTE0kE4/cNYa1EXfIlZs765b5wIO/5yfh3X+LfBKaeaPvQDR 05FzwCv417UMXaLOpkf9pRb/ieq78IQmXRQiJV5Lu/6ye2JNuDsGS4FVAOUPF6fQtPe3 RpSxwMHTav8Ij6vhk2z49JBCNM+6TnQHBTwH3+BJUl8RHwHhHCnr8E9tm9jqdZUUNAiC ijr6qE+Q3RCHY+Zaqs1FPpAANegHt6Vv79ynv4drS2mUPUqAxWrNNNMzPd/ZCMNK6jii DEXuI6Fg9Evp38erOUJWs7/sGh2Cl9n1qDB3cLQGh9xnL1sUzWPT/bxmIVQQGSxQjtex Nz/w== X-Received: by 10.180.81.72 with SMTP id y8mr16820375wix.7.1403941757397; Sat, 28 Jun 2014 00:49:17 -0700 (PDT) Received: from dell_xps.localnet (230.3.169.217.in-addr.arpa. [217.169.3.230]) by mx.google.com with ESMTPSA id ey16sm5341742wid.14.2014.06.28.00.49.14 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 28 Jun 2014 00:49:16 -0700 (PDT) From: Mick To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] smartctrl drive error @60% Date: Sat, 28 Jun 2014 08:48:40 +0100 User-Agent: KMail/1.13.7 (Linux/3.12.21-gentoo-r1; KDE/4.12.5; x86_64; ; ) References: <53AA050F.4070907@gmail.com> <201406271422.28115.michaelkintzios@gmail.com> <20140627215432.003491a9@hactar.digimed.co.uk> In-Reply-To: <20140627215432.003491a9@hactar.digimed.co.uk> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart2130733.en0tP5INsl"; protocol="application/pgp-signature"; micalg=pgp-sha256 Content-Transfer-Encoding: 7bit Message-Id: <201406280848.51796.michaelkintzios@gmail.com> X-Archives-Salt: d80480ea-9353-4d80-85bd-e8e1c32fff1c X-Archives-Hash: 50a315cdafe46ffefe6ce46461345c99 --nextPart2130733.en0tP5INsl Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable On Friday 27 Jun 2014 21:54:32 Neil Bothwick wrote: > On Fri, 27 Jun 2014 14:22:09 +0100, Mick wrote: > > I would think that your ISP providers in the US will be blocking > > outgoing port 25 to stop compromised MSWindows machines spamming the > > rest of us. If you use my suggestion there shouldn't be a problem. >=20 > It makes no difference whether you address it directly to your ISP > address or via an alias. The ISP won't block port 25 connections to its > own servers from its own customers, otherwise none of them could send > email at all! In the US many big players are blocking outbound port 25 for their customer= s=20 as a blanket measure to control spam from botnets, e.g.: http://www.verizon.com/Support/Residential/internet/highspeed/general+suppo= rt/top+questions/questionsone/124274.htm If Dale uses the ssmtp.conf I sent he will be using a different port + TLS= =20 encryption and should not have a problem. Even if Dale's ISP does not block port 25 for connections to the ISP's *own= *=20 mail servers, it may well block it to other providers' mail addresses for t= he=20 same reason. This was a common practice some years back (pre-Gmail) when I= SP=20 had started charging for mail services. =2D-=20 Regards, Mick --nextPart2130733.en0tP5INsl Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (GNU/Linux) iQEcBAABCAAGBQJTrnNjAAoJELAdA+zwE4YebuUH/1fF4Mn7wm5qKbtx628KEco/ WmurWBYvpQQwza2gjgC2yOHtOLjDdLkj2dhImO7JmvKsSFkb0dV0cjBTRGpL7umg UlomVAdcQBP7+YJn0HZficcq/U0WrNeZfp76AVEUhAT6YA4eeU6w/OYvcR/54m0A iz+ykGMleQhzqLb0MBs88VFN/Jeay6FBGVr1izJDQwZUdpNDpf5DL9cebGiXKzDu IH6D1oukL6KAVTgU0Cu1CQ23ruAcyi2sUpw9aRZM74z/c9TsrroxOkZtxoHpNE6Y z5T006WcOoNa9LzSMu/cKji6GPQapUkGZxlPtQE2gYXelwxR1aZhc+uIeXo0zqc= =Za58 -----END PGP SIGNATURE----- --nextPart2130733.en0tP5INsl--