Складчина Инсталятор PowerMTA 4.5 r11

Инсталятор PowerMTA 4.5 r11

​

Не знаете, что такое "PowerMTA" ? Тогда не ломайте голову... вам это не нужно. Для тех, кто знает и понимает ценность - супер-предложение ниже !

Инсталятор без ограничения на количество серверов и каких либо привязок к mac адресам. Получаете rpm-пакет с инструкцией для установки.

Для "не верующих" - версия ядра:

PowerMTA v4.5r11 (2017-09-18 18:01:51, 64-bit; tags/[email protected]).

​

Комплектация:

• PowerMTA 4.5 r11 (enterprise-plus) - Сам rpm-пакет для самостоятельной ручной установки на сервер. (тестировался на CentOS 6). Количество установок - без ограничений.
• Необходимые файлы для "активации".
• Видео-инструкция по установке.
• Видео-инструкция по работе с PowerMTA (работа с конфигурацией).

Стоимость (официальная) лицензии PMTA 4.5 для 1 сервера - около 10 тысяч долларов (плюс/минус...) Для Вас тут и сейчас - всего 1000р.

На вопросы "чем отличается, чем лучше" и т.п. читайте содержимое changelog ниже (оставил только описание начиная с версии 4.5 r6, которая была ранее самая стабильная):
​

2017-09-13: released build 4.5r11

- added experimental support for rolling up queues based on the receiving
mailer's IP addresses. This allows domains such as those served by
....mail.protection.outlook.com MXes to be rolled up into a set of queues,
depending on the IP address(es) involved. To enable this feature,
add the "rollup-by-ip" keyword after the rollup queue name, as in
"mx *.mail.protection.outlook.com omp.rollup rollup-by-ip". Please
email [email protected] with any feedback;
- added global directive "http-redirect-to-https", defaulted to false,
which, if enabled causes pmtahttpd to redirect any non-HTTPS requests
to their HTTPS equivalent;
- changed "pmta delete" command to write accounting records by default, and
added "--no-accounting" option to allow overriding it;
- modified DSN extended status codes due to SPF or iprev check rejection
as per RFC7372;
- modified configuration parsing to print a warning if an include file
opens a tag without closing it, to facilitate locating configuration
errors;
- added support for finding the correct license key to use among several
in the same file, based on MAC address, IP address, etc.;
- extended "pmta reload" command to also display warnings, if any, on
the console output whenever the configuration file has errors preventing
the reload;
- modified body-pattern-file support to unfold (in the style of RFC5322
FWS) captured groups, to avoid embedding line terminations in accounting
records;
- fixed body-pattern-file handler not matching lines terminated with CRLF;
- fixed issues creating default X.509 certificates when the hostname is
longer than 64 bytes;
- added automatic removal of previous "Authentication-Results" headers
claiming to have been issued by the local host when "check-...-inbound"
is enabled;
- added "--server" option to "pmta resolve", to have it send its queries to
a specific name server and thus facilitate resolving DNS issues;
- fixed "remove-header" directive also applying to "Authentication-Results"
header(s) added by PowerMTA for "check-...-inbound" directives;
- fixed some issues formatting "Authentication-Results" headers;
- fixed "iprev" authentication verifier incorrectly passing explanatory
messages in its "policy.iprev" property;

2017-06-06: released build 4.5r10

- added support for 'include' directive in <smtp-pattern-list>;
- added <domain>.discard-as-bounce, defaulted to 'false', to allow
having discarded emails noted as bounces in accounting files;
- added support for NULL MX record handling (RFC7505);
- added support for passing the private key to use for DKIM signing in
a header. To use this, enable the new <source>.process-x-dkim-key
directive and pass the key in PEM format in a "X-DKIM-Key" header.
Using this directive also requires specifying the key selector in
X-DKIM-Options, and enabling <source>.process-x-dkim-options;
- added support for custom bounce and FBL processing using regular
expression matching. The patterns are entered in separate files
and configured the new 'body-pattern-file' directive. Please see
the User's Guide for details;
- added experimental support for JSON output in the web monitor by using
"format=json" on the /status, /jobs, /jobDetail and /listQueue paths.
JSON support is still under development and is not expected to be
complete before PowerMTA v5.0. Please send any feedback to
[email protected];
- updated SPF checker, aligning it with RFC7208 and the corresponding
openspf tests;
- added "pmta check spf" command in substitution of "pmta check mfrom"
and deprecated "check mfrom", since Sender-ID is obsolete;
- also renamed <domain>.check-mfrom-outbound and the various
<source>.*-mfrom-* directives to <domain>.check-spf-outbound,
<source>check-spf-inbound, etc., deprecating the old names;
- deprecated SPF/mfrom "best guess" functionality, given that it goes
against the common interpretation of a published SPF record as an
authorization to use certain domain names in email;
- extended pmtakeytool "newcert" command to include a SubjectAltName
extension to new certificates, as currently required by some web
browsers;
- added <source>.check-spf-inbound-max-void-lookups, integer defaulted
to 2, to allow specifying the maximum number of "void" (empty and
NXDOMAIN) responses allowed before aborting SPF verification with
"permerror";
- added IPv6 <source ::1> entries equivalent to those already present
for 127.0.0.1 in the default configuration, so that the default behavior
is the same across IP versions;
- fixed DKIM authentication result not being "none" when the message
isn't signed;
- fixed bounces due to missing SMTPUTF8 support including SMTP responses
that had nothing to do with the failure;
- fixed email address maximum domain name length validation;
- modified Authentication-Results header format to combine all PowerMTA-
generated authentication results in a single header, in preparation
for ARC support;
- fixed queue size percentage calculation in web monitor's domain details
page;
- updated email authentication section of the User's Guide, removing
DomainKeys and better describing DKIM support;

2017-03-20: released build 4.5r9

- added <smtp-listener> tag as an alternative to the "smtp-listener"
directive, to allow overriding the various "smtp-server-tls-..."
directives (as "tls-..."). For example, to set a listener-specific TLS
certificate, you'd set "tls-certificate" inside <smtp-listener>;
- added support for more easily redirecting traffic to SparkPost (for
additional capacity, for example). To use, after setting things up in
SparkPost, define "<domain {sparkpost}>" with its "auth-password"
set to your SparkPost API key and set "queue-to {sparkpost}" in any
<domain>s that you wish to redirect. The SparkPost campaign name is
automatically set to the jobID, if any, and additional options can be
set with the new "sparkpost-sandbox" and "sparkpost-ip-pool" directives;
- added "--older-than" option to "pmta list" command, to specify that
only recipients older than a certain time interval be listed;
- added global <rewrite-list> tag to specify a list of email address
rewriting rules. The directives initially supported are "mail-from",
to rewrite only the email envelope originator, and "from-domain", to
rewrite the email originating domain in both the envelope and headers.
Also added <source> "rewrite-list" to specify the rewrite list, if any,
to use for a given source;
- added boolean <source> "add-x-virtual-mta-header", defaulted to "false",
to add an "X-Virtual-MTA" header with the Virtual MTA through which the
email is delivered, if no such header is yet present, to facilitate
tracking messages;
- added <source> "allow-chunking", defaulted to "true", to allow disabling
the CHUNKING (BDAT) extension. This is sometimes necessary to work
around buggy firewalls;
- added <domain> "ignore-dsn" directive, to instruct PowerMTA to ignore
the DSN SMTP extension;
- added reserved mailmerge variable "*priority" that can be defined to
set the priority for a recipient during submission;
- updated distributed OpenSSL to 1.0.2k, as the previous version is no
longer supported;
- greatly improved performance of certain OpenSSL operations on 64-bit
Windows;
- modified the default of <domain> "track-recipient-events" to "false",
to help conserve memory;
- modified the default DKIM signing algorithm to "rsa-sha256", which
is the current best practice;
- modified X.509 certificate generator in "pmtakeytool", used in new
web monitor installations, to create v3 certificates, as v1 certificates
are no longer recognized by Chrome and Safari under MacOS Sierra;
- fixed warning icon clobbering the displayed text in some contexts in
the web monitor;
- fixed submission APIs implicitly specifying a DSN NOTIFY=FAILURE setting
even for recipients for whom setNotify wasn't invoked;
- fixed <domain> "smtp-client-certificate", "smtp-tls-ca-file" and
"reuse-ssl-session" settings not being displayed;
- fixed files read by a few TLS configuration directives not being
recognized as configuration files for the purposes of updating the
configuration through the PMC or web monitor;
- fixed "retry-recipients-after" setting not being displayed;
- fixed bug handling (relatively rare) failures determining free space on
file systems;
- fixed "pmta show settings" not displaying string settings that have
an empty value;
- fixed race condition leading to crashes if the configuration was reloaded
while new messages were being received;
- removed support for DomainKeys (not DKIM!) signing and verification,
since this protocol is now obsolete. Its associated directives, such
as <domain> "dk-sign", are ignored with a warning if configured;

2016-12-20: released build 4.5r8

- extended "relay-address" directive to allow matching by regular
expression;
- added <source>.suppress-local-dsn, defaulted to "false", to have PowerMTA
not generate local DSNs for messages received from that source. This
directive also works for email addresses in suppression lists and some
other cases not covered by <domain>.deliver-local-dsn;
- deprecated <domain>.deliver-local-dsn in favor of
<source>.suppress-local-dsn;
- added bouncing of expired messages in paused queues, as that seems to be
the expected behavior;
- modified SMTP pattern matching to allow match-based actions even in the
presence of SMTP syntax errors;
- fixed <pattern-list> invoked through "call-to" not always matching
headers;
- fixed PowerMTA not attempting deliveries to A records when
"bounce-upon-no-mx" is specified with a time interval;
- improved DKIM-Signature header folding when signing, to help preempt
overly long lines;
- fixed missing filename validation in configuration parser;
- simplified license key processing, no longer supporting multiple keys for
the same product and version, as this was error prone;
- added requirement that perpetual ("expires: never") license keys also
contain a "supportExpires" field validating the right to upgrade. This
does NOT affect the ability to use the key indefinitely, but only the
ability to upgrade to newer builds;
- updated documentation;

2016-09-29: released build 4.5r7

- upgraded to OpenSSL 1.0.1u, to get the latest bug fixes;
- added *schedule mail merge variable, which can be used to specify
per-recipient delivery schedules;
- added <domain> dkim-query-method and second-dkim-query-method, to
optionally specify the value of the "q=" tag in DKIM signatures;
- added support for parsing the "q=" value from X-DKIM-Options;
- fixed formatting of non-ASCII characters in the output of "pmta"
and "pmtastats" commands on Unix;
- improved SSL session establishment performance, also adding support
for session reuse if supported by the remote system;
- fixed missing logging and added workaround for when IPv4 or IPv6
lookups are skipped because no IPv4/IPv6 connectivity is detected;
- fixed SPF checker not recognizing a responses that only contain CNAMEs
as indications that the sought record doesn't exist;
- other small improvements;
- updated documentation;

Это НЕ курс по рассылкам ! Это именно инсталятор + инструкция по установке и работе с конфиг-файлом. Гарантий инбокса никакая из версий PMTA не предоставляет если не понимаете, что это и зачем. Для понимающих и тех, кто "в теме" - это "клад" !

 

Я никуда не спешу )

 

Если вы за ГОД на рассылке этим скриптом не заработали несколько тысяч рублей, чтобы купить новую версию (PlexMail), то рекомендую вообще забыть про рассылки и не тратить деньги.

 

Вы меня с кем-то путаете т.к. мой скрипт ставил изначально ставил 4.0, потом 4.5 r1 и сейчас 4.5 r11 (последняя доступная) не было у меня версии 4.5 r6. Есть конечно "помогалы", которые что-то подобное ставили, но это был обман с подменой одного из файлов (чтобы вы видели, что это якобы r6). Если это так, то я вас "поздравляю"...

 

Приложите усилия - рекламируйте.

 

Потому, что есть указанное минимальное количество. Хотите быстрее - приложите тоже усилия рекламируя складчину. Не будет нужного количества - не будет складчины. Я никуда не спешу.