Hello,
OK - all the Regedit did was turn off the pickup event.
We need the MTA running.
Search found 48 matches
- Tue Nov 07, 2023 5:50 pm
- Forum: MailEnable Professional Edition
- Topic: MTADeliverMessage
- Replies: 3
- Views: 3152
- Mon Oct 30, 2023 3:06 pm
- Forum: MailEnable Professional Edition
- Topic: MTADeliverMessage
- Replies: 3
- Views: 3152
Re: MTADeliverMessage
Thank you for your reply.
And your 20+ years as Admin!
And your 20+ years as Admin!
- Sat Oct 21, 2023 10:21 pm
- Forum: MailEnable Professional Edition
- Topic: MTADeliverMessage
- Replies: 3
- Views: 3152
MTADeliverMessage
Hello all, "MTADeliverMessage:: COM Pickup Event enabled but no COM class specified" We are getting the following in our MTA Debug logs: 10/21/23 18:09:59 Processing file DD9FB3C842D649FD941B16C7ED428325.MAI from queue SF 10/21/23 18:09:59 MTADeliverMessage::Pre Pickup Event executing: C:\Program Fi...
- Thu Aug 10, 2023 2:57 am
- Forum: MailEnable Enterprise Edition
- Topic: Licence limitations
- Replies: 6
- Views: 8593
Re: Licence limitations
Thanks - yes that is what we did and it worked perfectly - thank you.
- Tue Aug 01, 2023 9:09 pm
- Forum: MailEnable Enterprise Edition
- Topic: Licence limitations
- Replies: 6
- Views: 8593
Re: Licence limitations
I know this thread is from long ago. But reading here I am hoping that this is NOT still true: "your best way forward is to remove MailEnable completely from the new server" We have installed the same version of ME for our migration - we saw that it was successfully set up as trial license. We did t...
- Mon Feb 27, 2017 5:42 pm
- Forum: MailEnable Professional Edition
- Topic: Serious iPhone SMTP Issues - cannot send
- Replies: 3
- Views: 16956
Re: Serious iPhone SMTP Issues - cannot send
Thanks for the reply. I should have come back in and posted that we had resolved this. We were a bit too aggressive in blocking at the HELO level (SMTP | Properties | Security tab} and blocked what appeared to be 100% spam coming from: [*.*.*.*] It turns out that some smartphones use the bracketed I...
- Wed Feb 22, 2017 10:22 pm
- Forum: MailEnable Enterprise Edition
- Topic: Fighting Hackers
- Replies: 19
- Views: 53352
Re: Fighting Hackers
Hey siteffect - There is another thread about this going on - title is: EHLO Blocking - HELO *.* I did not make this statement to start a conversation about "EHLO Blocking - HELO *.*" - I was simply telling you to do a search for this title here in the forum to FIND the other thread where that conve...
- Tue Feb 21, 2017 4:27 am
- Forum: MailEnable Enterprise Edition
- Topic: Fighting Hackers
- Replies: 19
- Views: 53352
Re: Fighting Hackers
Hey siteffect -
There is another thread about this going on - title is:
EHLO Blocking - HELO *.*
Hope this helps -
There is another thread about this going on - title is:
EHLO Blocking - HELO *.*
Hope this helps -
- Mon Feb 13, 2017 11:52 pm
- Forum: MailEnable Enterprise Edition
- Topic: Fighting Hackers
- Replies: 19
- Views: 53352
Re: Fighting Hackers
Why not just block YLMF-PC at the HELO block?
SMTP Properties
Security TAB
Configure Blocks (at the bottom).
No need to block IP addresses if the HELO is blocked.
SMTP Properties
Security TAB
Configure Blocks (at the bottom).
No need to block IP addresses if the HELO is blocked.
- Fri Feb 10, 2017 11:19 pm
- Forum: MailEnable Professional Edition
- Topic: EHLO Blocking - HELO *.*
- Replies: 4
- Views: 11493
Re: EHLO Blocking - HELO *.*
Update on this thread: it would appear that smartphones are sending their HELO in this format EHLO+[10.0.0.121] The Android that I tested used the above. I assume iPhone do the same. The IP is the one assigned to the device by the WiFi connection from the DHCP on the internal network. Definitely rec...
- Fri Feb 10, 2017 11:17 pm
- Forum: Suggestions
- Topic: EHLO blocking - extension
- Replies: 15
- Views: 60809
Re: EHLO blocking - extension
Yes it would appear that smartphones are sending their HELO in this format
EHLO+[10.0.0.121]
The Android that I tested used the above.
The IP is the one assigned to the device by the WiFi connection from the DHCP on the internal network.
Definitely remove the [*.*.*.*] from the block list.
EHLO+[10.0.0.121]
The Android that I tested used the above.
The IP is the one assigned to the device by the WiFi connection from the DHCP on the internal network.
Definitely remove the [*.*.*.*] from the block list.
- Wed Feb 01, 2017 8:55 pm
- Forum: Suggestions
- Topic: Abuse Detection and Prevention
- Replies: 0
- Views: 15826
Abuse Detection and Prevention
I read somewhere recently that we should NOT have BOTH Connection Dropping and Abuse Detection and Prevention "on" at the same time.
If this is true then my suggestion is to have a text warning next to both these options in the backend to alert people.
If this is true then my suggestion is to have a text warning next to both these options in the backend to alert people.
- Wed Feb 01, 2017 8:53 pm
- Forum: MailEnable Enterprise Edition
- Topic: Fighting Hackers
- Replies: 19
- Views: 53352
Re: Fighting Hackers
I read somewhere recently that you should NOT have BOTH Connection Dropping and Abuse Detection and Prevention on at the same time. Perhaps someone from ME can confirm this? When I read this I wondered why ME does not have a text warning next to both these options in the backend to alert people. We ...
- Wed Feb 01, 2017 5:49 pm
- Forum: Suggestions
- Topic: EHLO blocking - extension
- Replies: 15
- Views: 60809
Re: EHLO blocking - extension
Hello Brett, Yes the function is working in 9.54. I have found a minor bug and have already reported it. Basically if you have *.br blocked and the HELO name is static.bringit.br it doesn't get stopped. Apparently the code checks the first .br finds .bringit and then lets it pass. The function in SM...
- Wed Feb 01, 2017 7:38 am
- Forum: MailEnable Professional Edition
- Topic: EHLO Blocking - HELO *.*
- Replies: 4
- Views: 11493
Re: EHLO Blocking - HELO *.*
Hello again, Yes we see a lot of email come in with this bracket format - [192.168.1.100] the IP addresses are all different of course. Here are a few examples from the log files: EHLO EHLO+[197.157.18.98] EHLO EHLO+[185.99.32.109] EHLO EHLO+[10.75.60.50] After careful review of these messages it ap...