Hi all, I am trying to use DKIM on a mail domain that is actually hosted somewhere else. i added the domain example.com to a postoffice as a Smart Host I created dkim key and added that to the DNS of the domain. the issue now is that I can send to everybody, but no-one from that external domain can ...

we are at version 9.81 … can you also make a fix available for this version ?

how did you fix it, reinstall magic spam or did they released an update ?

any update on this ? we have the same problem with 9.81 !

we found that this line is entered in the NAME.sys file under postoffices Auth-Failure-Count: is there any way this can also be written in a separate file under the logging directory ? In this case we can easily detect what mailboxes are locked at any given moment and found potential hack attempts m...

is there any way we can see Who actually locked a mailbox ? Which IP, Which Login, What time ?
Thanks, this would be a big help

can you tell me how & where you change that option ?

Hi all, we are continiously having locked mailboxes due to intrusion attempts. Is there any quick way to see why a mailbox has been locked ? i know it's due to 3 failed login attemps, but can I easily find what IP actually locked the mailbox ? I looked through the pop / smtp / imap log files, but th...

I think so, we are still evaluating it, but it looks like its resolved, thank you

39423

did this thanks

good morning, it is email client independent, even with a normal telnet session on the server we are having the problem. We connect to the mailbox via telnet on the server. we delete a message, we quit, on that point the EML message is deleted, but the _index.xml file is not changing date and time. ...

We have a big issue with the latest version of mailenable 9.72 (our other mailserver version 9.60 does not have this issue) the _index.xml file is not recreated after a pop mailbox access. Situation... - the mailbox has 2 messages which are shown in the _index.xml file and in the directory inbox on ...

Blocking IP addresses on SMTP would be a good solution. The best way that I can think of to block these is to have something that will block failed connection attempts by IP address. ME would count each consecutive failed login attempt by the IP address rather than the username, so lets say users ar...

HELO *.* not sure, we have legitimate connection with that command ... why do you think so ?