ietf-mta-filters
[Top] [All Lists]

Re: does vacation need to define what an address looks like?

2000-08-28 17:17:42
--On Monday, August 28, 2000 16:29 -0700 Tim Showalter <tjs(_at_)mirapoint(_dot_)com> wrote:
Chris Newman <cnewman(_at_)innosoft(_dot_)com> writes:
Suppose I have the addresses <cnewman(_at_)isp(_dot_)com> and 
<*(_at_)cnewman(_dot_)isp(_dot_)com>
which share the same Sieve script?  Does the resolution of a "local"
address act differently depending upon which address the message being
filtered was sent to?

I don't understand what those addresses indicate in either redirect or
vacation.  vacation doesn't currently specify that addresses are
supposed to be wildcards, and that wasn't my intent when I wrote it.

I was using shorthand. I was suggesting a scenario where <cnewman(_at_)isp(_dot_)com> goes to my mailbox, as does any message with a domain part of "cnewman.isp.com" (regardless of the local part).

In some implementations, I can unfortunately imagine the local-part
being the only information available.

Suppose we consider "local" to mean domain of "", with the @ left out
since there's no domain.

That means the address can't be resolved, because there could be 200 different mailboxes which receive mail addressed to the local part "cnewman" in the same mailstore. In short, the concept of "local" is meaningless to me. The only concept that might have meaning is "same domain as in RCPT TO being processed", but for a given sieve script, that might have many different values.

I don't want vacation to trigger because I was
bcc'ed on a message also to 
tjs(_at_)some(_dot_)domain(_dot_)ive(_dot_)never(_dot_)heard(_dot_)of(_dot_)com(_dot_)
  If
I instruct vacation that "tjs" is an alias for me, I want it to trigger
only when the mail is to <tjs>,
i.e., no domain at all.

It sounds like you need a distinguished syntax for "any recipient address associated with this sieve script". So add that (perhaps "<>" would work for that). Then supporting subaddresses, vanity domains and their ilk becomes an implementation detail rather than a scripting nightmare.

I don't think virtual domains are a problem; however, vanity domains may
be.

If tjs(_at_)domain1(_dot_)com and tjs(_at_)domain2(_dot_)com are two different users, then which one does "tjs" refer to?

                - Chris