Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

It's a common mistake to think that a sender should insert a Return-Path header.

Receivers use the envelope sender in MAIL FROM command to return asynchronous/remote bounces. The Return-Path header is inserted by receivers to preserve the envelope sender when it is delivered via other means than SMTP. See section 4.4 in RFC 5321, the "SMTP standard":

   When the delivery SMTP server makes the "final delivery" of a
   message, it inserts a return-path line at the beginning of the mail
   data.  This use of return-path is required; mail systems MUST support
   it.  The return-path line preserves the information in the <reverse-
   path> from the MAIL command.  Here, final delivery means the message
   has left the SMTP environment.  Normally, this would mean it had been
   delivered to the destination user or an associated mail drop, but in
   some cases it may be further processed and transmitted by another
   mail system.

Thanks Marteen!!

You should not use more IPs than necessary. A volume less than 10K per day per IP is too low. A volume of 1M per day per IP is on the upper end.
For a mailing list of 1M I would use a pool of 4 IPs. If you are an ESP I would create pools for groups of customers. And reserve the remaining IPs for customers that prefer dedicated IPs.
To warmup the reputation on the IPs you need to start with low volume, or split the volume using cold-virtual-mta and forward the remainder to another platform.
Make sure all prerequisites are in place: authentication, feedback loops, reputation monitoring, ...

Maarten
Postmastery

Hi !

I will set up a new /24 and domain

What's the recomended configuration for this?

Warm-up , pool , vmtas, etc

Can i to set up a virtual.mta with 10 ips?? more o less?

Very Thanks!!

OK

Thanks!!!

As long as you dont change the domain itself,changing the subdomain on returnpath wont change anything in terms of reputation.

Hi, what is the best configuration to header return-path

At this moment we use the same for all ips of X.X.X.X/24

ie: Return-Path : <name@subdomain.domain.com>

It's fine??

Or we should use <name@subdomain1.domain.com> ( X.X.X.1)
<name@subdomain2.domain.com> ( X.X.X.2)
<name@subdomainN.domain.com> ( X.X.X.N)


where  subdomainN.domain.com is the RNDS for the ip X.X.X.N

Thanks!!

HI, can you explain this??

If you are using PowerMTA 4.5r6 or later then you can also use mx-rollup-list feature to consolidate Microsoft related domains into one queue. This will improve resource utilization. For example, Microsoft EU and APAC :

# Microsoft
mx eur.olc.protection.outlook.com outlook-eur.rollup
mx apc.olc.protection.outlook.com outlook-apc.rollup

whereis hotmail.com

Thanks!!

We only use http://link, we don't use mailto:  for all domains (hotmail, gmail, yahoo, and other domains)

I'ts rigth?

In this BLOG post we discuss the implementation of a List-Unsubscribe header and share a use-case. For PMTA users we present an interesting add-on to streamline MAILTO unsubscribe requests.
https://www.postmastery.com/list-unsubscribe-header-critical-for-sustained-email-delivery/