exim error 535

[zEitEr]

Stop the mail program on the PC#2 and see whether or not requests from it stops in exim logs.

The listed suggestions are not relative I'd rather say. And Exim does not check how strong a password is. In case of a wrong password or permissions webmails would fail too.

 

[poNgz0r]

The affected PC must be having another program which tries to connect to SMTP service either without password or with a wrong one. It's not the server's side issue I'd rather say. Probably the PC#2 has malware or other hidden services.

1 last thing i finally found out. I noticed after better looking that he is using IPv6. And when i looked into my exim.variables.conf i saw disable_ipv6=true.
So i made a exim.variables.conf.custom and set: disable_ipv6=false

Can this make a difference?

 

[poNgz0r]

Stop the mail program on the PC#2 and see whether or not requests from it stops in exim logs.

The listed suggestions are not relative I'd rather say. And Exim does not check how strong a password is. In case of a wrong password or permissions webmails would fail too.

As soon as i stop the mail on PC2 the logs are gone, i also know for 100% sure its PC2 because the internal IP get logged too. I saw an option about IPv6 disabled, which was disabled and i saw in the log that he is using ipv6. So i set ipv6_disabled=false and i restarted everything. Let's hope it's gone now? Or doesn't ipv6 disabling matter?

 

[zEitEr]

If a mail program connects to the server it does not actually matter which IP version is used: IPv4 or IPv6, it does not make any difference for a password authentication.

Try to change a password to something simple (without using specials chars, probably your mail program does not support it).

Check logs in mail program for possible clues then.

If it does not help I have no more ideas.

 

[ikkeben]

Could it be some protocol errors to old whatever tls cipher and so on.
The chello smtp is (to) old and should changed to the newer ISP mailservers i presume don't know Ziggo maybe?

Protocols as tls version depends also from OS on PC itself with the settings allowed and yes or no updated.

PC has exact same connection not a other router / wifi also ... ?


LOG files for brute force / hack / limits we had one whose PC was hacked. (Then the limits reached same kind of error.)

Could be testing your public ip's, if IPv6 it could be different for only that PC, from that pc as not working email, is then mailserver webmail still possible?
Connection then you should check in log files if both ( port 443 webmail and the mailserver port are same ip meaning ip connection addres from that PC2)

Ziggo / UPC / chello full stack ipv6 or dslite.

You can test from pc and server and so on https://ipv6-test.com/ and https://en.internet.nl/

Also we have had a problem with one not allowing protocols while the connection was over a voip configured / protected server, so patched the ethernet cable to the old outside ip solved this, webmail was working only smtp protocol/port not allowed over that route. ( no logs on mailserver so not the case here)

 

[poNgz0r]

Could it be some protocol errors to old whatever tls cipher and so on.
The chello smtp is (to) old and should changed to the newer ISP mailservers i presume don't know Ziggo maybe?

Protocols as tls version depends also from OS on PC itself with the settings allowed and yes or no updated.

PC has exact same connection not a other router / wifi also ... ?


LOG files for brute force / hack / limits we had one whose PC was hacked. (Then the limits reached same kind of error.)

Could be testing your public ip's, if IPv6 it could be different for only that PC, from that pc as not working email, is then mailserver webmail still possible?
Connection then you should check in log files if both ( port 443 webmail and the mailserver port are same ip meaning ip connection addres from that PC2)

Ziggo / UPC / chello full stack ipv6 or dslite.

You can test from pc and server and so on https://ipv6-test.com/ and https://en.internet.nl/

Also we have had a problem with one not allowing protocols while the connection was over a voip configured / protected server, so patched the ethernet cable to the old outside ip solved this, webmail was working only smtp protocol/port not allowed over that route. ( no logs on mailserver so not the case here)

Sorry but i have no clue what you are trying to say... it's the same network, same host, same ISP. PC1 works, PC2 errors randomly but not if i start Outlook. If i start outlook and manually send/receive mails nothing shows up in the logs.

There must be definately something else running causing this

 

[poNgz0r]

This can finally be closed. Thunderbird and Outlook where correct but there was a built-in Windows client/ account which also uses that mail address and therefor it kept pulling mail even if the application was closed