Aide DKIM

[dodo31]

Bonjour,

Je fait appel a vous car ça fait 3 jours que je galère...

J'ai un nas syno avec mon smtp qui fonctionne bien.

Je suis chez ovh

Mais malgrer les tuto sur internet je n'arrive pas a configurer DKIM.

J'ai générer une cle avec synlogie dans serveurmail que j'ai mi dans les dns de mon domaine, mais mais mails ne sont toujours pas signer.

Dans serveurmail dans le syno :

xxx dans le sélecteur

et ma cle public générer par syno.

DNS chez ovh : 

xxx._domainkey.mondomaine.fr

v=DKIM1; k=rsa; t=s; p=MIGfMA0G .......

Je ne comprend pas ? faut t'il une clé priver ? si oui je la rentre ou ?

Merci de m'expliquer car je suis perdu....

Merci

 

[Fenrir]

il y a 12 minutes, dodo31 a dit :

faut t'il une clé priver ?

oui

il y a 12 minutes, dodo31 a dit :

si oui je la rentre ou ?

dans la conf de ton agent dkim, si c'est un syno il suffit normalement de suivre le guide : https://www.synology.com/fr-fr/knowledgebase/DSM/help/MailServer/mailserver_spam

https://www.mail-tester.com/spf-dkim-check

[dodo31]

Ok lerci

 

jai suivi de guide ; Pour activer DKIM :

jai mi dans le préfixe xxx

jai genrerer ma clé public en dessous, 

jai rentrer mon préfixe chez ovh : xxx._domainkey.mondomaine.fr

et le champ : comme j'ai cité plus haut dans mon message.

mais dans tous cela où est la clé privé ?

 0

 

•  

[Fenrir]

Je viens de tester vite fait (installation de dns server+mailserver+mailstation, création de la zone dns, conf de mail server, création de l'enregistrement TXT pour la dkim et envoi d'un mail), ça fonctionne :

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=XXXXXXX.fr; s=XXXX; t=1478903041; bh=lcj/Sl5qKl6K6zwFUwb7Flgnngl892pW574kmS1hrS0=; h=Date:From:To:Subject; b=QwH7kNW9w73JAx19QytVPCDfhIGmv9gVCkFLnwMdeWroKlAFbdFOhomb/G3AJhd0j
	 goVkkAkNyeFeRHu2zSAYY5v+GEnT2OyKM1GztORePs6SQ64QXOFocBuEKNMFwUwDr3
	 aN5i1apg0cElDuJPlsXAPQCEs8AasZgA156WKvvE=

Quel est ton problème ?

[dodo31]

Mes mail de sont pas signer, chez gmail par exemple. 

 

Peux tu m'expliquer en détail ce que tu as fais stp?

J'ai pas installer DNS server sur le syno, tu le configure comment ?

SI tu peux tout me détailler stp :)

 

[Fenrir]

il y a 21 minutes, dodo31 a dit :

Mes mail de sont pas signer, chez gmail par exemple. 

Envoi moi le source d'un mail en MP, avec ton vrai nom de domaine.

il y a 20 minutes, dodo31 a dit :

J'ai pas installer DNS server sur le syno, tu le configure comment ?

j'ai installé le dns pour ne pas avoir à créer/modifier un vrai nom de domaine.

[Fenrir]

Un nas n'est pas adapté à ce que tu essayes de faire, tu vas souvent être marqué spam et avec un volumétrie telle qu'indiquée, ton FAI risque te d'envoyer un avertissement.

Pour ton usage il serait plus propre de relayer les mails via un serveur hébergé (un vps à 3€ sera suffisant) ou via ton hébergeur (ils ont surement des offres).

Si tu pars sur un VPS, tu pourras affiner les règles de filtrage pour éviter les relais ouvert en configurant quelques lignes dans le fichier /etc/postfix/main.cf.

Ça ne t’empêchera pas d'utiliser ton nas en secours si besoin.

 

[Fenrir]

Pour la conf du postfix, à priori (mais pas testé), il faut modifier le fichier /volume1/@appstore/MailServer/etc/template/main.template

[dodo31]

Voici ce que j'ai dans ce fichier:

 

# Global Postfix configuration file. This file lists only a subset
# of all parameters. For the syntax, and for a complete parameter
# list, see the postconf(5) manual page (command: "man 5 postconf").
#
# For common configuration examples, see BASIC_CONFIGURATION_README
# and STANDARD_CONFIGURATION_README. To find these documents, use
# the command "postconf html_directory readme_directory", or go to
# http://www.postfix.org/.
#
# For best results, change no more than 2-3 parameters at a time,
# and test if Postfix still works after every change.

# SOFT BOUNCE
#
# The soft_bounce parameter provides a limited safety net for
# testing.  When soft_bounce is enabled, mail will remain queued that
# would otherwise bounce. This parameter disables locally-generated
# bounces, and prevents the SMTP server from rejecting mail permanently
# (by changing 5xx replies into 4xx replies). However, soft_bounce
# is no cure for address rewriting mistakes or mail routing mistakes.
#
#soft_bounce = no

# LOCAL PATHNAME INFORMATION
#
# The queue_directory specifies the location of the Postfix queue.
# This is also the root directory of Postfix daemons that run chrooted.
# See the files in examples/chroot-setup for setting up Postfix chroot
# environments on different UNIX systems.
#
queue_directory = /var/spool/@MailPlus-Server/postfix

# The command_directory parameter specifies the location of all
# postXXX commands.
#
command_directory = /var/packages/MailPlus-Server/target/sbin

# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
#
daemon_directory = /var/packages/MailPlus-Server/target/libexec

# The data_directory parameter specifies the location of Postfix-writable
# data files (caches, random numbers). This directory must be owned
# by the mail_owner account (see below).
#
data_directory = /var/lib/postfix

# QUEUE AND PROCESS OWNERSHIP
#
# The mail_owner parameter specifies the owner of the Postfix queue
# and of most Postfix daemon processes.  Specify the name of a user
# account THAT DOES NOT SHARE ITS USER OR GROUP ID WITH OTHER ACCOUNTS
# AND THAT OWNS NO OTHER FILES OR PROCESSES ON THE SYSTEM.  In
# particular, don't specify nobody or daemon. PLEASE USE A DEDICATED
# USER.
#
mail_owner = postfix

# The default_privs parameter specifies the default rights used by
# the local delivery agent for delivery to external file or command.
# These rights are used in the absence of a recipient user context.
# DO NOT SPECIFY A PRIVILEGED USER OR THE POSTFIX OWNER.
#
#default_privs = nobody

# INTERNET HOST AND DOMAIN NAMES
# 
# The myhostname parameter specifies the internet hostname of this
# mail system. The default is to use the fully-qualified domain name
# from gethostname(). $myhostname is used as a default value for many
# other configuration parameters.
#
#myhostname = host.domain.tld
#myhostname = virtual.domain.tld

# The mydomain parameter specifies the local internet domain name.
# The default is to use $myhostname minus the first component.
# $mydomain is used as a default value for many other configuration
# parameters.
#
#mydomain = domain.tld

# SENDING MAIL
# 
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites.  If you run a domain with multiple
# machines, you should (1) change this to $mydomain and (2) set up
# a domain-wide alias database that aliases each user to
# user@that.users.mailhost.
#
# For the sake of consistency between sender and recipient addresses,
# myorigin also specifies the default domain name that is appended
# to recipient addresses that have no @domain part.
#
#myorigin = $myhostname
#myorigin = $mydomain

# RECEIVING MAIL

# The inet_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on.  By default,
# the software claims all active interfaces on the machine. The
# parameter also controls delivery of mail to user@[ip.address].
#
# See also the proxy_interfaces parameter, for network addresses that
# are forwarded to us via a proxy or network address translator.
#
# Note: you need to stop/start Postfix when this parameter changes.
#
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost

# The proxy_interfaces parameter specifies the network interface
# addresses that this mail system receives mail on by way of a
# proxy or network address translation unit. This setting extends
# the address list specified with the inet_interfaces parameter.
#
# You must specify your proxy/NAT addresses when your system is a
# backup MX host for other domains, otherwise mail delivery loops
# will happen when the primary MX host is down.
#
#proxy_interfaces =
#proxy_interfaces = 1.2.3.4

# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for.
#
# These domains are routed to the delivery agent specified with the
# local_transport parameter setting. By default, that is the UNIX
# compatible delivery agent that lookups all recipients in /etc/passwd
# and /etc/aliases or their equivalent.
#
# The default is $myhostname + localhost.$mydomain.  On a mail domain
# gateway, you should also include $mydomain.
#
# Do not specify the names of virtual domains - those domains are
# specified elsewhere (see VIRTUAL_README).
#
# Do not specify the names of domains that this machine is backup MX
# host for. Specify those names via the relay_domains settings for
# the SMTP server, or use permit_mx_backup if you are lazy (see
# STANDARD_CONFIGURATION_README).
#
# The local machine is always the final destination for mail addressed
# to user@[the.net.work.address] of an interface that the mail system
# receives mail on (see the inet_interfaces parameter).
#
# Specify a list of host or domain names, /file/name or type:table
# patterns, separated by commas and/or whitespace. A /file/name
# pattern is replaced by its contents; a type:table is matched when
# a name matches a lookup key (the right-hand side is ignored).
# Continue long lines by starting the next line with whitespace.
#
# See also below, section "REJECTING MAIL FOR UNKNOWN LOCAL USERS".
#
#mydestination = $myhostname, localhost.$mydomain, localhost
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain
#mydestination = $myhostname, localhost.$mydomain, localhost, $mydomain,
#    mail.$mydomain, www.$mydomain, ftp.$mydomain
#mydestination = $myhostname

# REJECTING MAIL FOR UNKNOWN LOCAL USERS
#
# The local_recipient_maps parameter specifies optional lookup tables
# with all names or addresses of users that are local with respect
# to $mydestination, $inet_interfaces or $proxy_interfaces.
#
# If this parameter is defined, then the SMTP server will reject
# mail for unknown local users. This parameter is defined by default.
#
# To turn off local recipient checking in the SMTP server, specify
# local_recipient_maps = (i.e. empty).
#
# The default setting assumes that you use the default Postfix local
# delivery agent for local delivery. You need to update the
# local_recipient_maps setting if:
#
# - You define $mydestination domain recipients in files other than
#   /etc/passwd, /etc/aliases, or the $virtual_alias_maps files.
#   For example, you define $mydestination domain recipients in    
#   the $virtual_mailbox_maps files.
#
# - You redefine the local delivery agent in master.cf.
#
# - You redefine the "local_transport" setting in main.cf.
#
# - You use the "luser_relay", "mailbox_transport", or "fallback_transport"
#   feature of the Postfix local delivery agent (see local(8)).
#
# Details are described in the LOCAL_RECIPIENT_README file.
#
# Beware: if the Postfix SMTP server runs chrooted, you probably have
# to access the passwd file via the proxymap service, in order to
# overcome chroot restrictions. The alternative, having a copy of
# the system passwd file in the chroot jail is just not practical.
#
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify a bare username, an @domain.tld
# wild-card, or specify a user@domain.tld address.
# 
#local_recipient_maps = unix:passwd.byname $alias_maps
#local_recipient_maps = proxy:unix:passwd.byname $alias_maps
#local_recipient_maps =

# The unknown_local_recipient_reject_code specifies the SMTP server
# response code when a recipient domain matches $mydestination or
# ${proxy,inet}_interfaces, while $local_recipient_maps is non-empty
# and the recipient address or address local-part is not found.
#
# The default setting is 550 (reject mail) but it is safer to start
# with 450 (try again later) until you are certain that your
# local_recipient_maps settings are OK.
#
unknown_local_recipient_reject_code = 550

# TRUST AND RELAY CONTROL

# The mynetworks parameter specifies the list of "trusted" SMTP
# clients that have more privileges than "strangers".
#
# In particular, "trusted" SMTP clients are allowed to relay mail
# through Postfix.  See the smtpd_recipient_restrictions parameter
# in postconf(5).
#
# You can specify the list of "trusted" network addresses by hand
# or you can let Postfix do it for you (which is the default).
#
# By default (mynetworks_style = subnet), Postfix "trusts" SMTP
# clients in the same IP subnetworks as the local machine.
# On Linux, this does works correctly only with interfaces specified
# with the "ifconfig" command.
# 
# Specify "mynetworks_style = class" when Postfix should "trust" SMTP
# clients in the same IP class A/B/C networks as the local machine.
# Don't do this with a dialup site - it would cause Postfix to "trust"
# your entire provider's network.  Instead, specify an explicit
# mynetworks list by hand, as described below.
#  
# Specify "mynetworks_style = host" when Postfix should "trust"
# only the local machine.
# 
#mynetworks_style = class
#mynetworks_style = subnet
#mynetworks_style = host

# Alternatively, you can specify the mynetworks list by hand, in
# which case Postfix ignores the mynetworks_style setting.
#
# Specify an explicit list of network/netmask patterns, where the
# mask specifies the number of bits in the network part of a host
# address.
#
# You can also specify the absolute pathname of a pattern file instead
# of listing the patterns here. Specify type:table for table-based lookups
# (the value on the table right-hand side is not used).
#
#mynetworks = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table

# The relay_domains parameter restricts what destinations this system will
# relay mail to.  See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
#
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
#   subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# 
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# 
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace.  Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
#
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#
#relay_domains = $mydestination

# INTERNET OR INTRANET

# The relayhost parameter specifies the default host to send mail to
# when no entry is matched in the optional transport(5) table. When
# no relayhost is given, mail is routed directly to the destination.
#
# On an intranet, specify the organizational domain name. If your
# internal DNS uses no MX records, specify the name of the intranet
# gateway host instead.
#
# In the case of SMTP, specify a domain, host, host:port, [host]:port,
# [address] or [address]:port; the form [host] turns off MX lookups.
#
# If you're connected via UUCP, see also the default_transport parameter.
#
#relayhost = $mydomain
#relayhost = [gateway.my.domain]
#relayhost = [mailserver.isp.tld]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]

# REJECTING UNKNOWN RELAY USERS
#
# The relay_recipient_maps parameter specifies optional lookup tables
# with all addresses in the domains that match $relay_domains.
#
# If this parameter is defined, then the SMTP server will reject
# mail for unknown relay users. This feature is off by default.
#
# The right-hand side of the lookup tables is conveniently ignored.
# In the left-hand side, specify an @domain.tld wild-card, or specify
# a user@domain.tld address.
# 
#relay_recipient_maps = hash:/etc/postfix/relay_recipients

# INPUT RATE CONTROL
#
# The in_flow_delay configuration parameter implements mail input
# flow control. This feature is turned on by default, although it
# still needs further development (it's disabled on SCO UNIX due
# to an SCO bug).
# 
# A Postfix process will pause for $in_flow_delay seconds before
# accepting a new message, when the message arrival rate exceeds the
# message delivery rate. With the default 100 SMTP server process
# limit, this limits the mail inflow to 100 messages a second more
# than the number of messages delivered per second.
# 
# Specify 0 to disable the feature. Valid delays are 0..10.
# 
#in_flow_delay = 1s

# ADDRESS REWRITING
#
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.

# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
#
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.

# "USER HAS MOVED" BOUNCE MESSAGES
#
# See the discussion in the ADDRESS_REWRITING_README document.

# TRANSPORT MAP
#
# See the discussion in the ADDRESS_REWRITING_README document.

# ALIAS DATABASE
#
# The alias_maps parameter specifies the list of alias databases used
# by the local delivery agent. The default list is system dependent.
#
# On systems with NIS, the default is to search the local alias
# database, then the NIS alias database. See aliases(5) for syntax
# details.
# 
# If you change the alias database, run "postalias /etc/aliases" (or
# wherever your system stores the mail alias file), or simply run
# "newaliases" to build the necessary DBM or DB file.
#
# It will take a minute or so before changes become visible.  Use
# "postfix reload" to eliminate the delay.
#
#alias_maps = dbm:/etc/aliases
#alias_maps = hash:/etc/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases

# The alias_database parameter specifies the alias database(s) that
# are built with "newaliases" or "sendmail -bi".  This is a separate
# configuration parameter, because alias_maps (see above) may specify
# tables that are not necessarily all under control by Postfix.
#
#alias_database = dbm:/etc/aliases
#alias_database = dbm:/etc/mail/aliases
#alias_database = hash:/etc/aliases
#alias_database = hash:/etc/aliases, hash:/opt/majordomo/aliases
alias_database = hash:/var/packages/MailPlus-Server/target/etc/aliases

# ADDRESS EXTENSIONS (e.g., user+foo)
#
# The recipient_delimiter parameter specifies the separator between
# user names and address extensions (user+foo). See canonical(5),
# local(8), relocated(5) and virtual(5) for the effects this has on
# aliases, canonical, virtual, relocated and .forward file lookups.
# Basically, the software tries user+foo and .forward+foo before
# trying user and .forward.
#
#recipient_delimiter = +

# DELIVERY TO MAILBOX
#
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user.  Specify
# "Maildir/" for qmail-style delivery (the / is required).
#
#home_mailbox = Mailbox
#home_mailbox = Maildir/
home_mailbox = Maildir/
 
# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#
#mail_spool_directory = /var/mail
#mail_spool_directory = /var/spool/mail

# The mailbox_command parameter specifies the optional external
# command to use instead of mailbox delivery. The command is run as
# the recipient with proper HOME, SHELL and LOGNAME environment settings.
# Exception:  delivery for root is done as $default_user.
#
# Other environment variables of interest: USER (recipient username),
# EXTENSION (address extension), DOMAIN (domain part of address),
# and LOCAL (the address localpart).
#
# Unlike other Postfix configuration parameters, the mailbox_command
# parameter is not subjected to $parameter substitutions. This is to
# make it easier to specify shell syntax (see example below).
#
# Avoid shell meta characters because they will force Postfix to run
# an expensive shell process. Procmail alone is expensive enough.
#
# IF YOU USE THIS TO DELIVER MAIL SYSTEM-WIDE, YOU MUST SET UP AN
# ALIAS THAT FORWARDS MAIL FOR ROOT TO A REAL USER.
#
#mailbox_command = /some/where/procmail
#mailbox_command = /some/where/procmail -a "$EXTENSION"
mailbox_command = /var/packages/MailPlus-Server/target/libexec/dovecot/dovecot-lda -f "$SENDER" -a "$RECIPIENT"

# The mailbox_transport specifies the optional transport in master.cf
# to use after processing aliases and .forward files. This parameter
# has precedence over the mailbox_command, fallback_transport and
# luser_relay parameters.
#
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf.  The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
#
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for    
# non-UNIX accounts with "User unknown in local recipient table".
#
#mailbox_transport = lmtp:unix:/file/name
#mailbox_transport = cyrus

# The fallback_transport specifies the optional transport in master.cf
# to use for recipients that are not found in the UNIX passwd database.
# This parameter has precedence over the luser_relay parameter.
#
# Specify a string of the form transport:nexthop, where transport is
# the name of a mail delivery transport defined in master.cf.  The
# :nexthop part is optional. For more details see the sample transport
# configuration file.
#
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for    
# non-UNIX accounts with "User unknown in local recipient table".
#
#fallback_transport = lmtp:unix:/file/name
#fallback_transport = cyrus
#fallback_transport =

# The luser_relay parameter specifies an optional destination address
# for unknown recipients.  By default, mail for unknown@$mydestination,
# unknown@[$inet_interfaces] or unknown@[$proxy_interfaces] is returned
# as undeliverable.
#
# The following expansions are done on luser_relay: $user (recipient
# username), $shell (recipient shell), $home (recipient home directory),
# $recipient (full recipient address), $extension (recipient address
# extension), $domain (recipient domain), $local (entire recipient
# localpart), $recipient_delimiter. Specify ${name?value} or
# ${name:value} to expand value only when $name does (does not) exist.
#
# luser_relay works only for the default Postfix local delivery agent.
#
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must specify "local_recipient_maps =" (i.e. empty) in
# the main.cf file, otherwise the SMTP server will reject mail for    
# non-UNIX accounts with "User unknown in local recipient table".
#
#luser_relay = $user@other.host
#luser_relay = $local@other.host
#luser_relay = admin+$local
  
# JUNK MAIL CONTROLS
# 
# The controls listed here are only a very small subset. The file
# SMTPD_ACCESS_README provides an overview.

# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
#
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
#
# For details, see "man header_checks".
#
#header_checks = regexp:/etc/postfix/header_checks

# FAST ETRN SERVICE
#
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
# See the ETRN_README document for a detailed description.
# 
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
# 
#fast_flush_domains = $relay_domains

# SHOW SOFTWARE VERSION OR NOT
#
# The smtpd_banner parameter specifies the text that follows the 220
# code in the SMTP server's greeting banner. Some people like to see
# the mail version advertised. By default, Postfix shows no version.
#
# You MUST specify $myhostname at the start of the text. That is an
# RFC requirement. Postfix itself does not care.
#
#smtpd_banner = $myhostname ESMTP $mail_name
#smtpd_banner = $myhostname ESMTP $mail_name ($mail_version)

# PARALLEL DELIVERY TO THE SAME DESTINATION
#
# How many parallel deliveries to the same user or domain? With local
# delivery, it does not make sense to do massively parallel delivery
# to the same user, because mailbox updates must happen sequentially,
# and expensive pipelines in .forward files can cause disasters when
# too many are run at the same time. With SMTP deliveries, 10
# simultaneous connections to the same domain could be sufficient to
# raise eyebrows.
# 
# Each message delivery transport has its XXX_destination_concurrency_limit
# parameter.  The default is $default_destination_concurrency_limit for
# most delivery transports. For the local delivery agent the default is 2.

#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20

# DEBUGGING CONTROL
#
# The debug_peer_level parameter specifies the increment in verbose
# logging level when an SMTP client or server host name or address
# matches a pattern in the debug_peer_list parameter.
#
#debug_peer_level = 2

# The debug_peer_list parameter specifies an optional list of domain
# or network patterns, /file/name patterns or type:name tables. When
# an SMTP client or server host name or address matches a pattern,
# increase the verbose logging level by the amount specified in the
# debug_peer_level parameter.
#
#debug_peer_list = 127.0.0.1
#debug_peer_list = some.domain

# The debugger_command specifies the external command that is executed
# when a Postfix daemon program is run with the -D option.
#
# Use "command .. & sleep 5" so that the debugger can attach before
# the process marches on. If you use an X-based debugger, be sure to
# set up your XAUTHORITY environment variable before starting Postfix.
#
#debugger_command =
#     PATH=/bin:/usr/bin:/usr/local/bin:/usr/X11R6/bin
#     ddd $daemon_directory/$process_name $process_id & sleep 5

# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
#
# debugger_command =
#    PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
#    echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
#    >$config_directory/$process_name.$process_id.log & sleep 5
#
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
#
# debugger_command =
#    PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
#    -dmS $process_name gdb $daemon_directory/$process_name
#    $process_id & sleep 1

# INSTALL-TIME CONFIGURATION INFORMATION
#
# The following parameters are used when installing a new Postfix version.
# 
# sendmail_path: The full pathname of the Postfix sendmail command.
# This is the Sendmail-compatible mail posting interface.
# 
sendmail_path = /var/packages/MailPlus-Server/target/sbin/sendmail

# newaliases_path: The full pathname of the Postfix newaliases command.
# This is the Sendmail-compatible command to build alias databases.
#
newaliases_path = /var/packages/MailPlus-Server/target/bin/newaliases

# mailq_path: The full pathname of the Postfix mailq command.  This
# is the Sendmail-compatible mail queue listing command.
# 
mailq_path = /var/packages/MailPlus-Server/target/bin/mailq

# setgid_group: The group for mail submission and queue management
# commands.  This must be a group name with a numerical group ID that
# is not shared with other accounts, not even with the Postfix account.
#
setgid_group = maildrop

# html_directory: The location of the Postfix HTML documentation.
#
#html_directory =

# manpage_directory: The location of the Postfix on-line manual pages.
#
#manpage_directory =

# sample_directory: The location of the Postfix sample configuration files.
# This parameter is obsolete as of Postfix 2.1.
#
#sample_directory =

# readme_directory: The location of the Postfix README files.
#
#readme_directory =

inet_protocols = ipv4, ipv6
mailbox_size_limit = 0
broken_sasl_auth_clients = yes
disable_vrfy_command = yes
cyrus_sasl_config_path = /var/packages/MailPlus-Server/target/etc
smtpd_sasl_authenticated_header = yes
smtpd_sasl_service = smtp_mps
smtpd_tls_cert_file = /usr/local/etc/certificate/MailPlus-Server/postfix/fullchain.pem
smtpd_tls_key_file = /usr/local/etc/certificate/MailPlus-Server/postfix/privkey.pem
smtpd_tls_security_level = may
smtpd_tls_mandatory_exclude_ciphers = aNULL, RC4
smtpd_tls_exclude_ciphers = aNULL, RC4
smtp_tls_security_level = may
smtpd_tls_protocols = !SSLv2, !SSLv3
smtpd_tls_mandatory_protocols = !SSLv2, !SSLv3
smtpd_tls_loglevel = 1
smtp_tls_loglevel = 1
smtp_tls_fingerprint_digest = sha1
smtpd_tls_fingerprint_digest = sha1
smtp_tls_note_starttls_offer = yes
smtpd_tls_received_header = yes
header_checks = regexp:/var/packages/MailPlus-Server/target/etc/header_checks, pcre:/var/packages/MailPlus-Server/target/etc/attachment_filter.pcre
sender_bcc_maps = hash:/var/packages/MailPlus-Server/target/etc/bcc/sender_bcc
recipient_bcc_maps = hash:/var/packages/MailPlus-Server/target/etc/bcc/recipient_bcc
anvil_rate_time_unit = 1d
smtp_host_lookup = dns, native
duplicate_filter_limit = 32768
smtpd_client_restrictions = check_client_access regexp:/var/packages/MailPlus-Server/target/etc/access/client_access, permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination
postscreen_dnsbl_action = enforce
postscreen_greet_action = enforce
smtpd_relay_restrictions = $smtpd_recipient_restrictions
message_drop_headers = bcc, content-length, resent-bcc
smtpd_tls_dh1024_param_file = /usr/syno/etc/ssl/dh2048.pem
smtp_tls_CApath = /etc/ssl/certs/
tls_ssl_options = no_compression
 

Merci :)

[Fenrir]

bah ajoute la directive que je t'ai indiqué (transport...)

edit : pour rappel c'est

transport_maps = hash:/chemin/vers/le/fichier/transport

Dans le fichier /chemin/vers/le/fichier/transport :

domain1.com smtp:[xxx.xxx.xxx.xxx]
domain2.com smtp:smtp.domain2.com

Modifié le 16 novembre 2016 par Fenrir

[dodo31]

transport_maps = hash:/chemin/vers/le/fichier/transport

Dans le fichier /chemin/vers/le/fichier/transport :

domain1.com smtp:[xxx.xxx.xxx.xxx]
domain2.com smtp:smtp.domain2.com

=

monsmtp.com smtp : [mon ip]
et la ? Mon domaine supplémentaire ? et mon smtp ?

Et le chemin c'est le fichier :  main.template  ?

Merci

 

 

 

 

[PiwiLAbruti]

Pour info, je viens de m'apercevoir que j'ai le même souci. J'ai vérifié la cohérence des clés serveur/DNS, tout est OK.

Le destinataire reçoit l'en-tête suivant : Authentication-Results: domain.tld; dkim=permerror (bad message/signature format)

Je vais suivre la résolution du problème de @dodo31.

[dodo31]

@PiwiLAbruti

 

J'ai réussi à régler ce soucie faut rajouter le domaine concerner dans smtp de mailserver. 

 j'ai généré une clé dkim avec le nas, que j'ai mis dans les dns de chez ovh. Ça fonctionne mais à une condition : faut que le domaine sois dans domaine supplémentaire dans smtp de mailserveur.

exemple : xxx.com > dkim généré par le nas > dkim chez ovh > xxx.com dans domaine supplémentaire sinon les mails ne sont pas signer.

Le problème c'est que si je rajoute xxx.com dans domaine supplémentaire, si aaa.com envoi un mail à xxx.com avec mon smtp, c'est le serveur nas qui le reçoit! et je je ne veux pas!! si je supprime xxx.com du domaine supplémentaire les mails ne sont plus signer dkim...

[PiwiLAbruti]

J'ai rajouté mon domaine dans la liste des domaines supplémentaires, les mails ne sont toujours pas signés. 

En ce qui te concerne ton cas d'utilisation, un relai SMTP ne serait pas plus approprié ? On des boites chez Google au taf et les envois internes sont relayés par deux NAS. Du coup j'ai mis un nom de domaine bidon dans la configuration SMTP pour éviter que ces NAS ne réceptionnent les messages.

[Fenrir]

Il y a 7 heures, dodo31 a dit :

et la ? Mon domaine supplémentaire ? et mon smtp ?

#mail a destination d'adresses en @domaine2.com doivent être envoyés au serveur smtp.domain2.com
domain2.com smtp:smtp.domain2.com

Il y a 7 heures, dodo31 a dit :

Et le chemin c'est le fichier :  main.template  ?

je pense que ça marchera, il faut tester

Il y a 3 heures, PiwiLAbruti a dit :

les mails ne sont toujours pas signés

envoi moi le source d'un des mails en MP (avec les vrais domaine)

Il y a 3 heures, PiwiLAbruti a dit :

En ce qui te concerne ton cas d'utilisation, un relai SMTP ne serait pas plus approprié ?

c'est ce que j'essaye de lui dire depuis un moment

[dodo31]

Peux tu m'expliquer le but du relais smtp.

SI je comprend bien me faut un autre serveur smtp.

exemple : un VPS chez ovh qui sera relay dessus?

Pourquoi un relais? je te cache pas que je comprend pas trop.

Du coupe les mails seront envoyer par ip du vps ?

merci :)

[Fenrir]

il y a 1 minute, dodo31 a dit :

Peux tu m'expliquer le but du relais smtp.

Un relai c'est ce que tu fais déjà avec ton syno pour l'autre domaine, c'est un serveur qui prend des mails d'un domaine pour les envoyer quelque part. Il ne garde pas de mail en local. Comme c'est un rôle dédié, ça ne consomme presque pas de ressources, donc c'est capable de gérer bcp de mails (et de le signer si besoin).

Dans ton cas précis, tu as 2 types de domaines  :

• ceux que tu veux gérer avec le Syno (le nas est la destination finale)
• ceux qui doivent continuer leur voyage vers Internet => pour ceux là ton syno evrait être relai

Le soucis c'est qu'un nas ce n'est pas fait pour :

• pour le syno, tout ce qui rentre c'est pour lui, donc tu es contraint de bidouiller avec transport
• tu as une grosse volumétrie de mail (ce n'est pas dans le post mais on en a discuté ailleurs), trop grosse pour que ça soit raisonnable de passer par le syno (ou alors seulement en backup)

Avec un serveur dédié hébergé :

• tu pourras sans soucis modifier la conf
• tu auras un reverse DNS propre qui ne sera pas lié à une ligne ADSL
• tu auras une bande passante bien plus importante
• tu pourras faire des réglages plus avancé
• ...

Après c'est à toi de voir, tu as les 2 possibilités :

• bricoler le syno pour lui faire faire un truc non prévu et risquer de recevoir un avertissement de ton FAI à cause du volume (plus forte proba d'être détecté comme spammeur à cause de l'ip ADSL)
• monter un truc propre : c'est plus contraignant c'est certain, c'est aussi un métier, mais on peut arriver à faire un truc assez propre avec quelques heures de recherche

[dodo31]

OK merci

j'aimes les choses propres

Je prend un VPS chez ovh, je configure Debian 8?

Et je vois après pour postfix ?

[Fenrir]

il y a 12 minutes, dodo31 a dit :

Je prend un VPS chez ovh, je configure Debian 8?

commence par te monter une maquette, par exemple avec une petite VM sur ton PC

Un postfix reste un postfix, peu importe l'OS, la conf reste la même, si ça marche sur ta maquette, ça marchera sur un VPS ou un cluster à 50 nœuds.

Par contre fais bien attention au points suivants :

• firewall : il faut bien le configurer
• relai ouvert : tu ne dois PAS relayer des domaines que tu ne gère pas (en gros en entrée, si tu ne connais pas il faut jeter)

A noter que tu pourras aussi te servir de ce relai pour les mails sortant de ton syno, comme ça plus besoin du DKIM sur le syno (c'est le relai qui le fera pour tous les domaines) et moins de chance d'être attrapé par un antispam (si tu configures correctement ton serveur, les DNS direct et inverse, ...).

[dodo31]

ok merci

j'essaye 

j'aurais surement besoin de ton aide:)

[dodo31]

Salut, @Fenrir

 

j'ai installer postfix.

j'ai besoin d'aide pour la configuration stp.
Pour tester j'ai fais avec mon domaine perso.
j'ai mi en place les dns... / reverse

si je lance la commande :

$ host -t MX monDomaine.com

réponse :

monDomaine.com mail is handled by 1 smtp.monDomaine.com

Apres si je ping smtp.mondo.com 

Sa tombe sur mon ip c'est ok.

J'ai ouvert le port 25.

j'ai installer postfix.

si je lance la commande hostname: j'ai smtp.mondom.com

a l’installation de postfix, j'ai choisie Internet Site, et le nom de la machine, smtp.mondom.com

j'ai installer :

# aptitude install mailx

j'ai envoyer un mail :

# echo "Le contenu du mail" | mail -s "ceci est le sujet" xxx@monDomaine.com

j'ai bien reçu. ( de root@mondom.com)

je suis bloquer ici.

je n'est pas de fichier  transport.

Faut t'il le crée ? si oui comment le configurer ?

Voici mon fichier main.cf: en PV car il y a mon domaine.

Il doit me manquer des choses.... 

Merci

 

 

 

[Fenrir]

Il y a 5 heures, dodo31 a dit :

smtpd_relay_restrictions = permit_mynetworks permit_sasl_authenticated defer_unauth_destination

ici tu n'autorise à faire relai que pour

Il y a 5 heures, dodo31 a dit :

mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128

et les connexions authentifiées (sasl)

Il faut donc, à minima, que tu autorises aussi l'adresse d'où vont venir les mails à relayer (celle de chez toi ou de l'entreprise)

Il y a 5 heures, dodo31 a dit :

mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128 XXX.XXX.XXX.XXX/32

---------------------

Il y a 5 heures, dodo31 a dit :

mydestination = smtp.dxxxx-bxxxxxx.fr,  localhost.dxxxxx-bxxxxxx.fr, , localhost

c'est un relai, normalement il ne doit pas prendre de mails pour lui =>

Il y a 5 heures, dodo31 a dit :

mydestination = localhost

---------------------

Il y a 5 heures, dodo31 a dit :

je n'est pas de fichier  transport.

pas nécessaire pour un relai sur Internet en général (mais c'est parfois utile avec certaines destinations)

---------------------

Pour tester, une fois les corrections effectuées, le plus simple c'est un telnet depuis ton pc :

telnet smtp.monDomaine.com 25
ehlo maison
mail from: uneadressevalide@domaine.source
rcpt to: uneadressevalide@domaine.destination
data
subject: mail de test
blabla
.
quit

 

[dodo31]

Salut, @Fenrir

alors:

Voici mon fichier main.cf en PV et aussi   /etc/dovecot/conf.d/10-master.conf

je n'arrive pas a faire la commande telnet:

telnet smtp.mondomaine.com 25

Sa fais rien, le petite barre qui clignote et c'est tous je ne peux rien taper.

Si j'essaye dans un outlook avec la conf suivante:

imap; smtp.dxxxxxx-xxxxxxx.fr port 143
smtp : smtp.dxxxxx-xxxxxxxx.fr port 25 avec auth.

ça fonctionne pas :/

si je configure en automatique, avec smtp.dxxxxx-xx.fr

Il trouve les imap et smtp de 1&1 automatiquement ? c'est pas normal ?

merci

 

MAJ:

smtp.dxxxxx-xxxxx.fr

port 25

Si je rentre mon ip dans mynetworks ca fonctionne. j'arrive en a envoyer avec ça.

sous condition que je supprime de main.cf :

# Activer l'identification SASL
smtpd_sasl_auth_enable = yes

# Utiliser le service d'identification de Dovecot
smtpd_sasl_type = dovecot
smtpd_sasl_path = private/auth

# Noter dans les en-tête des messages l'identifiant de l'utilisateur.
smtpd_sasl_authenticated_header = yes

Sinon les mails ne parte pas.

Mais comment dire a postfix que j'autorise tous les domaines et toutes les ip si il est auth avec le port 587 ?

Es ce que dovecot est utile ? Si oui comment le configurer ?

Merci

 

 

Modifié le 22 novembre 2016 par dodo31

[PiwiLAbruti]

Le fait que ton client Outlook configure les serveurs de 1&1 vient très probablement du fait qu'un enregistrement _autodiscover._tcp est déjà renseigné par défaut dans la zone de ton nom de domaine.

En automatique, Outlook utilise l'enregistrement SRV _autodiscover._tcp.domain.tld pour localiser le serveur qui fournit un fichier XML https://autodiscover.<smtpdomain>/Autodiscover/Autodiscover.xml contenant la configuration des clients Outlook.

Plus de détails sur le site de Microsoft :

• https://support.microsoft.com/fr-fr/kb/940881
• https://msdn.microsoft.com/fr-fr/library/office/jj900169(v=exchg.150).aspx

De manière plus standard, la configuration des clients peut se faire avec de simples enregistrements SRV :

_imaps._tcp.domain.tld.		SRV		0 1 993 imap.domain.tld.
_submission._tcp.domain.tld.	SRV		0 1 587 smtp.domain.tld.

Malheureusement ceci est très rarement implémenté alors que ça simplifierait la vie de beaucoup d'utilisateurs et renforcerait la sécurité en privilégiant les échanges chiffrés.

[dodo31]

Ok merci pour l'info c'est bon a savoir.

toute façon mon serveur me servira juste pour du smtp :) si j'y arrive