Making batch settings changes to multiple post offices and mailboxes. yes/no?

Any way to set same options on all postoffices, and possibly all mailboxes in all postoffices? I'm hoping there's an autonimous way to accomplish this. If not, oh well, but I figured it'd be worth asking ;) For example, I want to be able to turn on greylisting for each mailbox within each postoffice...

I'll back this one up as well

They already use the/an editor... it's just a matter of adding one in a different spot.

Doh! We just upgraded to 3.6 Pro, and due to how well some of the features are working out for our customers, and the requests to granularize some of them (greylisting, for instance), we may just end up upgrading again.

Thanks for the reply.

Is there anyway to change this verbage? ------------------------------------------------------------------------ MailEnable: You have been added to the list (news@nobodysrealaddress.com). To unsubscribe to this list, please send a message back to the list with 'unsubscribe' as the subject. ---------...

They did. Read the link I posted again. They addressed that the message is incorrect. You're not getting MEStats unless you have Enterprise Edition.

It can only be used wtih Enterprise edition.

http://forum.mailenable.com/viewtopic.php?t=17538

I just heard back from Ian. They were able to reproduce the problem and will be addressing it in an upcoming release

I can currently repeat this in ME Pro 3.6. I'm PMing you details to reproduce.

Edited: Private Message Sent to Ian

I dont have any of the old conf files since I don't use AWSTATS to analyze them anymore. But I used this... http://forum.mailenable.com/viewtopic.php?t=5690&start=0&postdays=0&postorder=asc&highlight=awstats And this is available on the AWSTATS website now... http://awstats.sourceforge.net/docs/awst...

Yep. I had it setup before, but that was awhile ago. Just enable W3C compliant logging.

We hit some of that, too, and what we ended up doing for the time being was to change the Greylisting Sensitivity from High to Medium so that it allows the match to be made as long as the subnets match the class C mask.

After a few weeks we'll move on over to Class D again and see how things go.

Okay. I updated my config based on analysis of my logs since upgrading to 3.6 (12/31/2008). Initially SPAMCOP was most active, and only late last week did I move to ZEN, which took over as number one detector. Just this morning I've updated the list to match what my original post now states, and we'...

The only thing i can see missing from your "default" built-in tests are the URL Blacklist test. I have found the multi.surbl.org list to be quite effective. Cheers Doesn't ZEN take care of that? Spamhaus says that if using ZEN that I should *not* use XBL/DNSBL... so do I put ZEN in the "DNS Blackli...