550-5.7.1 [22.214.171.124] The IP you're using to send mail is not authorized
It may be that you are sending the wrong HELO message.max7 wrote:]T 20090108 231048 4966876a HELO max-023fe7af57c
SORBS wrote: Dynamic IP Space (LAN, Cable, DSL & Dial Ups)
Netblock: 126.96.36.199/13 (188.8.131.52-184.108.40.206)
Record Created: Fri Jan 2 00:23:09 2009 GMT
Record Updated: Fri Jan 2 00:23:09 2009 GMT
Additional Information: [#218700 - RoadRunner Supplied List (02/01/2009)] Dynamic/Generic IP/rDNS address, use your ISPs mail server or get rDNS set to indicate static assignment.
Currently active and flagged to be published in DNS
If you wish to request a delisting please do so through the Support System.
Followed by Road Runners policy and how to fix your issue perhapsSpamhaus PBL query wrote:220.127.116.11/13 is listed on the Policy Block List (PBL)
Find out why here:Spamhaus CBL query wrote:IP Address 18.104.22.168 is currently listed in the CBL.
It was detected at 2009-01-09 16:00 GMT (+/- 30 minutes), approximately 8 hours ago.
Wiedmann pointed out the issue and your best course of action would have been to investigate further why perhaps GMail does not accept mail from your IP - in the Internet World what worked a minute ago may not work a minute later.Wiedmann wrote:GMail doesn't accept mails from your IP (dsl dial-up line).
Enter name server IP addresses separated by commas. If you leave this field blank, MecuryE will use the name servers defined in the Windows Network control panel.
routinet wrote:I'm not at all familiar with MercuryE, but it sounds like it uses its own mini-DNS client. Normally, an internet connection obtains the primary DNS server during DHCP, the same process through which it will receive an IP. The server list is sent along with other configuration items. I'm not sure how MercuryE would decide which server to use since each connection could have different lists.
In any case, you need to put a DNS server IP in the box provided, then it should work. This does not mean put the IP of hotmail.com in there...that's not a DNS server. Neither is localhost (127.0.0.1), unless you happen to run your own domain on that same box. Contact your ISP, or google for a publicly available DNS server to use.
IP Look Up wrote:ns_name_01: elrond.otago.ac.nz
You may have used your ISP as an SMTP relay in the lost previous Mercury Configuration and if you are doing that again then it should work the same as nothing of any significance has been change in the new version of XAMPP relating to Mercury.
IP Address Lookup
22.214.171.124 is not listed in the SBL
126.96.36.199 is listed in the PBL, in the following records:
188.8.131.52 is listed in the XBL, because it appears in:
In Protocol modules... Select active protocol modules have you tried swapping MercuryE to MercuryC for SMTP relay client when using that protocol?
AppName: mercury.exe AppVer: 184.108.40.206 ModName: mercuryc.dll
ModVer: 220.127.116.11 Offset: 00005042
Any clues C:\xampp\MercuryMail\LOGS in the log files?
T 20090109 231529 4967d9f9 Connection from 127.0.0.1
T 20090109 231529 4967d9f9 HELO max-023fe7af57c
T 20090109 231529 4967d9f9 MAIL FROM:<postmaster@localhost>
T 20090109 231529 4967d9f9 RCPT TO:<firstname.lastname@example.org>
T 20090109 231530 4967d9f9 DATA - 9 lines, 160 bytes.
T 20090109 231530 4967d9f9 QUIT
T 20090109 231530 4967d9f9 Connection closed with 127.0.0.1, 1 sec. elapsed.
T 20090109 232858 4967dda9 Connection from 127.0.0.1
T 20090109 232858 4967dda9 Connection closed with 127.0.0.1, 0 sec. elapsed.
T 20090109 233008 4967ddaa Connection from 127.0.0.1
T 20090109 233008 4967ddaa HELO max-023fe7af57c
T 20090109 233008 4967ddaa MAIL FROM:<email@example.com>
T 20090109 233008 4967ddaa RCPT TO:<firstname.lastname@example.org>
T 20090109 233008 4967ddaa DATA - 9 lines, 153 bytes.
T 20090109 233008 4967ddaa QUIT
T 20090109 233008 4967ddaa Connection closed with 127.0.0.1, 0 sec. elapsed.
T 20090109 233344 4967de67 Connection from 127.0.0.1
T 20090109 233344 4967de67 HELO max-023fe7af57c
T 20090109 233344 4967de67 MAIL FROM:<email@example.com>
T 20090109 233344 4967de67 RCPT TO:<firstname.lastname@example.org>
T 20090109 233344 4967de67 DATA - 9 lines, 154 bytes.
T 20090109 233344 4967de67 QUIT
T 20090109 233344 4967de67 Connection closed with 127.0.0.1, 0 sec. elapsed.
T 20090110 004459 4967ef43 Connection from 127.0.0.1
T 20090110 004459 4967ef43 HELO max-023fe7af57c
T 20090110 004459 4967ef43 MAIL FROM:<email@example.com>
T 20090110 004459 4967ef43 RCPT TO:<firstname.lastname@example.org>
T 20090110 004459 4967ef43 DATA - 9 lines, 157 bytes.
T 20090110 004459 4967ef43 QUIT
T 20090110 004459 4967ef43 Connection closed with 127.0.0.1, 0 sec. elapsed.
...you will get bounce message back that appears to indicate that your email to helocheck didn't work. It did. It's _supposed_ to work that way. The important piece to check is the error message you see.
Examine the error message, and you should see something like one of the following lines:
#5.1.1 SMTP; 550 Your HELO name for IP address 18.104.22.168 was "localhost.localdomain"
#5.1.1 SMTP; 550 Your HELO name for IP address 22.214.171.124 was "localhost"
#5.1.1 SMTP; 550 Your HELO name for IP address 126.96.36.199 was "smtp"
#5.1.1 SMTP; 550 Your HELO name for IP address 188.8.131.52 was "184.108.40.206"
#5.1.1 SMTP; 550 Your HELO name for IP address 220.127.116.11 was "[18.104.22.168]"
#5.1.1 SMTP; 550 Your HELO name for IP address 22.214.171.124 was "mail.example.com"
It should be the fully qualified domain name for your mail server or an IP address enclosed in square brackets.
In the above example, the first four examples are syntactically wrong by RFC2821. The last two are valid.
If it isn't like one of the last two examples, you have found the problem that needs to be fixed.
T 20090110 114739 49688985 HELO max-023fe7af57c
Consult your mail software documentation/configuration panels on how to set the "server name" to what it should be.
Thanks for posting back with the solution as it may help others with a similar issue - I am also pleased that your hard work and investigation payed off.The resolution consisted of:
* Designating the DNS server addresses (primary and alternative)in network connections/IP properties
* input my ISPs domain in Advanced TCP/IP settings/"DNS suffix for this connection" field.
Once I did this, the emails flowed as they should, appearing in only seconds after I executed my script.
Did you finally discover the answer to this?The only question that remains is, did this resolve what I believe to be the real cause of all this upset, namely an invalid HELO? I'm not sure on this point but, in anticipation of victory, I requested that my IP be delisted from CBL. I will find out soon enough if this isn't resolved.
When service staff are allowed to tinker unobserved and unquestioned as to what they are or have done then anything is possible, unfortunately.In the end, I still do not know how all this mess got started. Was it the cable guy messing with my Network connections? Was it simply the fact that I got lucky with XAMPP 1.68 and if so, how did that work so easily? And what about the fact that when I tried swapping MercuryE to MercuryC for SMTP relay client and Mecury mail would crash each time? Does this indicate a level of corruption on this install and would a reinstallation be the wise move?
Users browsing this forum: No registered users and 72 guests