550 5.7.1 Mail from 188.240.44.77 blocked using Trend Micro RBL+. Please see http://www.mail-abuse.com/cgi-bin/lookup?ip_address=188.240.44.77Fine, I understand, and I do remember I tried to test my outgoing SMTP connections with another email address hosted on anonymousdomain.com. At the same time I noticed that the Google servers were delivering just fine my mails, without any issues.
During this time I faced the need to switch between various proxy switches on my computers and laptops. Hotels with specific proxies, public spaces without proxy, work network specific settings, etc.
At the end it became quite annoying to switch proxies between sessions, etc., getting disconnected from work VPNs, hanging between proxies while roaming between my work desk and public places.
And all this must come to an end... hence, I wrote a small Proxy switcher, which simply can to one of the following settings:
As of now I tested the proxy on my Windows 7 with DOT NET 4; further on I shall continue testing this application also on other platforms.
The application can be found at http://static.sorescu.eu/Applications/WebProxySwitcher-1203280028/WebProxySwitcher.exe.
I took a look in the logs of my ad-hoc SMTP server (running on the main domain) sorescu.eu and I noticed a series of denied authentications.
I did not understand what happened, but I saw the user and the password list encoded in Base64. After I collected all the encoded values, I was curious which credentials were tested. I shall present below the application that I wrote to help me in decoding them, and, the list of passwords used to log in.
Java Base64 decoder code:
Worthy saying, before listing the password list:
Few days ago a colleague of mine got an almost-impossible task: fix a bug in a Java application that had to print an HTML document built ad-hoc, and the customer was complaining that when printing, in place of printing, it was throwing various JavaScript errors.
The problem was that once the Java application was loading the JExplorer component, the application was running the code (I don't remember by heart the code, but it is close to reality).
And, the situation to be worsened, the bug was appearing only sometimes, on some machines, at some times, being hard to identify and understand a pattern.
After two hours of drinking coffee (vital brain combustion ingredient, obviously) and lots of endless investigations, just like an inspiration, I remembered that the JExplorer publishes an API through which I can tell it to save the document.
At the end, the bug was fixed with a very simple line of code.
I created a new subdomain named My.Sorescu.Eu - as the central place for applications and tools that should help you stay active, competitive, and in shape in a more and more competitive world.
Log in, check, or just come back in few weeks to see the progress.