From: fdc@cliwe.ping.de (Frank D. Cringle)
Subject: Re: Changing Return-Path
Date: 11 Nov 1998 17:06:15 +0100 [thread overview]
Message-ID: <vt1znanrig.fsf@cliwe.ping.de> (raw)
In-Reply-To: Anders Melchiorsen's message of "11 Nov 1998 12:48:38 +0100"
Anders Melchiorsen <and@kampsax.dtu.dk> writes:
> What I was wondering was whether the Return-Path: should be my e-mail
> address or the account I am posting from (which is unreachable due to
> a firewall).
If the Return-Path is unreachable due to a firewall, lots of mail
servers will reject the mail, whether the recipient is a mailing list
or not. Postmasters don't like accepting mail that they won't be able
to bounce later if the delivery fails.
--
Frank Cringle, fdc@cliwe.ping.de
voice: (+49 2304) 467101; fax: 943357
next prev parent reply other threads:[~1998-11-11 16:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1998-11-10 22:01 Anders Melchiorsen
1998-11-11 9:16 ` Matt Armstrong
1998-11-11 11:48 ` Anders Melchiorsen
1998-11-11 16:06 ` Frank D. Cringle [this message]
1998-11-11 18:14 ` Matt Armstrong
1998-11-11 19:03 ` Karl Kleinpaste
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=vt1znanrig.fsf@cliwe.ping.de \
--to=fdc@cliwe.ping.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).