From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.general/36358 Path: main.gmane.org!not-for-mail From: Graham Murray Newsgroups: gmane.emacs.gnus.general Subject: Re: Sender header? Date: 24 May 2001 20:30:17 +0000 Message-ID: References: <01May23.141128edt.115245@gateway.intersys.com> <01May24.115917edt.115250@gateway.intersys.com> <01May24.143521edt.115214@gateway.intersys.com> <01May24.153439edt.115213@gateway.intersys.com> NNTP-Posting-Host: coloc-standby.netfonds.no Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1035171957 8181 80.91.224.250 (21 Oct 2002 03:45:57 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Mon, 21 Oct 2002 03:45:57 +0000 (UTC) Return-Path: Original-Received: (qmail 28241 invoked by alias); 24 May 2001 20:31:24 -0000 Original-Received: (qmail 28236 invoked from network); 24 May 2001 20:31:21 -0000 Original-Received: from barnowl.demon.co.uk (158.152.23.247) by gnus.org with SMTP; 24 May 2001 20:31:21 -0000 Original-Received: (from graham@localhost) by barnowl.demon.co.uk (8.12.0.Beta7/8.12.0.Beta7) id f4OKUHck030899; Thu, 24 May 2001 20:30:17 GMT Mail-Copies-To: nobody Original-To: ding@gnus.org In-Reply-To: <01May24.153439edt.115213@gateway.intersys.com> (Stainless Steel Rat's message of "Thu, 24 May 2001 15:34:23 -0400") User-Agent: Gnus/5.090004 (Oort Gnus v0.04) Emacs/20.7 Original-Lines: 28 Xref: main.gmane.org gmane.emacs.gnus.general:36358 X-Report-Spam: http://spam.gmane.org/gmane.emacs.gnus.general:36358 Stainless Steel Rat writes: > Yes, that is exactly what I think. A records are required for all machines > on the Internet that have anything to do with mail, and MX records should > exist for all such hosts. Proper mail handling depends on that being the > case. If your host has neither A nor MX records then it is not configured > correctly. Trying to make Gnus work around that does not fix the problem. I think that there are at least 2 situations in which that does not apply. 1) Dial-up hosts using dynamic IP. In this situation, the user is often given a mailbox of user@isp.com. There are MX records for isp.com which points at the ISP's mail server(s). However there is no (fixed) A record for the customer's system, and its name is dynamically assigned when the system connects to the ISP. Therefore, it is not possible to configure the system with its FQDN. 2) Hosts on an internal LAN (probably using RFC 1918 addresses) behind a firewall. All users on the LAN are allocated mailboxes in the form of user@x.com. Internally the hosts on the LAN are configured as a.x.com, b.x.com etc. The internal host names should never be visible to the Internet "at large". Currently if user@a.x.com sends mail with a from address of user1@x.com (the externally visible mailbox), gnus will set the Sender to user@a.x.com - which address should be visible outside of x.com's internal network.