[Top] [All Lists]

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

2000-08-28 17:50:59
Chris Newman <cnewman(_at_)innosoft(_dot_)com> writes:

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

I'm sorry; I got a bit confused there.

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'm not advocating MUST or SHOULD here.  It's got to be optional, and
will clearly be useless for enlightened implementations that always use
FQDNs.  Unfortunately there's an installed base that might find local
addresses useful.

I don't want vacation to trigger because I was
bcc'ed on a message also to 
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.

"Any recipient address associated with this script" is built-in and
already there.

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

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

I would expect that "tjs" would refer to the tjs in the SMTP server's
canonical hostname.  If the server is called, it refers
to the former; if the server is called, "tjs" refers to
neither address.  If the box doesn't have a canonical hostname, or the
box doesn't ever support local email addresses, the script can be
rejected, or the address can be ignored (one of these behaviors should
be specified, and it should be the latter).

If virtual domains are involved, then it is unlikely that anyone can
refer to me as local user "tjs" anyway.