-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry about all the list clutter, I just seem to be having a bad day ;-)
The company I'm with uses Webtrends professional suite for our website
reporting. Webtrends is supposed to send an email responce containing a
website report.
The software
On Wed, 6 Oct 1999 15:08:02 -0400, Jeff McNeil wrote:
>The software generates my report fine, connects to the qmail server, and says
>it's successfully sent the message, but guess what? No Email. Email just never
>shows up.I can send an email though the same server via netscape without
>any
Jeff McNeil wrote:
>
I had a CR/LF problem with a JavaMail implementation. I used
recordio to track down the problem. I first noticed the problem in
the logs, whem smtpd would exit with a status of 256. The remote
unit would think the mail was delivered because smtpd said OK when
qui
On Wed, Oct 06, 1999 at 03:51:19PM -0400,
"Thomas M. Sasala" <[EMAIL PROTECTED]> wrote:
> Jeff McNeil wrote:
> >
>
> I had a CR/LF problem with a JavaMail implementation. I used
> recordio to track down the problem. I first noticed the problem in
> the logs, whem smtpd would exit with
I wasn't checking the status of quit. As it turns out,
the transport implementation did not check the status of any of
command. It merely stuffed the whole message into the smtp
server and closed the connection. It never waited for a response
from the server. If the transport code had
On Wed, Oct 06, 1999 at 04:48:21PM -0400, Thomas M. Sasala wrote:
> In any case, why does smtpd return 256 and throw away the
> mail? I have records of a good transaction (all commands get a +OK)
> yet smtpd exits with 256 and the mail is eternally lost.
What do you mean with "smtpd exits
+ Markus Stumpf <[EMAIL PROTECTED]>:
| As with disappering messages:
| smtpd simply accepts the email and hands it on to other processes
| (qmail-queue).
That statement may be a bit misleading. The cronology is the other
way around: qmail-smtpd hands the message to qmail-queue, and does not
giv
I was getting something like this (please note this is not
the actual log - I can post that tomorrow is someone wants to see
it):
933785415.436366 tcpserver: status: 1/40
933785415.437241 tcpserver: pid 6010 from 127.0.0.1
933785415.462990 tcpserver: ok 6010 localhost:127.0.0.1:25
localho
On Thu, Oct 07, 1999 at 07:32:45AM -0400,
"Thomas M. Sasala" <[EMAIL PROTECTED]> wrote:
> I was getting something like this (please note this is not
> the actual log - I can post that tomorrow is someone wants to see
> it):
>
> 933785415.436366 tcpserver: status: 1/40
> 933785415.437241 t
I think you are missing the point. I'm not looking at the
exit code. Let me be specific. I was using a Java transport class
that was not properly written. I would send a message with this class
and the class would say the message was sent. However, in reality,
smtpd would reject the
On Thu, Oct 07, 1999 at 11:24:57AM -0400, Thomas M. Sasala wrote:
> To debug the problem I used recordio. I noticed that the
> class was not reading any output from smptd. It just stuffed the
> whole message into smptd and exited. So, I modified the class to
> read input and check for +OK
"Thomas M. Sasala" <[EMAIL PROTECTED]> wrote:
> I think you are missing the point. I'm not looking at the
>exit code. Let me be specific. I was using a Java transport class
>that was not properly written. I would send a message with this class
>and the class would say the message was se
My bad. This is true - the +OK and -ERROR are from
POP sessions. I should of said XXX ok for the smtp session.
I was getting 2xx ok as responses.
Markus Stumpf wrote:
>
> SMTP dialog does not use "+OK" oder "-ERROR", but "Codes". See RFC 821
> for examples and definitions.
> Whatever y
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Subject: Re: A second strange problem.
>
>
> So, the point here is that smtpd responded with +OK for everything,
> leading me to believe the mail had been accepted and was delivered.
14 matches
Mail list logo
