Hector Santos wrote:
----- Original Message -----
Your path was not verifier. Now lets look at WCSAP log:
20031218 18:10:54 0001ac00 -------------------------------------
20031218 18:10:54 0001ac00 version: 1.42 / 1.36
20031218 18:10:54 0001ac00 cmd : MAIL FROM
20031218 18:10:54 0001ac00 method : WCSAP
20031218 18:10:54 0001ac00 uid : 0
20031218 18:10:54 0001ac00 ip : 204.127.198.39
20031218 18:10:54 0001ac00 cdn : rwcrmhc13.comcast.net
20031218 18:10:54 0001ac00 hdn :
20031218 18:10:54 0001ac00 rbl : 0
20031218 18:10:54 0001ac00 relay : 0
20031218 18:10:54 0001ac00 from : <millenix(_at_)zemos(_dot_)net>
20031218 18:10:54 0001ac00 filter : test
20031218 18:10:54 0001ac00 result : 0
20031218 18:11:04 0001ac00 no ptr record - rejected
20031218 18:11:04 0001ac00 SMTP response code: 552
20031218 18:11:04 0001ac00 wcsap finish
20031218 18:12:05 0001ac01 -------------------------------------
Sorry, NO PTR RECORD FOR ZEMOS.NET
You ain't GETTING IN! PERIOD!
Looking at this log, something is unclear to me. Are you connecting to
the comcast.net server that's connected to you, or are you connecting
to a query-returned MX for zemos.net? Your manual tests in your later
response to Markus indicate that you're checking against zemos.net, but
that's not explicit here. In fact, I see no mention of zemos.net in the
WSCAP log other than in my address.
Good point. I'll make sure its logged better. The PTR logging was
incorrect. I copied some PTR lookup (not used yet) logging code. It was an
DNS MX lookup error that was returned. It a NX_DOMAIN DNS error (non
existent domain). I can't explain why it happen that one time, but it
seems ok now. I think it might have been a timeout. As you can see there
was a 10 second delay in the response. I need to increase this timeout.
That will resolve it.
What exact DNS queries are you making, what connections are you
opening, and what commands are you sending? I'm not about to tell all
of the other zemos.net MX operators to log SMTP transactions to debug
your broken software.
Oh, and you think you can write better software than I? What have you out
there? Don't get go buddy.
I said no such thing. The log message you posted gave no indication that
WCSAP received the response NXDOMAIN. Thus, I assumed that it made the
connection that one would expect (to a zemos.net MX) and the verification
failed there.
If you're connecting to the comcast.net server in an attempt to verify
the return path, that's WRONG! If it accepted mail for zemos.net, it
would be an open relay.
Look, the DOMAIN PART of your return address, ZEMOS.NET is used for the
verification. Thats obvious ok?
rwcrmhc13.comcast.net is the client domain provided by your MTA at the
HELO/EHLO state. It is just logged in wcSAP and will be used in the future
when the SMTP specs are tighten.
I see that, but it was something I had to ask, since your log output didn't
indicate it explicitly.
Philip Miller
P.S.: There is 1 'L' in my given name.
Sorry. I'll make sure to remember there is one 'l' in your given name.
No memory required. It appears in the headers of every email I send.
PS: Why are you an A-HOLES!? No wonder nothing is getting DONE!!
Anyone who tries to contributes GETS shot down with ad-nuisance rhetoric.
Maybe if you shit and get off the pot and WRITE SOME BETTER SOFTWARE with
all the EXPERTISE you speak of, then maybe the world would be better off
with PHIL-WARE!
There's no question in my mind that the software you are writing is useful
and is an improvement over many other things on the market or freely available.
Look at it this way: You're writing commercial software. We are debugging
edge cases in your software for free. I understand that the DNS failure we
just witnessed was an odd anomaly that your software couldn't have done
anything to prevent. However, its log output didn't indicate that anomalous
result, but something else.
This isn't about who's smarter. It's about reducing spam through
technological means.
Yes, I made remarks I shouldn't have, and I regret that. We don't need
personal remarks on this list.
Philip Miller
_______________________________________________
Asrg mailing list
Asrg(_at_)ietf(_dot_)org
https://www1.ietf.org/mailman/listinfo/asrg