On Sat, Apr 24, 1999 at 11:28:38AM -0500, Bruno Wolff III wrote:
> On Fri, Apr 23, 1999 at 11:55:13AM -0500,
> Fred Lindberg <[EMAIL PROTECTED]> wrote:
> > On Fri, 23 Apr 1999 16:40:44 GMT, Sam wrote:
> >
> > >Actually, what Qmail should do is to reject that address as a recipient
> > >address up front, telling the luser to fix it.
> >
> > Outlook express talks SMTP to qmail. It should _send_ correctly. IMHO,
> > code to check syntax is wasted in qmail, unless required for function.
> > In this case, all that would result is a [maybe] easier-to-interpret
> > error message.
>
> Most likely this is happening because the address is being passed as
> command arguments to qmail-inject. That argument is a raw address so
> it is pretty much anything goes. The address will get encoded for use
> in the smtp protocol by qmail.
No. The problem is with Outlook Express (and with Outlook, for that matter.)
Everytime I've seen it, it's been from addresses Outlook (Express) has
harvested from received messages. It tacks either control characters
or spaces on the end. So, basically, qmail-smtpd (these programs are
Microsoft programs; they know nothing about qmail-inject or the Unix
command-line) receives an address that looks like <[EMAIL PROTECTED] >
The solution is straightforward. Go into the addressbook, select the entire
block, delete it, and retype it. Problem goes away.
Qmail shouldn't be doing anything to distort what the client tells it it
wants, IMO.
> Sendmail doesn't work like this. Sendmail treats addresses on the command
> line as encoded and will attempt to decode them. I had some problems with
> mutt and addresses that were quoted because of this difference.
Again, not the issue.
Greg
