I can confirm that setting "Use MIME Library" to 1 solved our problems here. I also tracked down to how it got set to zero on our server -- Back in 2015 when upgrading from version 8 to version 9 there was a problem with the then-new MIME library and on 19-November-2015 Ian had me disable it by sett...

I can confirm that we are seeing the same behavior here after upgrading from 10.27 to 10.29 - Remote images don't load. - Whitelisting has no effect, images still won't load. - clicking on the text brings up a "Download Remote Image" dialog box, but clicking "Ok" does not cause the image to be downl...

DKIM is used to sign the contents of the message to insure that the message body and key headers haven't changed since it was composed. Something to remember is while the KEY may be valid, it may not be the CORRECT key for the message. Think of it this way - in your pocket you have a ring of keys. E...

Yes, you can block those connections by going into port settings and checking the "Requires connections to authenticate before sending mail" box. Adding a privileged IP bypasses the authentication, so localhost won't be a problem. I would also suggest adding ::1 in addition to 127.0.0.1 if you have ...

not a command-line tool, but a worst case scenario option would be to stop the mailenable services, edit the auth.tab file to change the passwords, then restart the mailenable services.

I migrated and upgraded one of my Mailenable Professional servers to from version 9.x version 10.1 last week, and users are screaming. Some of the issues I have been able to resolve, such as the change in the way that Version 10 inserts the IP address of the webmail user. The new version puts it in ...

I actually forgot about that filter - I don't use it and do all of my DKIM checking in SpamAssassin. Filtering is run on mail retrieved using POP Retrieval, so that filter should work just fine for your needs. SPF, however, is based upon the IP address of the delivering mail server. Mailenable may n...

Since nobody has replied, for now I have set up a scheduled task to recycle the MTA service daily in hopes that it is a memory or resource leak causing the problem and will wait for the next version. If you are running with SpamAssassin integration you might want to check your own setups to make sur...

Incoming email messages, whether they are sent from you via your mail client or from outside parties and addressed to you, are all received via SMTP. That is where you configure SPF checking. DKIM is inserted by Mailenable if you have gone to through the additional steps to configure it, but it is n...

After upgrading to 9.74 a week or so ago I have noticed filtering such as SpamAssassin integration failing after a few days. I run a separate spamassassin server under Ubuntu. I monitor the Spamassassin server with nagios, and I can run spamc from my workstation to query it and know that it was up a...

Also, don't forget to create your policy record in DNS. At the very least you should have _domainkey TXT t=y; o=~ t=y means testing o=~ means that SOME messages are signed Once you are sure that things are working, remove the t=y; and if ALL of the email for that domain flows through mailenable and ...

Yes, since DKIM is on a per-domain basis it will need to be done for each of the domains.

I prefer to set up SPF, DKIM, and AutoDiscover records all at the same time since each of them require modifying the domain's DNS.

That explains it -- Window's DNS can't handle TXT records longer than 255 bytes. Regenerate your key as 1024 bits, and the shorter key will fix within your DNS constraints.

You don't have the full key in DNS. You can check it from the command prompt like this: C:\>nslookup -type=txt wws._domainkey.williamswebsolutions.net The response you are getting is looking like this: Non-authoritative answer: wws._domainkey.williamswebsolutions.net text = "v=DKIM1; p=MIIBIjANBgkqh...

Has anybody else noticed spammers circumventing Mailenable's anti-spam? We are running Mailenable Pro version 9, with SpamAssassin integration. We've been getting the occasional messages from addresses like FOX|NEWS@whatever, and even though SpamAssassin correctly sees them as spam, they are still b...