After I read your email I didn't believe Avast would effect Multipop, but I turned off two flags: 1. Scan.... Pop3 and imap4 2. Scan... SMTP Then force Multipop to pull mail. &nbs...
Scott
Posts made by Scott
-
Multipop outbound connection IP Address (127.0.0.1)
-
Multipop outbound connection IP Address (127.0.0.1)
Avast was checked before starting this ticket and yes the setting(s) remain the same. Please note, our SMTP is working correctly because it is bound to our internal ip address of 192.168.2...
-
Multipop outbound connection IP Address (127.0.0.1)
"I will see if I can break this on my test machine and then run some further tests to see if there is another way to address this problem." I would believe the larger question should be, where in ...
-
Multipop outbound connection IP Address (127.0.0.1)
Currently the system will not bind to any physical or virtual IP address unlike SMTP (In/out) (as an example) which works correctly. As you know there isnt a parameter(s) to configure binding...
-
Multipop outbound connection IP Address (127.0.0.1)
Ran the command: netsh interface ip delete destinationcache Restarted Mdaemon and found the same problem (see below) Tue 2023-10-10 12:53:50.921: [00508048] * Connection established 127.0.0...
-
Multipop outbound connection IP Address (127.0.0.1)
I see version 23.5 was just posted, will this update correct the problem I reported?
-
Multipop outbound connection IP Address (127.0.0.1)
I see version 23.5 was just posted, will this update correct the problem I reported?
-
Multipop outbound connection IP Address (127.0.0.1)
Very good. Thank you for your help. Will I be updated when both fixes are available?
-
Multipop outbound connection IP Address (127.0.0.1)
My system is setup to only accept connections to our virtual ip address (192.168.21.251) for the mail server. The VM it resides has a network card ip of 192.168.21.179. After tracing traffic ...
-
Multipop outbound connection IP Address (127.0.0.1)
Any update? So, where in the system can we bind our Multipop connection?
-
Multipop outbound connection IP Address (127.0.0.1)
Multipop outbound IP address connection uses 127.0.0.1 instead of the assigned bound ip address under IMAP & POP3 We've had a similar issue with SMTP (out) connection (see previous post ...
-
Antivirus (could not connect to the server)
Arron, upgrading solved the issue. Thank you.
-
Antivirus (could not connect to the server)
We have connectivity to either http or https. However, when we drill down to http://files.mdaemon.com/antivirus/ctav/updates/ it prompts for a username and password. Ping Test Pinging altnt...
-
Antivirus (could not connect to the server)
Log file shows only a message (see below) #Update session at 09:25:21 on 2023-08-07Date Time Action Status Object2023-08-07 09:25:21 -- SPUPDATER START -- 2023-08-07 09:25:21 Version 21.5.1 ...
-
SMTP (out) communication
Update. I've identified what was causing the problems with the "connection established" not returning the correct network card ip address and the systems inability to verify the "SSL Certificate" ...
-
SMTP (out) communication
So, it appears from your last message, there's nothing further we can check, or parameters to change to effect this problem -- which is unfortunate. Thank you for your time on this issue.
-
SMTP (out) communication
"can you disable MTA-STS and RequireTLS?" Both had previously been disabled. I'll certainly pull together today's SMTP (out) log file and email it out ASAP.
-
SMTP (out) communication
"The latest screen shot, which I think is from the firewall, shows the source IP as 192.168.21.251, so does that mean its working? What is reported by the firewall is certainly a step in the right...
-
SMTP (out) communication
Simply stated, when Mdaemon smtp (out) log shows: Connection established 127.0.0.1:39904 --> 142.251.111.26:25 Our firewall display the bound virtual IP address given to Mdaemon in a clu...