Am 09.12.2011 um 23:06 schrieb Sean P. DeNigris:

Issue 5078: SMTPClient (wrongly) uses local address
http://code.google.com/p/pharo/issues/detail?id=5078

I have no idea how to fix it. I cheated in my image with "(PipeableOSProcess
waitForCommand: 'curl whatismyip.org') output" to get it to work
temporarily.

I'm sure this is not a bug. Using your local address ist the only thing you can do. The entry is only put in the mail header/envelope and usually has no effect at all. It wouldn't be to clever if a mail server would take the IP address from your produced mail header instead of the IP packet header. :) The later is checked indeed. In your copied snippet

you can see that 10.0.0.5 is considered as the one you told the server but it treats you to be ool-182daabe.dyn.optonline.net which is 24.45.170.190. So your router did network translate your IP to a real IP and the mail server saw it in the connect from this IP address. Exactly as it is supposed to be.

Analyzing your problem I focus on the "dyn" word in it. That means to me you are probably using a dialup or similar line from home. These are always considered to be not trusted. So If you try to use the mail server to send an email to someone that is not a user on this mail server you will need relaying permission which means you need to log in somehow to the mail server. In nearly every other case a mail server will reject your trial of sending messages. Another reason why it probably doesn't work is because your dynamically assigned IP address is blacklisted. I checked the mentioned IP address over

and at least spamhaus has this IP address listed which is a very prominent RBL service. The addresses are added and removed automatically so this could also be a reason why it worked some day and now it doesn't.

If you are using SMTP services you need a machine that is trusted or you need to use SMTP Auth to make the mail server accept your requests. Of course I do not know what is the problem exactly because that would need further investigation.