you are right, mail addresses are case-insensitive.
That upper-case matching works with, e.g. SMTPGATE/users/SMSNotifications added
to my confusion.
It would also be useful to put this into the reference manual for MOUNT and for SMTPCONF.
Now it works very well.
I got SMTPGATE working as well as the two servers for the SMS provider.
SMTPGATE has the advantage of more control of the mail, e.g. reject empty subjects, empty bodies
and - for tests - send a Bcc: to other addresses.
> -----Original Message-----
> From: Yutaka Sato [mailto:email@example.com]
> Sent: Tuesday, March 10, 2009 1:14 PM
> To: firstname.lastname@example.org
> Cc: Bladt, Norbert
> Subject: Re: [DeleGate-En] dg 9.9.1 as SMTP gateway
> In message <_A4396@delegate-en.ML_> on
> 03/10/09(20:26:13) I wrote:
> |Oh, I see. You are using upper case leter "SMS" in the
> MOUNT which is
> |not matched in this case. You need "nocase" MOUNT options
> as follows:
> | MOUNT="SMS@tss.ch smtp://email@example.com nocase"
> Maybe I should explain why it is so (for possible readers in
> future :).
> MOUNT is designed originally in DeleGate/1.4.0 for rewriting URL path
> of HTTP which is case sensitive. Thus the default is case sensitive
> and "nocase" option is necessary to do caseless matching.
> On the other hand, mail-addresses are manipulated caselessly in mail
> in general. So it is manipulated internally "normalized" to
> lower case
> letters if not specified the option "SMTPCONF=mboxcase".
> That is, "SMS@tss..ch" in RCPT from a client is represented as
> internally and does not match the "SMS@tss..ch" in the MOUNT
> without "nocase".
> So another solution is writing the MOUNT in lower case
> letters as this:
> MOUNT="firstname.lastname@example.org smtp://email@example.com"
> 9 9 Yutaka Sato <firstname.lastname@example.org> http://delegate.org/y.sato/
> ( ~ ) National Institute of Advanced Industrial Science and
> _< >_ 1-1-4 Umezono, Tsukuba, Ibaraki, 305-8568 Japan
> Do the more with the less -- B. Fuller