Hello, Thank you for the "prompt" response. Read carefully every single bit (yes I mean BIT) of the message listed below! About the tech issue never mind. The issue was on our end. I was forgotten to check my OUTPUT firewall rules. They were set to reject all outgoing connections from our server to any external machine on port 25. However I would like to follow up your answer as a customer and a technical person with more than 7 years of experience in Windows, linux, and *nix like os system administration and network trouble shooting. I really do not want to sound rude or offensive but your response time and the response itself really SUCKS. Second thank you for TEMPLATING me. If any of your tech representatives have read my first message he will see that ALL the necessary information is listed in my first message. By all I mean ALL! You do not need the message headers in case your servers refusing our outgoing connections. You do not even need the output from the MTA log file. Even the fault was on my end (please forgive me about that) your current response is USELESS! Yes. I am one of the system administrators. Otherwise how I am suppose to know all the information provided in my first complain!?!?!?! >>> We would appreciate it if you could provide more information to help us troubleshoot the issue. You need more information? Come one? Did you even checked the entire first message? >>> Please note that if you are not the system administrator for the mail server(s) affected, we encourage you to >>> contact the administrator so they can address the possible issues regarding mailings from the mail server. Yes. Prbbably I am the sysadmin otherwise I would not provide you with all the results from the tests I performed. YES! They are included in my first message. >>> * Explain the details of one event with the delivery problems to Yahoo! You do not even need them if you have carefully checked my first message. >>> Please provide the entire message, including the full text of the error message returned, and full header information. Again this information is useless in case a given SMTP server refusing connections from a given source. There are ONLY 2 reasons for a connection to be refused by the server. 1. The service is down and the deamon is not listening on the specific port. Since you are Yahoo! I tough that it is nearly impossible for your mail servers to be down (even if I have seen such cases) and of-course that was not the case as I was able to telnet to your SMTP mail servers (even they are set in round-robin/load balancing) from other locations but the server specified below. 2. There is a firewall on the way which is blocking these connections with a "connection refused" firewall state. That was the exact case even the fault was on my end. Please excuse me that I forgot to check my firewall rules before I send this report and my EXACT question I was asking about was to check your firewall states so I can determine if you are blocking my connection attempts with the firewall state mentioned above. >>> Within a Yahoo! Mail account, you can display this information by clicking the "Full Headers" link located within >>> the message in the bottom right-hand corner. Sure? w0w :) I was sending messages from an EXTERNAL source to your domain. >>> * The specific server_domain name and IP address of the email server(s) that have the delivery issue to Yahoo! Mail. >>> IP Address: xxx.xxx.xxx.xxx >>> Mail Server Domain Name: server_name.domain.com Hohohohoho. Are you still kidding? They were included in my INITIAL REPORT! >>> * Log messages from your mail server showing which IP you connected to and what responses you got from the remote >>> server at the time you received the corresponding failures/timeouts for the event you are reporting. They were also attached. >>> We appreciate your assistance. This information will be helpful in determining the reason why you are having issues >>> when delivering mail to Yahoo! Mail accounts. More of the information you are asked about in this specific case is USELESS. They root of the problem was "CONNECTION REFUSED" and I explained possible scenarios for such error above. >>> I await your response so I may resolve your issue. I am also waiting for your response. The main problem for the message I am currently writing is that you did not even forward this case to your technical department so they can provide me with adequate answer (Again even it was MY fault) Please explain WHY? If you have forwarded my first message to them could you please explain what kind of technical people you are hiring? Are they blind or they can not read? Or probably your 1st level mail assistance technical support team even do not know how the SMTP works? Original Message Follows: ------------------------- >>REDFRMCON Mail-Id: 1178292208-6312 Name: *snip* Yahoo! ID: *snip* Type of feedback: Problem Problem area: Problems connecting to Yahoo! Error message: SMTP server error How often this occurs: Always Type your feedback here: Your MX servers are REFUSING all SMTP connections that are originating from the following IP addresses: addr:6x.6x.9x.6x addr:6x.6x.9x.1x6 These IP addresses are assigned as a primary and secondary on the server on one of our DEDICATED!!! customers. None of them is blacklisted in any public available spam database root@host [/var/log]# host -t mx yahoo.com yahoo.com mail is handled by 1 g.mx.mail.yahoo.com. yahoo.com mail is handled by 1 a.mx.mail.yahoo.com. yahoo.com mail is handled by 1 b.mx.mail.yahoo.com. yahoo.com mail is handled by 1 c.mx.mail.yahoo.com. yahoo.com mail is handled by 1 d.mx.mail.yahoo.com. yahoo.com mail is handled by 1 e.mx.mail.yahoo.com. yahoo.com mail is handled by 1 f.mx.mail.yahoo.com. root@host [/var/log]# telnet g.mx.mail.yahoo.com. 25 Trying 209.191.88.239... "telnet: connect to address" 209.191.88.239: Connection refused Trying 206.190.53.191... "telnet: connect to address"206.190.53.191: Connection refused root@host [/var/log]# telnet a.mx.mail.yahoo.com. 25 Trying 209.191.118.103... "telnet: connect to address" 209.191.118.103: Connection refused root@host [/var/log]# telnet b.mx.mail.yahoo.com. 25 Trying 66.196.97.250... "telnet: connect to address" 66.196.97.250: Connection refused root@host [/var/log]# telnet c.mx.mail.yahoo.com. 25 Trying 68.142.237.182... "telnet: connect to address" 68.142.237.182: Connection refused Trying 216.39.53.3... "telnet: connect to address 216.39.53.3:" Connection refused root@host [/var/log]# telnet d.mx.mail.yahoo.com. 25 Trying 216.39.53.2... "telnet: connect to address 216.39.53.2:" Connection refused root@host [/var/log]# telnet e.mx.mail.yahoo.com. 25 Trying 216.39.53.1... "telnet: connect to address 216.39.53.1:" Connection refused root@host [/var/log]# telnet f.mx.mail.yahoo.com. 25 Trying 209.191.88.247... "telnet: connect to address" 209.191.88.247: Connection refused Trying 68.142.202.247... "telnet: connect to address" 68.142.202.247: Connection refused ATTENTION!!! Below IS MY QUESTION and it was the core of the problem. That is why I have included it at the end of my complain. Because WE know what we are doing and I do not want to waste your nor mine time. As I previously explained I am also a technical person and I know very well how to write my reports on a specific issue so it could be as easier as possible for the remote end to assist me without wasting the time of both of us. You do not even addressed this question in your response!!! @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ Please check your firewall states if you are filtering this IP addresses or ADVICE ASAP. @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ Thank you in advance. Polite as usual, Valentin