 
|
| Mime-Version: |
1.0 |
| Sender: |
|
| Date: |
Wed, 3 Apr 1996 11:11:51 -0500 |
| Reply-To: |
|
| Subject: |
|
| From: |
|
| Content-Transfer-Encoding: |
7bit |
| In-Reply-To: |
|
| Content-Type: |
multipart/signed; boundary="===_-1_Wed_Apr__3_11:11:50_EST_1996";
micalg=pgp-md5; protocol="application/pgp-signature" |
| Comments: |
|
On Wed, 03 Apr 1996 09:17:02 CST, you said:
> * List-Address= [log in to unmask]
Well, unless I've not had enough caffeine yet, this means that the mail will
go out as being from "[log in to unmask]", right?
> Everything goes along just fine UNTIL someone (or something) sends
> mail to [log in to unmask] instead of
> [log in to unmask]
>
> Why is this happening.
If it went out as [log in to unmask], then any reasonable guess as to where
to send to would be [log in to unmask], not [log in to unmask]
Where is it supposed to guess the value of "realnode" from?
> Short of creating an alias for each listname-owner as well, is there
> something we can do to get it to go to the right address?
Well, if you're gonna call it [log in to unmask], you'll need to have your
mail service Do The Right Thing with [log in to unmask], listname-request,
and so on. Whether this involves creating aliases, forwarding, or waving
a dead chicken over the CPU (most commonly associated with Microsoft products)
will depend on your local software configuration....
--
Valdis Kletnieks
Computer Systems Engineer
Virginia Tech
|
|
|
