From owner-freebsd-doc@FreeBSD.ORG Thu Jan 17 16:12:44 2013 Return-Path: Delivered-To: freebsd-doc@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 1E8C5289 for ; Thu, 17 Jan 2013 16:12:44 +0000 (UTC) (envelope-from lists@eitanadler.com) Received: from mail-la0-f48.google.com (mail-la0-f48.google.com [209.85.215.48]) by mx1.freebsd.org (Postfix) with ESMTP id 77628B02 for ; Thu, 17 Jan 2013 16:12:43 +0000 (UTC) Received: by mail-la0-f48.google.com with SMTP id ej20so2863163lab.35 for ; Thu, 17 Jan 2013 08:12:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=eitanadler.com; s=0xdeadbeef; h=x-received:mime-version:from:date:message-id:subject:to :content-type:content-transfer-encoding; bh=JIdXzo88AHSHPUnauCgJGZcHESI96kXc/E2+rIIaPi4=; b=eN1Pry12+sE3wzJwpqJSJiiBjGU2DGTJOCUsuf50xxIqZwoMxsaBydcbumneQgdBuy QaBgOVU4+QRBnTsNqiL7uboUEd8ZRvw6UUMQrbbsXebwmbVjBh03AxO+0SltRL7NXkJq IyNRrqwIbRfEo3esZW+MoUH3pIkWzIY+YDlTk= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=x-received:mime-version:from:date:message-id:subject:to :content-type:content-transfer-encoding:x-gm-message-state; bh=JIdXzo88AHSHPUnauCgJGZcHESI96kXc/E2+rIIaPi4=; b=PJ0p0e1WCNolYTVunmkNmutk6CcyJW41SdvNJm8qIR4Sj+LNabd47+99GffObclhAv OdUpAWXdVmIkHY7QILZEmyWUqjk2lnf25QbnrRQMbN4DdvXcZrx2pQpzNNU+xQIcvzI8 bQj7oKyuxzUqqOVRHPIFz1VtOFJmW+yaQAPxvSicfumQmOHi/stcWh8njLKWwI3Ku4Bd /iTjCx6RJJGGnVls8KAnstERLbj1czMHIlnv/jjFpJsIzOPEj3ayifIww37ledgSXK52 Zm7Hbb+nXq8+rMRG9DADmpeHsGaNQ3HNILaqVPtmVS7LFWs4cEFMPdIHFitfmHChHCuw V6QA== X-Received: by 10.112.88.7 with SMTP id bc7mr2480816lbb.108.1358439162051; Thu, 17 Jan 2013 08:12:42 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.30.131 with HTTP; Thu, 17 Jan 2013 08:12:11 -0800 (PST) From: Eitan Adler Date: Thu, 17 Jan 2013 11:12:11 -0500 Message-ID: Subject: documenting the requirements for FreeBSD.org to send mail To: freebsd-doc@freebsd.org Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Gm-Message-State: ALoCoQlZvvIx01HJgPcLqt1Qbq1JFgcQ0OuuV2PTTyCcIbM7C2vsIeJvdTpuhD+bcUt/SeBHkHc2 X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2013 16:12:44 -0000 I am working with clusteradm and postmaster to fix the freebsd-mail-bounces= FAQ: Content and patch are pasted below. The one concern is the manner that I described "Forward-confirmed reverse DNS" is too specific and knocks out correctly configured clients. In particular there does not have to be a 1-1 mapping, there just has to exist *a* mapping. Can anyone suggest better wording for this specific case or general improvements for this question? =3D=3D=3D=3D=3D content =3D=3D=3D=3D=3D The FreeBSD.org mail system implements some Postfix checks on incoming mail and rejects mail that is either from misconfigured relays or otherwise appears likely to be spam. Some of the specific requirements are: -- The IP address of the SMTP client must "reverse-resolve" to a hostname. The IP address of the connecting host must have "reverse DNS" set up pointing to a domain which resolves back to the conneting IP address. -- The fully-qualified hostname given in the SMTP conversation (either HELO or EHLO) must resolve to the IP address of the client. Other advice to help your mail reach its destination include: -- Mail should be sent in plain text, and messages sent to mailing lists should generally be no more than 200KB in length. -- Avoid excessive cross posting. Choose one mailing list which seems most relevant and send it there. If you still have trouble with email infrastructure at FreeBSD.org send a note with the details to ;. Include a date/time interval so that logs may be reviewed =E2=80=94 and note that we only keep one week's worth of mail logs. (Be sure to specify the time zone or offset from UTC.) =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D patch: commit 9b12f8184246956a8adf4278757ad3d2747d49e7 Author: Eitan Adler Date: Mon Dec 3 00:21:40 2012 -0500 Update and clarify the freebsd-mail-bounces question (why mail to freebsd.org bounces) to reflect reality. Submitted by: postmaster (dhw) Approved by: ??? (mentor) diff --git a/en_US.ISO8859-1/books/faq/book.xml b/en_US.ISO8859-1/books/faq/book.xml index 1b7ed76..55f4a8a 100644 --- a/en_US.ISO8859-1/books/faq/book.xml +++ b/en_US.ISO8859-1/books/faq/book.xml @@ -8910,69 +8910,56 @@ hint.sio.7.irq=3D"12" The FreeBSD.org mail - system implements some of the stricter + system implements some Postfix checks on incoming mail - and rejects mail that is either misconfigured or is - potential spam. Your mail might bounce for one of the - following reasons: + and rejects mail that is either from misconfigured relays or + otherwise appears likely to be spam. Some of the + specific requirements are: - The email is being sent from a known spam domain or - IP block. + The IP address of the SMTP client must + "reverse-resolve" to a hostname. - The &os; mail servers reject email from known spam - sources. If you have service through a company or - domain who generates or relays spam, please switch to a - service provider who does not. + The IP address of the connecting host must have + "reverse DNS" set up pointing to a domain which + resolves back to the conneting IP address. - The body of the email only contains HTML. - - Mail should be sent in plain text only. Please - configure your mail user agent to send plain - text. + The fully-qualified hostname given in the + SMTP conversation (either HELO or EHLO) must resolve + to the IP address of the client. + - - The mailer at FreeBSD.org cannot resolve - the IP address of the connecting host back to a - symbolic name. - - Working reverse DNS is a standard requirement for - accepting mail from a host. Set up reverse DNS for your - mail server's IP address. Many home services (DSL, - cable, dialup, etc.) will not give you this option. In - this case, relay your email through your service - provider's mail server. - + Other advice to help your mail reach its destination + include: + - The hostname given in the EHLO/HELO part of the SMTP - exchange cannot be resolved to an IP address. - - A fully qualified, resolvable host name is necessary - in this part of the SMTP dialogue before mail will be - accepted. If you do not have a host name that is - registered in the DNS, then you should use your service - provider's mail server to relay your mail. + Mail should be sent in plain text, and messages + sent to mailing lists should generally be no more than + 200KB in length. - Your message had a message ID ending with the string - localhost. - - Some mail user agents generate bad message IDs which - will not be accepted. You will need to persuade your mail - user agent to generate a valid message ID or else - configure your mail transfer agent to rewrite - them. + Avoid excessive cross posting. Choose + one mailing list which seems most + relevant and send it there. - - + + If you still have trouble with email infrastructure at + FreeBSD.org send a note + with the details to + postmaster@freebsd.org;. Include a + date/time interval so that logs may be reviewed — + and note that we only keep one week's worth of mail logs. + (Be sure to specify the time zone or offset from + UTC.) + + --=20 Eitan Adler