Nethserver 7.4 with Postfix 2.10.1 without smtputf8_enable


(Agustinus Mulyawan) #1


Kindly advise if any postfix version upgrade to 3.1?
If no postfix version upgrade to 3.1, is there any issue with rebuild postfix with smtputf8_enable?
Any tips to rebuild to make support in SMTP-based content filters (Amavisd), LMTP servers (Dovecot), and down-stream SMTP servers?

(Davide Principi) #2

No ATM. The Postfix package comes from CentOS: we will upgrade to Postfix 3 when CentOS (RHEL) releases it.

Yes! NethServer does not rebuild upstream packages!

Please refer to upstream documentation for that.

We avoid recompiling upstream packages because it is a big effort to test and maintain them.

Is SMTPUTF8 widely spread? Or is it still a niche? As you see it requires the upgrade of many components: is it worth the effort today? Could you explain why is it needed?

(Agustinus Mulyawan) #3

Dear Davide,

Thanks for quick feedback.
Nethserver mainly used for email server.
To avoid email consider as SPAM, I enable SPF, DMARC and DKIM signing.
No issue for SPF and DMARC on email test, but fail on DKIM: “wrong body hash: expected” for email with content-type: ‘multipart/mixed’ or ‘multipart/alternative’ which sent from outlook.
Email sent by web mail client no issue with DKIM.

Below is the configuration in nethserver:

filippo enable dkim

$enable_dkim_verification = 1;
$enable_dkim_signing = 1;
$log_level = 5;
dkim_key(‘domain’, ‘dkim’, ‘/etc/pki/tls/private/domain.pem’);
@dkim_signature_options_bysender_maps = ( { ‘.’ => { ttl => 21243600, c => ‘relaxed/relaxed’ } } );

I tried to use DKIM canonicalization ‘relaxed/simple’ also same fail result “wrong body hash: expected”.

Per googling the issue related with “mime 8 bit encoding converted to mime 7 bit encoding” as result hash body check fail, since postfix not support smtp with utf8 (smtputf8_enable).

(Davide Principi) #4

DKIM support is available out of the box with the Email 2 (beta) module. More info here

Remove old custom-templates.