If an email address starts with backslash ("\"), sendmail will not
perform alias substituion. I'm attempting to use that feature inside my
Sieve script (generated by Horde's Ingo application) as follows:
if true {
redirect "\\alex (AT) milivojevic (DOT) org";
keep;
}
However, I'm getting an error from timsieved:
script errors: line 7: address '\alex (AT) milivojevic (DOT) org': parse error,
unexpected $undefined.
Does this means Sieve does not support "backslashed" addresses, or my
Sieve script manager program generated errornous script? If later, what
would be the correct way to escape backslash that is part of email address?
Thanks,
Aleksandar Milivojevic
Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ:
List Archives/Info:

Quoting Sury <ondrej (AT) sury (DOT) org>:

Well,

IMH you are mixing .forward syntax with /usr/sbin/sendmail behaviour.

Sieve reinjects forwarded mail using /usr/sbin/sendmail (or whatever you
have configured in /etc/imapd.conf) and since backslashed email address
is not valid, so isn't sieve script. So what you want to do is to learn
your /usr/sbin/sendmail to not do alias substitution.

I haven't really checked RFCs to see if "\" is allowed charcter in an email
address. It might be that it is, or that it isn't, or it might be that RFCs
simply discourage its use. However, "\" characher is always interpreted by
sendmail. It is not limited to dot forward file. If you send email to
recipient whose MTA is sendmail and "backslash" his email address,
aliases will
not be expanded on it. I don't know how other MTA (other than sendmail) would
treat it.

What I have are two mail servers. I want to forward from one to
another (which
runs sendmail), and make sure that email *stays* there. I've tested it (by
manually sendmail email to address beggining with "\"), it works. Simple
solution for simple problem, no need to complicate things with sendmail
configuration wizardy (and risk side-effects). Also known as KISS
principle. The only trouble is how to convince timsieved to accept "\"
character in an
email address, and to inject it back to MTA the way I specified it. If it is
possible at all.

This message was sent using IMP, the Internet Messaging Program.

Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ:
List Archives/Info:

July 13, 2005 9:49:34 AM -0500 alex (AT) milivojevic (DOT) org wrote:

I haven't really checked RFCs to see if "\" is allowed charcter in an
email
address. It might be that it is, or that it isn't, or it might be that
RFCs
simply discourage its use.

It doesn't appear to be allowed by RFC2822 in local-part as it appears in
"specials" and not "atext".

<>
-David

Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ:
List Archives/Info:

Quoting David R Bosso <dbosso (AT) lsit (DOT) ucsb.edu>:

It doesn't appear to be allowed by RFC2822 in local-part as it
appears in "specials" and not "atext".

<>

In which case I guess there's no way to have timsived accept an address
containing backslash? then editing timsived source and recompiling?

This message was sent using IMP, the Internet Messaging Program.

Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ:
List Archives/Info:

Quoting "Scott M. Likens" <damm (AT) yazzy (DOT) org>:

It seems unrealistic to me to expect a mailer to 'accept' backslashes in
email address's. Let alone, sieve,etc.

Well, any MUA I had in my hands will gladly accept them. Among the
MTA, I know
sendmail accepts backslashes *and* processes them as described (if envelope
address starts with backslash, aliases are not expanded on it). It also
preserves them when relaying email to another MTA. I do realize this is
sendmail specific feature, and as it appears from another post in this thread,
not really RFC compliant.

I would ask what brought you to use backslashes in email address's,
because not even Exchange uses them really. (Cept for logging in)

Sendmail uses them. I'm using sendmail. It seemed to be simple, clean and
quick solution to resolve one mail-loop problem I had. Sorry for bothering so
many people for so long time, I just hoped there was a simple way to make
timsieved accept backslash char as part of email address.

But yes you would need to rebuild sieve to support \'s, and currently
you'd have to build support for it to support it. So by all means, make
it, and send it to the list and if people love it maybe it'll become a
part of cyrus permanently.

Hmmm Somehow I got the feeling (from past discussions on the list about
relaxing some other types of checks) that this kind of thing makes it really
hard into official cyrus distribution, even when people love the
feature. Plus
this one is specific to single MTA (sendmail), and also very rarely used :-(

This message was sent using IMP, the Internet Messaging Program.

Cyrus Home Page: http://asg.web.cmu.edu/cyrus
Cyrus Wiki/FAQ:
List Archives/Info: