"Ihnen, David" wrote:
>
> Dale:
>
> Although your remote concurrency DOES appear to be a problem, I do not
> believe this is the problem encountered by the netscape user.
>
> If you have extended periods of time during which you have 20/20 connections
> used, by all means, raise the remote concurrency limit. I keep mine at 120,
> and the only time its reached that was intermittently and very briefly while
> clearing a 3 day mail backup.
>
> So, I used what you said and looked at the source of netscape. That error
> text is NS_SENDING_FROM_ERROR_COMMAND - and is only called when
>
> A. MAIL From: command has been sent
> and
> B. a 250 response code is not returned
>
> According to the qmail-smtpd source, when you send a mail command this is
> run:
>
> void smtp_mail(arg) char *arg;
> {
> if (!addrparse(arg)) { err_syntax(); return; }
> flagbarf = bmfcheck();
> seenmail = 1;
> if (!stralloc_copys(&rcptto,"")) die_nomem();
> if (!stralloc_copys(&mailfrom,addr.s)) die_nomem();
> if (!stralloc_0(&mailfrom)) die_nomem();
> out("250 ok\r\n");
> }
>
> I checked - of bmfcheck and addrparse and err_syntax, die_nomem only
> err_syntax and die_nomem can return something to the user, and that is
>
> void err_syntax() { out("555 syntax error (#5.5.4)\r\n"); }
>
> and
>
> void die_nomem() { out("421 out of memory (#4.3.0)\r\n"); flush(); _exit(1);
> }
>
> Neither of which have anything to do with 4.7.1 - which isn't a defined
> error code in any of the qmail programs.
>
> SO - My conclusion is that the system *MUST* be talking to some other
> service, than qmail-smtpd, or it would say something more like "syntax error
> (#5.5.4)" or "out of memory (#4.3.0)", rather than just "4.7.1".
>
> Troubleshoot the client's settings and the IP path. Maybe its trading off
> to different smtp servers? Maybe the dns or IP he's going to maps to more
> than one server?
>
> Of course, my source analysis may be flawed, and I invite all to look it
> over.
>
> Netscape source: http://lxr.mozilla.org/seamonkey/search
>
> David (who is having more fun that he probably is allowed to.)
Thanks for looking that up. I set my concurrency remote to 120 so that
should take care of the back log during busy periods. Hopefully that
will also get rid of this problem. I talked with the user and he ok
with it he just thought it was odd that it was doing that. I think what
could be happening is some sort of delay or routing problem between his
isp and my server. I am going to keep an eye on it and see what
happens. Netscape does do wierd things sometimes.
Too much fun never hurt anyone unless you are one of those darwin award
winners where you tried to make your car break the sound barrier and was
last seen passing mars. :)
--
Dale Miracle
System Administrator
Teoi Virtual Web Hosting
