Re: [ietf-smtp] own mail server: DNS / static IP / no bad reputation?

Ned Freed <ned.freed@mrochek.com> Mon, 12 October 2020 12:52 UTC

Return-Path: <ned.freed@mrochek.com>
X-Original-To: ietf-smtp@ietfa.amsl.com
Delivered-To: ietf-smtp@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 03C153A1491 for <ietf-smtp@ietfa.amsl.com>; Mon, 12 Oct 2020 05:52:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mrochek.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4Yxq6EIHji2I for <ietf-smtp@ietfa.amsl.com>; Mon, 12 Oct 2020 05:52:26 -0700 (PDT)
Received: from plum.mrochek.com (plum.mrochek.com [172.95.64.195]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C1BD33A1464 for <ietf-smtp@ietf.org>; Mon, 12 Oct 2020 05:52:26 -0700 (PDT)
Received: from dkim-sign.mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RQPKW4M3WW00B5XU@mauve.mrochek.com> for ietf-smtp@ietf.org; Mon, 12 Oct 2020 05:47:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mrochek.com; s=201712; t=1602506842; bh=fyugVwltx6y3NKDFEaxKjZKeXziEAHcrzfbLtYRp9M8=; h=Date:From:Subject:In-reply-to:References:To:From; b=PstE+Z6A9yL7dOJmNRdj4+TBVF7SxmRERJ78cZy7d2aR+6kPHdIHGk0jZ+KCjz/k2 sjsPDT2zYBArMgxmEnesFbUIGU68O0qvlvpMtD0JJRK8bttF5ew41D4xNCcW3fvaK2 NJnvcYXQuvCiPaoJi7K/dnIWyOIfXik/OuL9SZYw=
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Content-type: TEXT/PLAIN; CHARSET=us-ascii
Received: from mauve.mrochek.com by mauve.mrochek.com (PMDF V6.1-1 #35243) id <01RQN4TDY6V4005PTU@mauve.mrochek.com> for ietf-smtp@ietf.org; Mon, 12 Oct 2020 05:47:20 -0700 (PDT)
Message-id: <01RQPKW2Y2E8005PTU@mauve.mrochek.com>
Date: Mon, 12 Oct 2020 05:29:39 -0700 (PDT)
From: Ned Freed <ned.freed@mrochek.com>
In-reply-to: "Your message dated Mon, 12 Oct 2020 09:34:45 +0200" <20201012073445.GA7385@kiel.esmtp.org>
References: <20201009203231.GA91739@kiel.esmtp.org> <20201009204511.42EE023305C4@ary.qy> <20201012073445.GA7385@kiel.esmtp.org>
To: ietf-smtp@ietf.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-smtp/XRgSQ1x2_3ZefZMjgTU8rfQbzv0>
Subject: Re: [ietf-smtp] own mail server: DNS / static IP / no bad reputation?
X-BeenThere: ietf-smtp@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Discussion of issues related to Simple Mail Transfer Protocol \(SMTP\) \[RFC 821, RFC 2821, RFC 5321\]" <ietf-smtp.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-smtp/>
List-Post: <mailto:ietf-smtp@ietf.org>
List-Help: <mailto:ietf-smtp-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-smtp>, <mailto:ietf-smtp-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 12 Oct 2020 12:52:28 -0000

> [please use only the list for replies, thanks.]

> John R Levine wrote:
> > The place I use is called Tektonic, http://tektonic.net/

> Thanks, unfortunately they don't support the OS I'm using.
> But now that you wrote about "VPS" I know what to look for
> (not simply "hosting" - that showed mostly "web hosting")

> > (mostly) transparent outbound mail filtering so their reputation seems

> If STARTTLS is used, they shouldn't be able to do it, unless they
> mess with SMTP (or much worse: with TLS), right?

Add to that the reality that VPS solutions are far from immune to the
same sort of blocking issues you get from a cloud provider.

Several of the people I know using VPS solutions to send small amounts of
legitimate commercial email have been hit by IP reputation blocks recently. In
at least two cases all it took was a single noisy neighbor sending a bit too
much mail without jumping through the necessary hoops. AFAICT no spam,
phishing, etc. was involved.

Keith may have expressed himself badly, but like it or not, he has a point.
Operating a mail system is increasingly difficult, and a lot of that difficulty
is associated with limits and restrictions imposed by large providers in a
fairly arbitrary way.

And no, I don't have a solution to this problem. But claiming the problem
doesn't exist, or that VPS solutions or whatever are the necessary magic, isn't
helpful.

Now if you'll excuse me, I need to get back to figuring how the limit changes
one of the MSPs has just implemented so the small amount of opt-in mailing list
mail I send to them isn't unnecessarily delayed.

				Ned