Hopefully this post sheds some light...
http://forum.mailenable.com/viewtopic.p ... ght=#37982

That registry setting is only really suitable if ME doesn't accept direct connections from other external servers (such as Yahoo).

Martin

Hi wisp, If you've used the configuration I posted in the other thread linked above, then ALL clients/servers trying to send mail to your server will either need to authenticate or be allowed to relay (based on their IP address for example) before your server will accept the message. If you've added...

Yes, add your 192.168.0.6 address to the privileged IP list to allow your spam filtering software to send messages to ME without requiring authentication. You can remove the 127.0.0.1 IP address from the list if you don't have any other applications on the same server as ME that need to send mail vi...

You certainly can do this as we have a similar setup and it works very well.

Here's a post made a few weeks ago with more info, hope it helps...
http://forum.mailenable.com/viewtopic.p ... ght=#36387

Hi Andy, I believe you're entitled to all minor upgrades so yes, you can just install over the top of your existing v1.1 installation. We've never encountered any problems doing this. Personally I usually wait a week or so after a new release (except for security patches naturally) to see if anybody...

Have you applied the latest hotfix that fixes a possible exploit in the POP3 service?

http://www.mailenable.com/hotfix

Glad it worked, it's a great feature, but you're right about the documentation - how about a KB article ME guys?

This is a bit of a stab in the dark, but could this be your problem....?

http://www.mailenable.com/kb/Content/Ar ... D=me020421

If you configure authenticated relay on a standard install of ME Enterprise, it will still allow anyone to send messages to local recipients without authentication - standard practice for a mail server. However, if you want ALL senders (regardless of whether they're sending to a local address or rel...

That's strange, we have a similar set-up to you (we're also running ME Ent 1.2 with the "Ignore Local Addresses" registry entry set to 1), and it works perfectly for us. What does the SMTP debug log say when your scripts attempt to send mail? I've just tested it using telnet from a server within our...

Hi all, Has anyone managed to find a way to install just the MMC client tools on a workstation to allow remote management of ME? Can something be copied from a server with ME installed rather than having to install the full mail server on the workstation too? Failing that, is the client-only install...

I am assuming here that all of your users are on the same class of IPs. If not, you should be able to set up a priviliged IP for the spam box and turn on smtp authentication? The trouble there is, when you do have remote users, your ME server has to be exposed to the Internet where it will also acc...

We had a similar situation where we have an internet-facing gatway, and only wanted to accept incoming mail from the IP of this gateway, plus any internal users that authenticated. Basically, we wanted to stop ME accepting incoming mail that was addresses to local recipients, UNLESS the server it wa...

We experienced similar issues some time ago which I'm fairly sure related to permissions. As I understand it, ME webmail uses the _index.xml files in a user's mailbox to retrieve quota info, list messages and for the new messages pop-up. I'm guessing either ME doesn't have sufficient permissions to ...

That's probably a fair comment, but maybe my post should have been clearer. We have SQL Server on it's own machine, and did some testing with ME using SQL vs ME using TAB files. We found that SQL Server would consume resources far faster when ME was using it as it's backend. From SQL Server's own da...