Jeff Breidenbach <[EMAIL PROTECTED]>:
>>We have a list whose canonical name is [EMAIL PROTECTED], but
>>due to existing MX records, it can also be sent to as
>>[EMAIL PROTECTED], [EMAIL PROTECTED], etc, or even
>>[EMAIL PROTECTED]
>
>This sounds broken on your side. The address should look the same no
>matter which MX is doing the work.
Sorry, I wasn't specific enough. We have a single mail server (well,
and a backup), but a bazillion MX records pointing to them. So
unicon-group@{cs,ee,egr,...}.unlv.edu all get delivered to the same
server.
>I have mail-archive set to match things like:
>
> [EMAIL PROTECTED] [EMAIL PROTECTED]
>
>but not things like:
>
> [EMAIL PROTECTED] [EMAIL PROTECTED]
>
>The best I can do given the situation is set up an archive named
>[EMAIL PROTECTED], which should catch everything. Should I go
>ahead and do this? My other choice is to put some funky regular
>expressions in my override configuration, but I'd rather not do that
>for performance reasons.
>
>Jeff
Unfortunately, [EMAIL PROTECTED] will bounce if somebody tries to
send to it, although that would have worked a few years ago before the
university demanded that they control unlv.edu. On the other hand I
definitely don't want you to do something that's going to suck for
everybody, especially since it's a very low volume list. Some of us
have been grumbling about getting some real mailing list software
running for awhile now, so probably the correct solution is to just get
around to doing that now.
Thanks.
Steve
_______________________________________________
Gossip mailing list
[EMAIL PROTECTED]
http://jab.org/cgi-bin/mailman/listinfo/gossip
