Yes it seems like something is blocking me locally. Still, I even tried switching the firewall off (with Internet disconnected) and still wasnt able to connect to a mail account. Funny thing is tough, some bot tried earlier and it looks like it already had more success than me -.-
Connection from 200.137.194.19eight
* User staff, username or password failure (1 of 2)
1 sec. elapsed, connection closed
Connection from 200.137.194.19eight
* User administrator, username or password failure (1 of 2)
1 sec. elapsed, connection closed
Connection from 200.137.194.19eight
* User sales, username or password failure (1 of 2)
1 sec. elapsed, connection closed
Connection from 200.137.194.19eight
* User sales, username or password failure (1 of 2)
0 sec. elapsed, connection closed
Connection from 200.137.194.19eight
* User recruit, username or password failure (1 of 2)
0 sec. elapsed, connection closed
Connection from 200.137.194.19eight
* User alias, username or password failure (1 of 2)
0 sec. elapsed, connection closed
Connection from 200.137.194.19eight
* User office, username or password failure (1 of 2)
0 sec. elapsed, connection closed
Connection from 200.137.194.19eight
* User samba, username or password failure (1 of 2)
0 sec. elapsed, connection closed
Connection from 200.137.194.19eight
User test, (2) 14 messages, 27197 bytes (<- thats actually less funny. Can anyone tell me if the mails have been transmitted successfully? 0 seconds look too short for that. and yes, I changed the name of the test account... stupid idea.)
0 sec. elapsed, connection closed
...and a few more
Ill try to figure out whats blocking my login attempts locally.
[quote user="dilberts_left_nut"]
Your mail server should be assigned a static ip (either manually or via DHCP Static Lease) otherwise, if the assigned IP changes your port 25 forward will be pointing at a vacuum or the wrong machine.
What response do you get to:
telnet 127.0.0.1 25
?
[/quote]
I do have a fix local IP, still, I closed Port 110 after this incident. CMD says that telnet is not recognized. I think that's a Vista/Win7 thing where this command is blocked. I just cant remember right now where the settings for this are hidden. Maybe I should wait till I reinstall WinXP where I exactly know how what works.
Thanks to both of you for your help so far.