Microsoft email servers are having hardware resource problems since a week.There might be an upgrade maintenance on their Boxes.

You may see below errors in logs:

Error: “452 Unable to accept message because the server is out of disk space.”

Error: “452 Out of memory”

So please don’t be surprised if you encounter them in your logs.They look like a local problem at a glance.

Keep it delivered! 🙂

Our fellows at Port25 have announced the new version of PowerMTA v4.5 and this is a major release!

Please see here the announcement :

Scheduled Delivery Control™
PowerMTA v4.5’s unique Scheduled Delivery Control™ allows for scheduled, time based delivery for campaigns and even for individual mailings, by dynamically controlling the processing of messages based on the sender’s predefined time windows. Pushing this intelligence from the CRM solution to PowerMTA is the only way to ensure true time schedule adherence, since email servers and other delivery solutions will generally attempt delivery as soon as messages are submitted. For very large, time sensitive mailings, it allows senders to create and submit the full campaign hours or even days in advance, to be released on a certain day and time in the future to help ensure maximum reach and results within a desired time frame. Numerous start and stop time windows can be defined for a single message.

Recipient engagement is now a critical component in maximizing delivery to large inbox providers, and only PowerMTA’s Scheduled Delivery Control™ allows senders to truly take advantage of time based engagement metrics in order to maximize both delivery rates and overall campaign results. Have PowerMTA send the message at the time that your data shows is the most likely time frame the recipient will open, read, and act on the message. Scheduled Delivery Control™ is also needed to ensure adherence to strict time based policies imposed by some of the international gateway providers, as well.

PowerMTA Enterprise Plus
PowerMTA Enterprise Plus includes new, advanced performance based algorithms and optimizations to help Email Service Providers and cloud relay providers realize maximum return on recent high end hardware investments. Modern hardware today is far superior to what was available only 2 years ago, and this combined with ever increasing workloads, has senders demanding more from their applications. The optimizations in PowerMTA Enterprise Plus maximize hardware ROI, making it the best email delivery solution on the market to handle the huge workloads of this very demanding group of senders.

There is also a new version named Enterprise PLUS.Probably it will be much more expensive than the others as it is specifically designed for High Volume ESPs.

I hope the new release will be available soon!

ReturnPath company has news for you.

Please see the changes on certification standarts below;

Port25 just launched PowerMTA v4.0r16.

Below are a few highlights of this build:

PowerMTA v4.0r16:

• bundles OpenSSL v1.0.1h given the very recent vulnerabilities reported in prior versions of OpenSSL;

• ability to disable certain cryptographic protocols used for STARTTLS on a per domain basis, allowing for both greater control and to workaround compatibility issues between OpenSSL 1.0.1g/h and some email security appliance solutions. The new per domain directives are “smtp-tls-allow-sslv2”, “smtp-tls-allow-sslv3” and “smtp-tls-allow-tlsv1” .

• expanded DKIM signing functionality with a new per domain directive “dkim-disallow-adding-headers”, to help minimize DKIM replay attacks when additional headers are added after signing.

New version of PowerMTA is available now.Below you will see the changes done since 4.0r14.

There are not any major changes but some small fixes.

2014-04-09: released build 4.0r15

– upgraded integrated OpenSSL library to 1.0.1g, given the recent
“heartbleed” vulnerability fix;

– added ‘–retry-recipients’ flag to the trace command, to request that
any recipients awaiting a retry be attempted again immediately;

– fixed bug that caused accept-invalid-recipients to override relaying
settings, leading to PowerMTA accepting invalid recipients for bouncing
when they should be rejected due to relaying restrictions;

– fixed web monitor responding with an incorrect Content-Type header in
some URLs when XML is requested;

– modified per-domain defaults to ignore the CHUNKING extension unless
explicitly enabled, given widespread issues with Exchange servers;

– fixed processor not accounting for angle brackets when processing JMRP
messages;

– improved performance of certain internal operations by reimplementing
them using lock-free objects;

– improved performance pausing queues;

– improved the error message displayed on the web monitor when trying to
add a new file to the configuration using the ‘Edit Configuration’ page;

– other enhancements in preparation for upcoming features;