×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Hello Brad,
Am 20.10.2022 um 00:34 schrieb Brad Stone <bvstone@xxxxxxxxx>:
Not sure.. I've never found any specifics on it.
It's well documented where "all internet things" are documented: In RFCs. Maybe see here for details:
https://www.rfc-editor.org/rfc/rfc1893
https://www.rfc-editor.org/rfc/rfc3463
A good summary can be read here:
https://en.wikipedia.org/wiki/List_of_SMTP_server_return_codes
But not all servers reply with those types of errors
I'd love to see an example of those, because numeric status codes are an inherent feature of the SMTP protocol exchange itself.
Besides that, I've also had one of those "Multi Function" Copy-Scan-Fax-Print machines at a customer site. The (forgotten) manufacturer implemented the SMTP exchange in a funny way: It tried to be polite and instead of giving its name in the HELO, it was giving that of the configured remote. Just has humans would say "hello you". Hilarious when I found out what went wrong. :-)
and sometimes the error is just because it can't connect.
Of course.
I've seen MSF jobs running well over 50% for days because of this.
I think so, if people use it for direct delivery.
:wq! PoC
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
[javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.
midrange.com
