Не приходит почта на сервер. Как подружить sendmail и dovecot?

Суть вот в чем. Для сайтов поставил на сервер MTA sendmail(DKIM, DMARK, SFP сделал). Отправляется почта на отлично. А вот получить никак не могу. Установил для POP3/IMAP себе dovecot, но как настроить эту историю с sendmail не очень понятно. Конфиг dovecot:
## Dovecot configuration file

# If you're in a hurry, see http://wiki2.dovecot.org/QuickConfiguration

# "doveconf -n" command gives a clean output of the changed settings. Use it
# instead of copy&pasting files when posting to the Dovecot mailing list.

# '#' character and everything after it is treated as comments. Extra spaces
# and tabs are ignored. If you want to use either of these explicitly, put the
# value inside quotes, eg.: key = "# char and trailing whitespace  "

# Most (but not all) settings can be overridden by different protocols and/or
# source/destination IPs by placing the settings inside sections, for example:
# protocol imap { }, local { }, remote { }

# Default values are shown for each setting, it's not required to uncomment
# those. These are exceptions to this though: No sections (e.g. namespace {})
# or plugin settings are added by default, they're listed only as examples.
# Paths are also just examples with the real defaults being based on configure
# options. The paths listed here are for configure --prefix=/usr
# --sysconfdir=/etc --localstatedir=/var

# Enable installed protocols
!include_try /usr/share/dovecot/protocols.d/*.protocol

# A comma separated list of IPs or hosts where to listen in for connections. 
# "*" listens in all IPv4 interfaces, "::" listens in all IPv6 interfaces.
# If you want to specify non-default ports or anything more complex,
# edit conf.d/master.conf.
#listen = *, ::

# Base directory where to store runtime data.
#base_dir = /var/run/dovecot/

# Name of this instance. In multi-instance setup doveadm and other commands
# can use -i <instance_name> to select which instance is used (an alternative
# to -c <config_path>). The instance name is also added to Dovecot processes
# in ps output.
#instance_name = dovecot

# Greeting message for clients.
#login_greeting = Dovecot ready.

# Space separated list of trusted network ranges. Connections from these
# IPs are allowed to override their IP addresses and ports (for logging and
# for authentication checks). disable_plaintext_auth is also ignored for
# these networks. Typically you'd specify your IMAP proxy servers here.
#login_trusted_networks =

# Space separated list of login access check sockets (e.g. tcpwrap)
#login_access_sockets = 

# With proxy_maybe=yes if proxy destination matches any of these IPs, don't do
# proxying. This isn't necessary normally, but may be useful if the destination
# IP is e.g. a load balancer's IP.
#auth_proxy_self =

# Show more verbose process titles (in ps). Currently shows user name and
# IP address. Useful for seeing who are actually using the IMAP processes
# (eg. shared mailboxes or if same uid is used for multiple accounts).
#verbose_proctitle = no

# Should all processes be killed when Dovecot master process shuts down.
# Setting this to "no" means that Dovecot can be upgraded without
# forcing existing client connections to close (although that could also be
# a problem if the upgrade is e.g. because of a security fix).
#shutdown_clients = yes

# If non-zero, run mail commands via this many connections to doveadm server,
# instead of running them directly in the same process.
#doveadm_worker_count = 0
# UNIX socket or host:port used for connecting to doveadm server
#doveadm_socket_path = doveadm-server

# Space separated list of environment variables that are preserved on Dovecot
# startup and passed down to all of its child processes. You can also give
# key=value pairs to always set specific settings.
#import_environment = TZ

## Dictionary server settings

# Dictionary can be used to store key=value lists. This is used by several
# plugins. The dictionary can be accessed either directly or though a
# dictionary server. The following dict block maps dictionary names to URIs
# when the server is used. These can then be referenced using URIs in format
# "proxy::<name>".

dict {
  #quota = mysql:/etc/dovecot/dovecot-dict-sql.conf.ext
  #expire = sqlite:/etc/dovecot/dovecot-dict-sql.conf.ext

# Most of the actual configuration gets included below. The filenames are
# first sorted by their ASCII value and parsed in that order. The 00-prefixes
# in filenames are intended to make it easier to understand the ordering.
!include conf.d/*.conf

# A config file can also tried to be included without giving an error if
# it's not found:
!include_try local.conf
  • Вопрос задан
  • 146 просмотров
Пригласить эксперта
Ответы на вопрос 3
никого не трогаю, починяю примус
Этого недостаточно. Смотрите остальные конфиги
!include conf.d/*.conf

главный вопрос, на который вы должны себе ответить - куда кладет почту sendmail , а как к этому место получает доступ dovecot
Ответ написан
@leahch Куратор тега Linux
3D специалист. Dолго, Dорого, Dерьмово.
Блииииин! Ну почему, почему sendmail, которому больше 35 лет! Который без M4 никак не настроить! Берите opensmtpd, конфиг в 10 строчек.

1) что значит "не приходит"? MX запись настроили?
2) что в логах пишет sendmail?
3) почему sendmail?
4) в каком формате maildir?
5) имеет ли туда доступ в dovecot?
6) у вас почта точно не отсекается по SPF? DKIM? DMARC?
Ответ написан
@depressionofoleg Автор вопроса
1) MX запись настроил вроде адекватно, почта приходит не первый день, проблем не возникает. Собственно как и spf, dmark, dkim
2) По принятым письмам mail.log ничего не говорит, только по отправленным
3) Неофит в вопросах настройки почты, первый раз делаю подобное, выбрал sendmail из-за обилия гайдов.
4) Где настроить maildir в sendmail не нашел. В dovecot почта отправляется в mbox:~/mail:INBOX=/var/spool/mail/%u
5) Вот как раз в этом вопрос, не нашел где сендмейл почту хранит(если вообще хранит, smtp вроде для отправки служит)
Я извиняюсь, в теории многое понимаю, а вот на практике понят не могу.
Ответ написан
Ваш ответ на вопрос

Войдите, чтобы написать ответ

Войти через центр авторизации
Похожие вопросы