exim не принимает почту, courier-authdaemond не запускается!

EXIM, sendmail, postfix, Dovecot и прочие. Решение проблем связанных с работой электронной почты

Модератор: xM

Правила форума
Убедительная просьба юзать теги [code] при оформлении листингов.
Сообщения не оформленные должным образом имеют все шансы быть незамеченными.
lomaker
рядовой
Сообщения: 20
Зарегистрирован: 2008-08-08 12:33:43

exim не принимает почту, courier-authdaemond не запускается!

Непрочитанное сообщение lomaker » 2008-08-08 13:47:52

Поставил exim+courier-imap+clamav+postfixadmin по статье. Пробую отправлять почту с сервера - письма уходят. Пробую отправлять письма с сервера самому себе - ходят. А вот при отправке с внешнего почтаря сообщение неприлетает и в логах пишет следующее:

Aug 8 18:16:24 medved exim[20796]: 2008-08-08 18:16:24 DNS list lookup defer (probably timeout) for 52.200.180.213.opm.blitzed.org: assumed not in list
Aug 8 18:16:39 medved exim[20796]: 2008-08-08 18:16:39 DNS list lookup defer (probably timeout) for 52.200.180.213.bl.csma.biz: assumed not in list
Aug 8 18:16:54 medved exim[20796]: 2008-08-08 18:16:54 DNS list lookup defer (probably timeout) for 52.200.180.213.dynablock.njabl.org: assumed not in list
Aug 8 18:16:54 medved exim[20796]: 2008-08-08 18:16:54 Delay 20s for webmail11.yandex.ru [213.180.200.52] with HELO=webmail11.yandex.ru. Mail from Pupkin@yandex.ru to pupkin@mydomain.ru.
Aug 8 18:17:15 medved exim[20796]: 2008-08-08 18:17:15 1KRP22-0005PQ-VA malware acl condition: clamd: invalid socket 'var/run/clamav/clamd.sock'
Aug 8 18:17:15 medved exim[20796]: 2008-08-08 18:17:15 1KRP22-0005PQ-VA malware acl condition: clamd: invalid socket 'var/run/clamav/clamd.sock'
Aug 8 18:17:15 medved exim[20796]: 2008-08-08 18:17:15 1KRP22-0005PQ-VA H=webmail11.yandex.ru [213.180.200.52] I=[213.24.155.53]:25 F=<Pupkin@yandex.ru> temporarily rejected after DATA
Aug 8 18:17:15 medved exim[20796]: [1\22] 2008-08-08 18:17:15 1KRP22-0005PQ-VA H=webmail11.yandex.ru [213.180.200.52] I=[213.24.155.53]:25 F=<Pupkin@yandex.ru> temporarily rejected after DATA
Aug 8 18:17:15 medved exim[20796]: [2\22] Envelope-from: <Pupkin@yandex.ru>
Aug 8 18:17:15 medved exim[20796]: [3\22] Envelope-to: <pupkin@mydomain.ru>
Aug 8 18:17:15 medved exim[20796]: [4\22] P Received: from webmail11.yandex.ru ([213.180.200.52])
Aug 8 18:17:15 medved exim[20796]: [5\22] by mail.mydomain.ru with esmtp (Exim 4.68 (FreeBSD))
Aug 8 18:17:15 medved exim[20796]: [6\22] (envelope-from <Pupkin@yandex.ru>)
Aug 8 18:17:15 medved exim[20796]: [7\22] id 1KRP22-0005PQ-VA
Aug 8 18:17:15 medved exim[20796]: [8\22] for pupkin@mydomain.ru; Fri, 08 Aug 2008 18:17:15 +0800
Aug 8 18:17:15 medved exim[20796]: [9\22] P Received: from YAMAIL (webmail11) by mail.yandex.ru id S2999428AbYHHHbP for
Aug 8 18:17:15 medved exim[20796]: [10\22] <pupkin@mydomain.ru>; Fri, 8 Aug 2008 11:31:15 +0400
Aug 8 18:17:15 medved exim[20796]: [11\22] X-Yandex-Spam: 1
Aug 8 18:17:15 medved exim[20796]: [12\22] P Received: from [213.24.155.53] ([213.24.155.53]) by mail.yandex.ru with HTTP;
Aug 8 18:17:15 medved exim[20796]: [13\22] Fri, 08 Aug 2008 11:31:15 +0400
Aug 8 18:17:15 medved exim[20796]: [14\22] F From: St Danila <Pupkin@yandex.ru>
Aug 8 18:17:15 medved exim[20796]: [15\22] T To: pupkin@mydomain.ru
Aug 8 18:17:15 medved exim[20796]: [16\22] Subject: test
Aug 8 18:17:15 medved exim[20796]: [17\22] MIME-Version: 1.0
Aug 8 18:17:15 medved exim[20796]: [18\22] I Message-Id: <674161218180675@webmail11.yandex.ru>
Aug 8 18:17:15 medved exim[20796]: [19\22] Date: Fri, 08 Aug 2008 11:31:15 +0400
Aug 8 18:17:15 medved exim[20796]: [20\22] X-Mailer: Yamail [ http://yandex.ru ] 5.0
Aug 8 18:17:15 medved exim[20796]: [21\22] Content-Transfer-Encoding: 8bit
Aug 8 18:17:15 medved exim[20796]: [22/22] Content-Type: text/plain; charset=KOI8-R
Aug 8 18:17:15 medved exim[20796]: 2008-08-08 18:17:15 DNS list lookup defer (probably timeout) for 52.200.180.213.opm.blitzed.org: assumed not in list
Aug 8 18:17:15 medved exim[20796]: 2008-08-08 18:17:15 DNS list lookup defer (probably timeout) for 52.200.180.213.bl.csma.biz: assumed not in list
Aug 8 18:17:15 medved exim[20796]: 2008-08-08 18:17:15 DNS list lookup defer (probably timeout) for 52.200.180.213.dynablock.njabl.org: assumed not in list
Aug 8 18:17:15 medved exim[20796]: 2008-08-08 18:17:15 Delay 20s for webmail11.yandex.ru [213.180.200.52] with HELO=webmail11.yandex.ru. Mail from Pupkin@yandex.ru to pupkin@mydomain.ru.
Aug 8 18:17:35 medved exim[20796]: 2008-08-08 18:17:35 1KRP2N-0005PQ-FD malware acl condition: clamd: invalid socket 'var/run/clamav/clamd.sock'
Aug 8 18:17:35 medved exim[20796]: 2008-08-08 18:17:35 1KRP2N-0005PQ-FD malware acl condition: clamd: invalid socket 'var/run/clamav/clamd.sock'
Aug 8 18:17:35 medved exim[20796]: 2008-08-08 18:17:35 1KRP2N-0005PQ-FD H=webmail11.yandex.ru [213.180.200.52] I=[213.24.155.53]:25 F=<Pupkin@yandex.ru> temporarily rejected after DATA
Aug 8 18:17:35 medved exim[20796]: [1\22] 2008-08-08 18:17:35 1KRP2N-0005PQ-FD H=webmail11.yandex.ru [213.180.200.52] I=[213.24.155.53]:25 F=<Pupkin@yandex.ru> temporarily rejected after DATA
Aug 8 18:17:35 medved exim[20796]: [2\22] Envelope-from: <Pupkin@yandex.ru>
Aug 8 18:17:35 medved exim[20796]: [3\22] Envelope-to: <pupkin@mydomain.ru>
Aug 8 18:17:35 medved exim[20796]: [4\22] P Received: from webmail11.yandex.ru ([213.180.200.52])
Aug 8 18:17:35 medved exim[20796]: [5\22] by mail.mydomain.ru with esmtp (Exim 4.68 (FreeBSD))
Aug 8 18:17:35 medved exim[20796]: [6\22] (envelope-from <Pupkin@yandex.ru>)
Aug 8 18:17:35 medved exim[20796]: [7\22] id 1KRP2N-0005PQ-FD
Aug 8 18:17:35 medved exim[20796]: [8\22] for pupkin@mydomain.ru; Fri, 08 Aug 2008 18:17:35 +0800
Aug 8 18:17:35 medved exim[20796]: [9\22] P Received: from YAMAIL (webmail11) by mail.yandex.ru id S2999428AbYHHHbP for
Aug 8 18:17:35 medved exim[20796]: [10\22] <pupkin@mydomain.ru>; Fri, 8 Aug 2008 11:31:15 +0400
Aug 8 18:17:35 medved exim[20796]: [11\22] X-Yandex-Spam: 1
Aug 8 18:17:35 medved exim[20796]: [12\22] P Received: from [213.24.155.53] ([213.24.155.53]) by mail.yandex.ru with HTTP;
Aug 8 18:17:35 medved exim[20796]: [13\22] Fri, 08 Aug 2008 11:31:15 +0400
Aug 8 18:17:35 medved exim[20796]: [14\22] F From: St Danila <Pupkin@yandex.ru>
Aug 8 18:17:35 medved exim[20796]: [15\22] T To: pupkin@mydomain.ru
Aug 8 18:17:35 medved exim[20796]: [16\22] Subject: test
Aug 8 18:17:35 medved exim[20796]: [17\22] MIME-Version: 1.0
Aug 8 18:17:35 medved exim[20796]: [18\22] I Message-Id: <674161218180675@webmail11.yandex.ru>
Aug 8 18:17:35 medved exim[20796]: [19\22] Date: Fri, 08 Aug 2008 11:31:15 +0400
Aug 8 18:17:35 medved exim[20796]: [20\22] X-Mailer: Yamail [ http://yandex.ru ] 5.0
Aug 8 18:17:35 medved exim[20796]: [21\22] Content-Transfer-Encoding: 8bit
Aug 8 18:17:35 medved exim[20796]: [22/22] Content-Type: text/plain; charset=KOI8-R

В чем собака зарыта? Что значят эти сообщения? Если не сложно, опишите поподробнее плиз!!!

Далее ставлю courier-imap, рихтую конфиг авторизации. Набираю

./couruer-authdaemond start
./sockstat | grep authd
а фиг вам - не запускается он. Опять же в чем может бять причина? Может косячу в синтаксисе? Имеется ли возможность где-нибудь посмотреть его логи, в которых написано что его не устраивает? На всякий случай мой конфиг

#!/bin/sh
##VERSION: $Id: authmysqlrc,v 1.20 2007/10/07 02:50:45 mrsam Exp $
#
# Copyright 2000-2007 Double Precision, Inc. See COPYING for
# distribution information.
#
# Do not alter lines that begin with ##, they are used when upgrading
# this configuration.
#
# authmysqlrc created from authmysqlrc.dist by sysconftool
#
# DO NOT INSTALL THIS FILE with world read permissions. This file
# might contain the MySQL admin password!
#
# Each line in this file must follow the following format:
#
# field[spaces|tabs]value
#
# That is, the name of the field, followed by spaces or tabs, followed by
# field value. Trailing spaces are prohibited.


##NAME: LOCATION:0
#
# The server name, userid, and password used to log in.

MYSQL_SERVER localhost
MYSQL_USERNAME exim
MYSQL_PASSWORD exim

##NAME: SSLINFO:0
#
# The SSL information.
#
# To use SSL-encrypted connections, define the following variables (available
# in MySQL 4.0, or higher):
#
#
# MYSQL_SSL_KEY /path/to/file
# MYSQL_SSL_CERT /path/to/file
# MYSQL_SSL_CACERT /path/to/file
# MYSQL_SSL_CAPATH /path/to/file
# MYSQL_SSL_CIPHERS ALL:!DES

##NAME: MYSQL_SOCKET:0
#
# MYSQL_SOCKET can be used with MySQL version 3.22 or later, it specifies the
# filesystem pipe used for the connection
#
# MYSQL_SOCKET /var/mysql/mysql.sock

##NAME: MYSQL_PORT:0
#
# MYSQL_PORT can be used with MySQL version 3.22 or later to specify a port to
# connect to.

MYSQL_PORT 3306

##NAME: MYSQL_OPT:0
#
# Leave MYSQL_OPT as 0, unless you know what you're doing.

MYSQL_OPT 0

##NAME: MYSQL_DATABASE:0
#
# The name of the MySQL database we will open:

MYSQL_DATABASE exim

#NAME: MYSQL_CHARACTER_SET:0
#
# This is optional. MYSQL_CHARACTER_SET installs a character set. This option
# can be used with MySQL version 4.1 or later. MySQL supports 70+ collations
# for 30+ character sets. See MySQL documentations for more detalis.
#
# MYSQL_CHARACTER_SET latin1

##NAME: MYSQL_USER_TABLE:0
#
# The name of the table containing your user data. See README.authmysqlrc
# for the required fields in this table.

MYSQL_USER_TABLE mailbox

##NAME: MYSQL_CRYPT_PWFIELD:0
#
# Either MYSQL_CRYPT_PWFIELD or MYSQL_CLEAR_PWFIELD must be defined. Both
# are OK too. crypted passwords go into MYSQL_CRYPT_PWFIELD, cleartext
# passwords go into MYSQL_CLEAR_PWFIELD. Cleartext passwords allow
# CRAM-MD5 authentication to be implemented.

#MYSQL_CRYPT_PWFIELD password

##NAME: MYSQL_CLEAR_PWFIELD:0
#
#
MYSQL_CLEAR_PWFIELD password

##NAME: MYSQL_DEFAULT_DOMAIN:0
#
# If DEFAULT_DOMAIN is defined, and someone tries to log in as 'user',
# we will look up 'user@DEFAULT_DOMAIN' instead.
#
#
DEFAULT_DOMAIN mydomain.ru

##NAME: MYSQL_UID_FIELD:0
#
# Other fields in the mysql table:
#
# MYSQL_UID_FIELD - contains the numerical userid of the account
#
MYSQL_UID_FIELD 26

##NAME: MYSQL_GID_FIELD:0
#
# Numerical groupid of the account

MYSQL_GID_FIELD 26

##NAME: MYSQL_LOGIN_FIELD:0
#
# The login id, default is id. Basically the query is:
#
# SELECT MYSQL_UID_FIELD, MYSQL_GID_FIELD, ... WHERE id='loginid'
#

MYSQL_LOGIN_FIELD username

##NAME: MYSQL_HOME_FIELD:0
#

MYSQL_HOME_FIELD CONCAT('/var/mail/exim', maildir)

##NAME: MYSQL_NAME_FIELD:0
#
# The user's name (optional)

MYSQL_NAME_FIELD name

##NAME: MYSQL_MAILDIR_FIELD:0
#
# This is an optional field, and can be used to specify an arbitrary
# location of the maildir for the account, which normally defaults to
# $HOME/Maildir (where $HOME is read from MYSQL_HOME_FIELD).
#
# You still need to provide a MYSQL_HOME_FIELD, even if you uncomment this
# out.
#
MYSQL_MAILDIR_FIELD CONCAT('/var/mail/exim/', maildir)

Помогите чем смогете!!!

Хостинговая компания Host-Food.ru
Хостинг HostFood.ru
 

Услуги хостинговой компании Host-Food.ru

Хостинг HostFood.ru

Тарифы на хостинг в России, от 12 рублей: https://www.host-food.ru/tariffs/hosting/
Тарифы на виртуальные сервера (VPS/VDS/KVM) в РФ, от 189 руб.: https://www.host-food.ru/tariffs/virtualny-server-vps/
Выделенные сервера, Россия, Москва, от 2460 рублей (8 CPU, 8Gb RAM, 2x500Gb HDD, RAID 3ware 9750):
https://www.host-food.ru/tariffs/vydelennyi-server-ds/
Недорогие домены в популярных зонах: https://www.host-food.ru/domains/

Аватара пользователя
Alex Keda
стреляли...
Сообщения: 35068
Зарегистрирован: 2004-10-18 14:25:19
Откуда: Made in USSR
Контактная информация:

Re: exim не принимает почту, courier-authdaemond не запускается!

Непрочитанное сообщение Alex Keda » 2008-08-08 15:26:55

сообщение нормально оформите
Убей их всех! Бог потом рассортирует...

Alex_hha
лейтенант
Сообщения: 755
Зарегистрирован: 2005-11-06 18:25:26
Контактная информация:

Re: exim не принимает почту, courier-authdaemond не запускается!

Непрочитанное сообщение Alex_hha » 2008-08-08 17:35:15

clamd: invalid socket 'var/run/clamav/clamd.sock'
переведи на русский со словарем

lomaker
рядовой
Сообщения: 20
Зарегистрирован: 2008-08-08 12:33:43

Re: exim не принимает почту, courier-authdaemond не запускается!

Непрочитанное сообщение lomaker » 2008-08-09 5:53:31

lissyara писал(а):сообщение нормально оформите
извините, не знаком с правилами оформления на вашем сайте. Если можете дайте ссылку на ман :smile:

lomaker
рядовой
Сообщения: 20
Зарегистрирован: 2008-08-08 12:33:43

Re: exim не принимает почту, courier-authdaemond не запускается!

Непрочитанное сообщение lomaker » 2008-08-09 6:10:58

Alex_hha писал(а):
clamd: invalid socket 'var/run/clamav/clamd.sock'
переведи на русский со словарем
С английским у меня проблем не возникает :smile: читать умею. Кстати в сообщении забыл указать - с хламав пытался разобраться - сокет на месте. пробовал даже его переустановить к чертям - не помогло!!!
Попробую оформить сообщение должным образом :smile:
Поставил exim+courier-imap+clamav+postfixadmin по статье. Пробую отправлять почту с сервера - письма уходят. Пробую отправлять письма с сервера самому себе - ходят. А вот при отправке с внешнего почтаря сообщение неприлетает и в логах пишет следующее:

Код: Выделить всё

Aug 8 18:16:24 medved exim[20796]: 2008-08-08 18:16:24 DNS list lookup defer (probably timeout) for 52.200.180.213.opm.blitzed.org: assumed not in list
Aug 8 18:16:39 medved exim[20796]: 2008-08-08 18:16:39 DNS list lookup defer (probably timeout) for 52.200.180.213.bl.csma.biz: assumed not in list
Aug 8 18:16:54 medved exim[20796]: 2008-08-08 18:16:54 DNS list lookup defer (probably timeout) for 52.200.180.213.dynablock.njabl.org: assumed not in list
Aug 8 18:16:54 medved exim[20796]: 2008-08-08 18:16:54 Delay 20s for webmail11.yandex.ru [213.180.200.52] with HELO=webmail11.yandex.ru. Mail from Pupkin@yandex.ru to pupkin@mydomain.ru.
Aug 8 18:17:15 medved exim[20796]: 2008-08-08 18:17:15 1KRP22-0005PQ-VA malware acl condition: clamd: invalid socket 'var/run/clamav/clamd.sock'
Aug 8 18:17:15 medved exim[20796]: 2008-08-08 18:17:15 1KRP22-0005PQ-VA malware acl condition: clamd: invalid socket 'var/run/clamav/clamd.sock'
Aug 8 18:17:15 medved exim[20796]: 2008-08-08 18:17:15 1KRP22-0005PQ-VA H=webmail11.yandex.ru [213.180.200.52] I=[213.24.155.53]:25 F=<Pupkin@yandex.ru> temporarily rejected after DATA
Aug 8 18:17:15 medved exim[20796]: [1\22] 2008-08-08 18:17:15 1KRP22-0005PQ-VA H=webmail11.yandex.ru [213.180.200.52] I=[213.24.155.53]:25 F=<Pupkin@yandex.ru> temporarily rejected after DATA
Aug 8 18:17:15 medved exim[20796]: [2\22] Envelope-from: <Pupkin@yandex.ru>
Aug 8 18:17:15 medved exim[20796]: [3\22] Envelope-to: <pupkin@mydomain.ru>
Aug 8 18:17:15 medved exim[20796]: [4\22] P Received: from webmail11.yandex.ru ([213.180.200.52])
Aug 8 18:17:15 medved exim[20796]: [5\22] by mail.mydomain.ru with esmtp (Exim 4.68 (FreeBSD))
Aug 8 18:17:15 medved exim[20796]: [6\22] (envelope-from <Pupkin@yandex.ru>)
Aug 8 18:17:15 medved exim[20796]: [7\22] id 1KRP22-0005PQ-VA
Aug 8 18:17:15 medved exim[20796]: [8\22] for pupkin@mydomain.ru; Fri, 08 Aug 2008 18:17:15 +0800
Aug 8 18:17:15 medved exim[20796]: [9\22] P Received: from YAMAIL (webmail11) by mail.yandex.ru id S2999428AbYHHHbP for
Aug 8 18:17:15 medved exim[20796]: [10\22] <pupkin@mydomain.ru>; Fri, 8 Aug 2008 11:31:15 +0400
Aug 8 18:17:15 medved exim[20796]: [11\22] X-Yandex-Spam: 1
Aug 8 18:17:15 medved exim[20796]: [12\22] P Received: from [213.24.155.53] ([213.24.155.53]) by mail.yandex.ru with HTTP;
Aug 8 18:17:15 medved exim[20796]: [13\22] Fri, 08 Aug 2008 11:31:15 +0400
Aug 8 18:17:15 medved exim[20796]: [14\22] F From: St Danila <Pupkin@yandex.ru>
Aug 8 18:17:15 medved exim[20796]: [15\22] T To: pupkin@mydomain.ru
Aug 8 18:17:15 medved exim[20796]: [16\22] Subject: test
Aug 8 18:17:15 medved exim[20796]: [17\22] MIME-Version: 1.0
Aug 8 18:17:15 medved exim[20796]: [18\22] I Message-Id: <674161218180675@webmail11.yandex.ru>
Aug 8 18:17:15 medved exim[20796]: [19\22] Date: Fri, 08 Aug 2008 11:31:15 +0400
Aug 8 18:17:15 medved exim[20796]: [20\22] X-Mailer: Yamail [ http://yandex.ru ] 5.0
Aug 8 18:17:15 medved exim[20796]: [21\22] Content-Transfer-Encoding: 8bit
Aug 8 18:17:15 medved exim[20796]: [22/22] Content-Type: text/plain; charset=KOI8-R
Aug 8 18:17:15 medved exim[20796]: 2008-08-08 18:17:15 DNS list lookup defer (probably timeout) for 52.200.180.213.opm.blitzed.org: assumed not in list
Aug 8 18:17:15 medved exim[20796]: 2008-08-08 18:17:15 DNS list lookup defer (probably timeout) for 52.200.180.213.bl.csma.biz: assumed not in list
Aug 8 18:17:15 medved exim[20796]: 2008-08-08 18:17:15 DNS list lookup defer (probably timeout) for 52.200.180.213.dynablock.njabl.org: assumed not in list
Aug 8 18:17:15 medved exim[20796]: 2008-08-08 18:17:15 Delay 20s for webmail11.yandex.ru [213.180.200.52] with HELO=webmail11.yandex.ru. Mail from Pupkin@yandex.ru to pupkin@mydomain.ru.
Aug 8 18:17:35 medved exim[20796]: 2008-08-08 18:17:35 1KRP2N-0005PQ-FD malware acl condition: clamd: invalid socket 'var/run/clamav/clamd.sock'
Aug 8 18:17:35 medved exim[20796]: 2008-08-08 18:17:35 1KRP2N-0005PQ-FD malware acl condition: clamd: invalid socket 'var/run/clamav/clamd.sock'
Aug 8 18:17:35 medved exim[20796]: 2008-08-08 18:17:35 1KRP2N-0005PQ-FD H=webmail11.yandex.ru [213.180.200.52] I=[213.24.155.53]:25 F=<Pupkin@yandex.ru> temporarily rejected after DATA
Aug 8 18:17:35 medved exim[20796]: [1\22] 2008-08-08 18:17:35 1KRP2N-0005PQ-FD H=webmail11.yandex.ru [213.180.200.52] I=[213.24.155.53]:25 F=<Pupkin@yandex.ru> temporarily rejected after DATA
Aug 8 18:17:35 medved exim[20796]: [2\22] Envelope-from: <Pupkin@yandex.ru>
Aug 8 18:17:35 medved exim[20796]: [3\22] Envelope-to: <pupkin@mydomain.ru>
Aug 8 18:17:35 medved exim[20796]: [4\22] P Received: from webmail11.yandex.ru ([213.180.200.52])
Aug 8 18:17:35 medved exim[20796]: [5\22] by mail.mydomain.ru with esmtp (Exim 4.68 (FreeBSD))
Aug 8 18:17:35 medved exim[20796]: [6\22] (envelope-from <Pupkin@yandex.ru>)
Aug 8 18:17:35 medved exim[20796]: [7\22] id 1KRP2N-0005PQ-FD
Aug 8 18:17:35 medved exim[20796]: [8\22] for pupkin@mydomain.ru; Fri, 08 Aug 2008 18:17:35 +0800
Aug 8 18:17:35 medved exim[20796]: [9\22] P Received: from YAMAIL (webmail11) by mail.yandex.ru id S2999428AbYHHHbP for
Aug 8 18:17:35 medved exim[20796]: [10\22] <pupkin@mydomain.ru>; Fri, 8 Aug 2008 11:31:15 +0400
Aug 8 18:17:35 medved exim[20796]: [11\22] X-Yandex-Spam: 1
Aug 8 18:17:35 medved exim[20796]: [12\22] P Received: from [213.24.155.53] ([213.24.155.53]) by mail.yandex.ru with HTTP;
Aug 8 18:17:35 medved exim[20796]: [13\22] Fri, 08 Aug 2008 11:31:15 +0400
Aug 8 18:17:35 medved exim[20796]: [14\22] F From: St Danila <Pupkin@yandex.ru>
Aug 8 18:17:35 medved exim[20796]: [15\22] T To: pupkin@mydomain.ru
Aug 8 18:17:35 medved exim[20796]: [16\22] Subject: test
Aug 8 18:17:35 medved exim[20796]: [17\22] MIME-Version: 1.0
Aug 8 18:17:35 medved exim[20796]: [18\22] I Message-Id: <674161218180675@webmail11.yandex.ru>
Aug 8 18:17:35 medved exim[20796]: [19\22] Date: Fri, 08 Aug 2008 11:31:15 +0400
Aug 8 18:17:35 medved exim[20796]: [20\22] X-Mailer: Yamail [ http://yandex.ru ] 5.0
Aug 8 18:17:35 medved exim[20796]: [21\22] Content-Transfer-Encoding: 8bit
Aug 8 18:17:35 medved exim[20796]: [22/22] Content-Type: text/plain; charset=KOI8-R
В чем собака зарыта? Что значят эти сообщения? Если не сложно, опишите поподробнее плиз!!!

Далее ставлю courier-imap, рихтую конфиг авторизации. Набираю

./couruer-authdaemond start
./sockstat | grep authd
а фиг вам - не запускается он. Опять же в чем может бять причина? Может косячу в синтаксисе? Имеется ли возможность где-нибудь посмотреть его логи, в которых написано что его не устраивает? На всякий случай мой конфиг

Код: Выделить всё

#!/bin/sh
##VERSION: $Id: authmysqlrc,v 1.20 2007/10/07 02:50:45 mrsam Exp $
#
# Copyright 2000-2007 Double Precision, Inc. See COPYING for
# distribution information.
#
# Do not alter lines that begin with ##, they are used when upgrading
# this configuration.
#
# authmysqlrc created from authmysqlrc.dist by sysconftool
#
# DO NOT INSTALL THIS FILE with world read permissions. This file
# might contain the MySQL admin password!
#
# Each line in this file must follow the following format:
#
# field[spaces|tabs]value
#
# That is, the name of the field, followed by spaces or tabs, followed by
# field value. Trailing spaces are prohibited.


##NAME: LOCATION:0
#
# The server name, userid, and password used to log in.

MYSQL_SERVER localhost
MYSQL_USERNAME exim
MYSQL_PASSWORD exim

##NAME: SSLINFO:0
#
# The SSL information.
#
# To use SSL-encrypted connections, define the following variables (available
# in MySQL 4.0, or higher):
#
#
# MYSQL_SSL_KEY /path/to/file
# MYSQL_SSL_CERT /path/to/file
# MYSQL_SSL_CACERT /path/to/file
# MYSQL_SSL_CAPATH /path/to/file
# MYSQL_SSL_CIPHERS ALL:!DES

##NAME: MYSQL_SOCKET:0
#
# MYSQL_SOCKET can be used with MySQL version 3.22 or later, it specifies the
# filesystem pipe used for the connection
#
# MYSQL_SOCKET /var/mysql/mysql.sock

##NAME: MYSQL_PORT:0
#
# MYSQL_PORT can be used with MySQL version 3.22 or later to specify a port to
# connect to.

MYSQL_PORT 3306

##NAME: MYSQL_OPT:0
#
# Leave MYSQL_OPT as 0, unless you know what you're doing.

MYSQL_OPT 0

##NAME: MYSQL_DATABASE:0
#
# The name of the MySQL database we will open:

MYSQL_DATABASE exim

#NAME: MYSQL_CHARACTER_SET:0
#
# This is optional. MYSQL_CHARACTER_SET installs a character set. This option
# can be used with MySQL version 4.1 or later. MySQL supports 70+ collations
# for 30+ character sets. See MySQL documentations for more detalis.
#
# MYSQL_CHARACTER_SET latin1

##NAME: MYSQL_USER_TABLE:0
#
# The name of the table containing your user data. See README.authmysqlrc
# for the required fields in this table.

MYSQL_USER_TABLE mailbox

##NAME: MYSQL_CRYPT_PWFIELD:0
#
# Either MYSQL_CRYPT_PWFIELD or MYSQL_CLEAR_PWFIELD must be defined. Both
# are OK too. crypted passwords go into MYSQL_CRYPT_PWFIELD, cleartext
# passwords go into MYSQL_CLEAR_PWFIELD. Cleartext passwords allow
# CRAM-MD5 authentication to be implemented.

#MYSQL_CRYPT_PWFIELD password

##NAME: MYSQL_CLEAR_PWFIELD:0
#
#
MYSQL_CLEAR_PWFIELD password

##NAME: MYSQL_DEFAULT_DOMAIN:0
#
# If DEFAULT_DOMAIN is defined, and someone tries to log in as 'user',
# we will look up 'user@DEFAULT_DOMAIN' instead.
#
#
DEFAULT_DOMAIN mydomain.ru

##NAME: MYSQL_UID_FIELD:0
#
# Other fields in the mysql table:
#
# MYSQL_UID_FIELD - contains the numerical userid of the account
#
MYSQL_UID_FIELD 26

##NAME: MYSQL_GID_FIELD:0
#
# Numerical groupid of the account

MYSQL_GID_FIELD 26

##NAME: MYSQL_LOGIN_FIELD:0
#
# The login id, default is id. Basically the query is:
#
# SELECT MYSQL_UID_FIELD, MYSQL_GID_FIELD, ... WHERE id='loginid'
#

MYSQL_LOGIN_FIELD username

##NAME: MYSQL_HOME_FIELD:0
#

MYSQL_HOME_FIELD CONCAT('/var/mail/exim', maildir)

##NAME: MYSQL_NAME_FIELD:0
#
# The user's name (optional)

MYSQL_NAME_FIELD name

##NAME: MYSQL_MAILDIR_FIELD:0
#
# This is an optional field, and can be used to specify an arbitrary
# location of the maildir for the account, which normally defaults to
# $HOME/Maildir (where $HOME is read from MYSQL_HOME_FIELD).
#
# You still need to provide a MYSQL_HOME_FIELD, even if you uncomment this
# out.
#
MYSQL_MAILDIR_FIELD CONCAT('/var/mail/exim/', maildir)
и прилагаю конфиг екзима:

Код: Выделить всё

#!/bin/sh
# $Cambridge: exim/exim-src/src/configure.default,v 1.13 2007/06/26 11:21:36 ph10 Exp $

######################################################################
#                  Runtime configuration file for Exim               #
######################################################################


# This is a default configuration file which will operate correctly in
# uncomplicated installations. Please see the manual for a complete list
# of all the runtime configuration options that can be included in a
# configuration file. There are many more than are mentioned here. The
# manual is in the file doc/spec.txt in the Exim distribution as a plain
# ASCII file. Other formats (PostScript, Texinfo, HTML, PDF) are available
# from the Exim ftp sites. The manual is also online at the Exim web sites.


# This file is divided into several parts, all but the first of which are
# headed by a line starting with the word "begin". Only those parts that
# are required need to be present. Blank lines, and lines starting with #
# are ignored.


########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ###########
#                                                                          #
# Whenever you change Exim's configuration file, you *must* remember to    #
# HUP the Exim daemon, because it will not pick up the new configuration   #
# until you do. However, any other Exim processes that are started, for    #
# example, a process started by an MUA in order to send a message, will    #
# see the new configuration as soon as it is in place.                     #
#                                                                          #
# You do not need to HUP the daemon for changes in auxiliary files that    #
# are referenced from this file. They are read every time they are used.   #
#                                                                          #
# It is usually a good idea to test a new configuration for syntactic      #
# correctness before installing it (for example, by running the command    #
# "exim -C /config/file.new -bV").                                         #
#                                                                          #
########### IMPORTANT ########## IMPORTANT ########### IMPORTANT ###########



######################################################################
#                    MAIN CONFIGURATION SETTINGS                     #
######################################################################

# Specify your host's canonical name here. This should normally be the fully
# qualified "official" name of your host. If this option is not set, the
# uname() function is called to obtain the name. In many cases this does
# the right thing and you need not set anything explicitly.

primary_hostname = mail.myserver.ru

hide mysql_servers = localhost/exim/exim/exim

# The next three settings create two lists of domains and one list of hosts.
# These lists are referred to later in this configuration using the syntax
# +local_domains, +relay_to_domains, and +relay_from_hosts, respectively. They
# are all colon-separated lists:

domainlist local_domains = ${lookup mysql{SELECT domain FROM domain WHERE domain='${domain}' AND active=1}}
domainlist relay_to_domains =${lookup mysql{SELECT domain FROM domain WHERE domain='${'domain}' AND active=1}}
hostlist   relay_from_hosts = localhost:127.0.0.0/8:192.168.16.0/24

# Most straightforward access control requirements can be obtained by
# appropriate settings of the above options. In more complicated situations,
# you may need to modify the Access Control Lists (ACLs) which appear later in
# this file.

# The first setting specifies your local domains, for example:
#
#   domainlist local_domains = my.first.domain : my.second.domain
#
# You can use "@" to mean "the name of the local host", as in the default
# setting above. This is the name that is specified by primary_hostname,
# as specified above (or defaulted). If you do not want to do any local
# deliveries, remove the "@" from the setting above. If you want to accept mail
# addressed to your host's literal IP address, for example, mail addressed to
# "user@[192.168.23.44]", you can add "@[]" as an item in the local domains
# list. You also need to uncomment "allow_domain_literals" below. This is not
# recommended for today's Internet.

# The second setting specifies domains for which your host is an incoming relay.
# If you are not doing any relaying, you should leave the list empty. However,
# if your host is an MX backup or gateway of some kind for some domains, you
# must set relay_to_domains to match those domains. For example:
#
# domainlist relay_to_domains = *.myco.com : my.friend.org
#
# This will allow any host to relay through your host to those domains.
# See the section of the manual entitled "Control of relaying" for more
# information.

# The third setting specifies hosts that can use your host as an outgoing relay
# to any other host on the Internet. Such a setting commonly refers to a
# complete local network as well as the localhost. For example:
#
# hostlist relay_from_hosts = 127.0.0.1 : 192.168.0.0/16
#
# The "/16" is a bit mask (CIDR notation), not a number of hosts. Note that you
# have to include 127.0.0.1 if you want to allow processes on your host to send
# SMTP mail by using the loopback address. A number of MUAs use this method of
# sending mail.

# All three of these lists may contain many different kinds of item, including
# wildcarded names, regular expressions, and file lookups. See the reference
# manual for details. The lists above are used in the access control lists for
# checking incoming messages. The names of these ACLs are defined here:

acl_smtp_rcpt = acl_check_rcpt
acl_smtp_data = acl_check_data

# You should not change those settings until you understand how ACLs work.


# If you are running a version of Exim that was compiled with the content-
# scanning extension, you can cause incoming messages to be automatically
# scanned for viruses. You have to modify the configuration in two places to
# set this up. The first of them is here, where you define the interface to
# your scanner. This example is typical for ClamAV; see the manual for details
# of what to set for other virus scanners. The second modification is in the
# acl_check_data access control list (see below).

av_scanner = clamd:var/run/clamav/clamd.sock


# For spam scanning, there is a similar option that defines the interface to
# SpamAssassin. You do not need to set this if you are using the default, which
# is shown in this commented example. As for virus scanning, you must also
# modify the acl_check_data access control list to enable spam scanning.

# spamd_address = 127.0.0.1 783


# If Exim is compiled with support for TLS, you may want to enable the
# following options so that Exim allows clients to make encrypted
# connections. In the authenticators section below, there are template
# configurations for plaintext username/password authentication. This kind
# of authentication is only safe when used within a TLS connection, so the
# authenticators will only work if the following TLS settings are turned on
# as well.

# Allow any client to use TLS.

# tls_advertise_hosts = *

# Specify the location of the Exim server's TLS certificate and private key.
# The private key must not be encrypted (password protected). You can put
# the certificate and private key in the same file, in which case you only
# need the first setting, or in separate files, in which case you need both
# options.

# tls_certificate = /etc/ssl/exim.crt
# tls_privatekey = /etc/ssl/exim.pem

# In order to support roaming users who wish to send email from anywhere,
# you may want to make Exim listen on other ports as well as port 25, in
# case these users need to send email from a network that blocks port 25.
# The standard port for this purpose is port 587, the "message submission"
# port. See RFC 4409 for details. Microsoft MUAs cannot be configured to
# talk the message submission protocol correctly, so if you need to support
# them you should also allow TLS-on-connect on the traditional but
# non-standard port 465.

# daemon_smtp_ports = 25 : 465 : 587
# tls_on_connect_ports = 465


# Specify the domain you want to be added to all unqualified addresses
# here. An unqualified address is one that does not contain an "@" character
# followed by a domain. For example, "caesar@rome.example" is a fully qualified
# address, but the string "caesar" (i.e. just a login name) is an unqualified
# email address. Unqualified addresses are accepted only from local callers by
# default. See the recipient_unqualified_hosts option if you want to permit
# unqualified addresses from remote sources. If this option is not set, the
# primary_hostname value is used for qualification.

qualify_domain = mydomain.ru


# If you want unqualified recipient addresses to be qualified with a different
# domain to unqualified sender addresses, specify the recipient domain here.
# If this option is not set, the qualify_domain value is used.

qualify_recipient = mydomain.ru


# The following line must be uncommented if you want Exim to recognize
# addresses of the form "user@[10.11.12.13]" that is, with a "domain literal"
# (an IP address) instead of a named domain. The RFCs still require this form,
# but it makes little sense to permit mail to be sent to specific hosts by
# their IP address in the modern Internet. This ancient format has been used
# by those seeking to abuse hosts by using them for unwanted relaying. If you
# really do want to support domain literals, uncomment the following line, and
# see also the "domain_literal" router below.

allow_domain_literals = false


# No deliveries will ever be run under the uids of users specified by
# never_users (a colon-separated list). An attempt to do so causes a panic
# error to be logged, and the delivery to be deferred. This is a paranoic
# safety catch. There is an even stronger safety catch in the form of the
# FIXED_NEVER_USERS setting in the configuration for building Exim. The list of
# users that it specifies is built into the binary, and cannot be changed. The
# option below just adds additional users to the list. The default for
# FIXED_NEVER_USERS is "root", but just to be absolutely sure, the default here
# is also "root".

# Note that the default setting means you cannot deliver mail addressed to root
# as if it were a normal user. This isn't usually a problem, as most sites have
# an alias for root that redirects such mail to a human administrator.

exim_user = mailnull
exim_group = mail
never_users = root


# The setting below causes Exim to do a reverse DNS lookup on all incoming
# IP calls, in order to get the true host name. If you feel this is too
# expensive, you can specify the networks for which a lookup is done, or
# remove the setting entirely.

host_lookup = *


# The settings below, which are actually the same as the defaults in the
# code, cause Exim to make RFC 1413 (ident) callbacks for all incoming SMTP
# calls. You can limit the hosts to which these calls are made, and/or change
# the timeout that is used. If you set the timeout to zero, all RFC 1413 calls
# are disabled. RFC 1413 calls are cheap and can provide useful information
# for tracing problem messages, but some hosts and firewalls have problems
# with them. This can result in a timeout instead of an immediate refused
# connection, leading to delays on starting up SMTP sessions. (The default was
# reduced from 30s to 5s for release 4.61.)

#rfc1413_hosts = *
rfc1413_query_timeout = 5s


# By default, Exim expects all envelope addresses to be fully qualified, that
# is, they must contain both a local part and a domain. If you want to accept
# unqualified addresses (just a local part) from certain hosts, you can specify
# these hosts by setting one or both of
#
# sender_unqualified_hosts =
# recipient_unqualified_hosts =
#
# to control sender and recipient addresses, respectively. When this is done,
# unqualified addresses are qualified using the settings of qualify_domain
# and/or qualify_recipient (see above).


# If you want Exim to support the "percent hack" for certain domains,
# uncomment the following line and provide a list of domains. The "percent
# hack" is the feature by which mail addressed to x%y@z (where z is one of
# the domains listed) is locally rerouted to x@y and sent on. If z is not one
# of the "percent hack" domains, x%y is treated as an ordinary local part. This
# hack is rarely needed nowadays; you should not enable it unless you are sure
# that you really need it.
#
# percent_hack_domains =
#
# As well as setting this option you will also need to remove the test
# for local parts containing % in the ACL definition below.


# When Exim can neither deliver a message nor return it to sender, it "freezes"
# the delivery error message (aka "bounce message"). There are also other
# circumstances in which messages get frozen. They will stay on the queue for
# ever unless one of the following options is set.

# This option unfreezes frozen bounce messages after two days, tries
# once more to deliver them, and ignores any delivery failures.

ignore_bounce_errors_after = 45m

# This option cancels (removes) frozen messages that are older than a week.

timeout_frozen_after = 7d


# By default, messages that are waiting on Exim's queue are all held in a
# single directory called "input" which it itself within Exim's spool
# directory. (The default spool directory is specified when Exim is built, and
# is often /var/spool/exim/.) Exim works best when its queue is kept short, but
# there are circumstances where this is not always possible. If you uncomment
# the setting below, messages on the queue are held in 62 subdirectories of
# "input" instead of all in the same directory. The subdirectories are called
# 0, 1, ... A, B, ... a, b, ... z. This has two benefits: (1) If your file
# system degrades with many files in one directory, this is less likely to
# happen; (2) Exim can process the queue one subdirectory at a time instead of
# all at once, which can give better performance with large queues.

# split_spool_directory = true

helo_accept_junk_hosts = 192.168.16.0/24

auto_thaw = 1h

smtp_banner = "$primary_hostname, ESMTP EXIM $version_number"

smtp_accept_max = 35

smtp_accept_max_per_connection = 25

smtp_connect_backlog = 30

smtp_accept_max_per_host = 20

split_spool_directory = true

remote_max_parallel = 15

return_size_limit = 70k

message_size_limit = 10M

helo_allow_chars = _

smtp_enforce_sync = true

log_selector = \
    +all_parents \ 
    +connection_reject \
    +incoming_interface \
    +lost_incoming_connection \
    +received_sender \
    +received_recipients \
    +smtp_confirmation \
    +smtp_syntax_error \
    +smtp_protocol_error \
    -queue_run
    
#syslog_tymestamp = no

######################################################################
#                       ACL CONFIGURATION                            #
#         Specifies access control lists for incoming SMTP mail      #
######################################################################

begin acl

# This access control list is used for every RCPT command in an incoming
# SMTP message. The tests are run in order until the address is either
# accepted or denied.

acl_check_rcpt:

  # Accept if the source is local SMTP (i.e. not over TCP/IP). We do this by
  # testing for an empty sending host field.

  accept  hosts = :

  #############################################################################
  # The following section of the ACL is concerned with local parts that contain
  # @ or % or ! or / or | or dots in unusual places.
  #
  # The characters other than dots are rarely found in genuine local parts, but
  # are often tried by people looking to circumvent relaying restrictions.
  # Therefore, although they are valid in local parts, these rules lock them
  # out, as a precaution.
  #
  # Empty components (two dots in a row) are not valid in RFC 2822, but Exim
  # allows them because they have been encountered. (Consider local parts
  # constructed as "firstinitial.secondinitial.familyname" when applied to
  # someone like me, who has no second initial.) However, a local part starting
  # with a dot or containing /../ can cause trouble if it is used as part of a
  # file name (e.g. for a mailing list). This is also true for local parts that
  # contain slashes. A pipe symbol can also be troublesome if the local part is
  # incorporated unthinkingly into a shell command line.
  #
  # Two different rules are used. The first one is stricter, and is applied to
  # messages that are addressed to one of the local domains handled by this
  # host. The line "domains = +local_domains" restricts it to domains that are
  # defined by the "domainlist local_domains" setting above. The rule  blocks
  # local parts that begin with a dot or contain @ % ! / or |. If you have
  # local accounts that include these characters, you will have to modify this
  # rule.

  deny    message       = "оЕДПРХУФЙНЩЕ УЙНЧПМЩ Ч БДТЕУЕ"
          domains       = +local_domains
          local_parts   = ^[.] : ^.*[@%!/|]

  # The second rule applies to all other domains, and is less strict. The line
  # "domains = !+local_domains" restricts it to domains that are NOT defined by
  # the "domainlist local_domains" setting above. The exclamation mark is a
  # negating operator. This rule allows your own users to send outgoing
  # messages to sites that use slashes and vertical bars in their local parts.
  # It blocks local parts that begin with a dot, slash, or vertical bar, but
  # allows these characters within the local part. However, the sequence /../
  # is barred. The use of @ % and ! is blocked, as before. The motivation here
  # is to prevent your users (or your users' viruses) from mounting certain
  # kinds of attack on remote sites.

  deny    message       = "оЕДПРХУФЙНЩЕ УЙНЧПМЩ Ч БДТЕУЕ"
          domains       = !+local_domains
          local_parts   = ^[./|] : ^.*[@%!] : ^.*/\\.\\./
  #############################################################################

  # Accept mail to postmaster in any local domain, regardless of the source,
  # and without verifying the sender.

#  accept  local_parts   = postmaster
#          domains       = +local_domains

  # Deny unless the sender address can be verified.

  require verify        = sender

  deny	message		= "HELLO/EHLO ПВСЪБОП ВЩФШ РП SMTP RFC"
	condition	= ${if eq{$sender_helo_name}{}{yes}{no}}

  # Accept if the message comes from one of the hosts for which we are an
  # outgoing relay. It is assumed that such hosts are most likely to be MUAs,
  # so we set control=submission to make Exim treat the message as a
  # submission. It will fix up various errors in the message, for example, the
  # lack of a Date: header line. If you are actually relaying out out from
  # MTAs, you may want to disable this. If you are handling both relaying from
  # MTAs and submissions from MUAs you should probably split them into two
  # lists, and handle them differently.

  # Recipient verification is omitted here, because in many cases the clients
  # are dumb MUAs that don't cope well with SMTP error responses. If you are
  # actually relaying out from MTAs, you should probably add recipient
  # verification here.

  # Note that, by putting this test before any DNS black list checks, you will
  # always accept from these hosts, even if they end up on a black list. The
  # assumption is that they are your friends, and if they get onto a black
  # list, it is a mistake.

  accept  hosts         = +relay_from_hosts
  #        control       = submission

  # Accept if the message arrived over an authenticated connection, from
  # any host. Again, these messages are usually from MUAs, so recipient
  # verification is omitted, and submission mode is set. And again, we do this
  # check before any black list tests.

  accept  authenticated = *
  #        control       = submission

  # Рубаем нах, тех, кто подставляет свой IP в HELO
  deny    message       = "ne stav IP  HELO!"
          hosts         =  *:!+relay_from_hosts
          condition     = ${if eq{$sender_helo_name}\
                          {$sender_host_address}{true}{false}}


# Рубаем тех, кто в HELO пихает мой IP (2500 за месяц!)
  deny    condition     = ${if eq{$sender_helo_name}\
                          {$interface_address}{yes}{no}}
          hosts         = !127.0.0.1 : !localhost : *
          message       = "this is my IP! fuck off!"

# Рубаем тех, кто в HELO пихает только цифры
# (не бывает хостов ТОЛЬКО из цифр)
  deny    condition     = ${if match{$sender_helo_name}\
                          {\N^\d+$\N}{yes}{no}}
          hosts         = !127.0.0.1:!localhost:*
          message       = "v HELO ne moget bit tolko cifr!"

  # Рубаем хосты типа *adsl*; *dialup*; *pool*;....
  # Нормальные люди с таких не пишут. Если будут
  # проблемы - уберёте проблемный пункт (у меня клиенты
  # имеют запись типа asdl-1233.zone.su - я ADSL убрал...)
  deny    message       = "fuck off..."
          condition     = ${if match{$sender_host_name} \
                               {adsl|dialup|pool|peer|dhcp} \
                               {yes}{no}}
  # Рубаем тех, кто в блэк-листах. Серваки перебираются
  # сверху вниз, если не хост не найден на первом, то
  # запрашивается второй, и т.д. Если не найден ни в одном
  # из списка - то почта пропускается.
  deny    message       = "host in blacklist - $dnslist_domain \n $dnslist_text"
          dnslists      = opm.blitzed.org : \
                          proxies.blackholes.easynet.nl : \
                          cbl.abuseat.org : \
                          bl.spamcop.net : \
                          bl.csma.biz : \
                          dynablock.njabl.org : \
  
  # Insist that any other recipient address that we accept is either in one of
  # our local domains, or is in a domain for which we explicitly allow
  # relaying. Any other domain is rejected as being unacceptable for relaying.

  require message = relay not permitted
          domains = +local_domains : +relay_to_domains

  # We also require all accepted addresses to be verifiable. This check will
  # do local part verification for local domains, but only check the domain
  # for remote domains. The only way to check local parts for the remote
  # relay domains is to use a callout (add /callout), but please read the
  # documentation about callouts before doing this.

  require verify = recipient

  #############################################################################
  # There are no default checks on DNS black lists because the domains that
  # contain these lists are changing all the time. However, here are two
  # examples of how you can get Exim to perform a DNS black list lookup at this
  # point. The first one denies, whereas the second just warns.
  #
  # deny    message       = rejected because $sender_host_address is in a black list at $dnslist_domain\n$dnslist_text
  #         dnslists      = black.list.example
  #
  # warn    dnslists      = black.list.example
  #         add_header    = X-Warning: $sender_host_address is in a black list at $dnslist_domain
  #         log_message   = found in $dnslist_domain
  #############################################################################

  #############################################################################
  # This check is commented out because it is recognized that not every
  # sysadmin will want to do it. If you enable it, the check performs
  # Client SMTP Authorization (csa) checks on the sending host. These checks
  # do DNS lookups for SRV records. The CSA proposal is currently (May 2005)
  # an Internet draft. You can, of course, add additional conditions to this
  # ACL statement to restrict the CSA checks to certain hosts only.
  #
  # require verify = csa
  #############################################################################

  # At this point, the address has passed all the checks that have been
  # configured, so we accept it unconditionally.

  #accept
  
  # Задержка. (это такой метод борьбы со спамом,
  # основанный на принципе его рассылки) На этом рубается
  # почти весь спам. Единственно - метод неприменим на
  # реально загруженных MTA - т.к. в результате ему
  # приходится держать много открытых соединений.
  # но на офисе в сотню-две человек - шикарный метод.
  #
  # более сложный вариант, смотрите в статье по exim и
  # курьер имап. Т.к. там метод боле умный (просто правил
  # больше :), то можно и на более загруженные сервера ставить)
  warn
        # ставим дефолтовую задержку в 20 секунд
        set acl_m0 = 20s
  warn
        # ставим задержку в 0 секунд своим хостам и
        # дружественным сетям (соседняя контора :))
        hosts = +relay_from_hosts :172.0.0.0/8
        set acl_m0 = 0s
  warn
        # пишем в логи задержку (если оно вам надо)
        logwrite = Delay $acl_m0 for $sender_host_name \
		[$sender_host_address] with HELO=$sender_helo_name. Mail \
		from $sender_address to $local_part@$domain.
        delay = $acl_m0







  # Проверка получателя в локальных доменах.
  # Если не проходит, то проверяется следующий ACL,
  # и если непрошёл и там - deny
  accept  domains       = +local_domains
          endpass
          message       = "no this user in domen"
          verify        = recipient

  # Проверяем получателя в релейных доменах
  # Опять-таки если не проходит -> следующий ACL,
  # и если непрошёл и там - deny
  accept  domains       = +relay_to_domains
          endpass
          message       = "no route to host..."
          verify        = recipient

  # Разрешаем почту от доменов в списке relay_from_hosts
  accept  hosts         = +relay_from_hosts

  # Если неподошло ни одно правило - чувак явно ищет
  # открытый релей. Пшёл прочь. :)
  deny    message       = "this is not open relay."


# This ACL is used after the contents of a message have been received. This
# is the ACL in which you can test a message's headers or body, and in
# particular, this is where you can invoke external virus or spam scanners.
# Some suggested ways of configuring these tests are shown below, commented
# out. Without any tests, this ACL accepts all messages. If you want to use
# such tests, you must ensure that Exim is compiled with the content-scanning
# extension (WITH_CONTENT_SCAN=yes in Local/Makefile).

acl_check_data:

  # Deny if the message contains a virus. Before enabling this check, you
  # must install a virus scanner and set the av_scanner option above.
  #
  # deny    malware    = *
  #         message    = This message contains a virus ($malware_name).
	
  # Проверяем письмо на вирусы
  deny malware = *
  message = "In e-mail found VIRUS - $malware_name"

  # Если есть необходимость - тут проверки на спам
	
  # Add headers to a message if it is judged to be spam. Before enabling this,
  # you must install SpamAssassin. You may also need to set the spamd_address
  # option above.
  #
  # warn    spam       = nobody
  #         add_header = X-Spam_score: $spam_score\n\
  #                      X-Spam_score_int: $spam_score_int\n\
  #                      X-Spam_bar: $spam_bar\n\
  #                      X-Spam_report: $spam_report

  # Accept the message.

  # Пропускаем остальное
  accept



######################################################################
#                      ROUTERS CONFIGURATION                         #
#               Specifies how addresses are handled                  #
######################################################################
#     THE ORDER IN WHICH THE ROUTERS ARE DEFINED IS IMPORTANT!       #
# An address is passed to each router in turn until it is accepted.  #
######################################################################

begin routers

# This router routes to remote hosts over SMTP by explicit IP address,
# when an email address is given in "domain literal" form, for example,
# <user@[192.168.35.64]>. The RFCs require this facility. However, it is
# little-known these days, and has been exploited by evil people seeking
# to abuse SMTP relays. Consequently it is commented out in the default
# configuration. If you uncomment this router, you also need to uncomment
# allow_domain_literals above, so that Exim can recognize the syntax of
# domain literal addresses.

# domain_literal:
#   driver = ipliteral
#   domains = ! +local_domains
#   transport = remote_smtp


# This router routes addresses that are not in local domains by doing a DNS
# lookup on the domain name. The exclamation mark that appears in "domains = !
# +local_domains" is a negating operator, that is, it can be read as "not". The
# recipient's domain must not be one of those defined by "domainlist
# local_domains" above for this router to be used.
#
# If the router is used, any domain that resolves to 0.0.0.0 or to a loopback
# interface address (127.0.0.0/8) is treated as if it had no DNS entry. Note
# that 0.0.0.0 is the same as 0.0.0.0/32, which is commonly treated as the
# local host inside the network stack. It is not 0.0.0.0/0, the default route.
# If the DNS lookup fails, no further routers are tried because of the no_more
# setting, and consequently the address is unrouteable.

dnslookup:
  driver = dnslookup
  domains = ! +local_domains
  transport = remote_smtp
  ignore_target_hosts = 0.0.0.0 : 127.0.0.0/8
  no_more

system_aliases:
    driver      = redirect
    allow_fail
    allow_defer
    data = ${lookup mysql{SELECT `goto` FROM `alias` WHERE \
           `address`='${quote_mysql:$local_part@$domain}' OR \
           `address`='${quote_mysql:@$domain}'}}

mysqluser:
  driver = accept
  condition = ${if eq{}{${lookup mysql{SELECT `maildir` FROM `mailbox` \
              WHERE `username`='${quote_mysql:$local_part@$domain}'}}}{no}{yes}}
  transport = mysql_delivery


# The remaining routers handle addresses in the local domain(s), that is those
# domains that are defined by "domainlist local_domains" above.


# This router handles aliasing using a linearly searched alias file with the
# name /etc/aliases. When this configuration is installed automatically,
# the name gets inserted into this file from whatever is set in Exim's
# build-time configuration. The default path is the traditional /etc/aliases.
# If you install this configuration by hand, you need to specify the correct
# path in the "data" setting below.
#
##### NB  You must ensure that the alias file exists. It used to be the case
##### NB  that every Unix had that file, because it was the Sendmail default.
##### NB  These days, there are systems that don't have it. Your aliases
##### NB  file should at least contain an alias for "postmaster".
#
# If any of your aliases expand to pipes or files, you will need to set
# up a user and a group for these deliveries to run under. You can do
# this by uncommenting the "user" option below (changing the user name
# as appropriate) and adding a "group" option if necessary. Alternatively, you
# can specify "user" on the transports that are used. Note that the transports
# listed below are the same as are used for .forward files; you might want
# to set up different ones for pipe and file deliveries from aliases.

#system_aliases:
#  driver = redirect
 # allow_fail
  #allow_defer
  #data = ${lookup{$local_part}lsearch{/etc/aliases}}
  #user = mailnull
  #group = mail
  #file_transport = address_file
  #pipe_transport = address_pipe


# This router handles forwarding using traditional .forward files in users'
# home directories. If you want it also to allow mail filtering when a forward
# file starts with the string "# Exim filter" or "# Sieve filter", uncomment
# the "allow_filter" option.

# If you want this router to treat local parts with suffixes introduced by "-"
# or "+" characters as if the suffixes did not exist, uncomment the two local_
# part_suffix options. Then, for example, xxxx-foo@your.domain will be treated
# in the same way as xxxx@your.domain by this router. You probably want to make
# the same change to the localuser router.

# The no_verify setting means that this router is skipped when Exim is
# verifying addresses. Similarly, no_expn means that this router is skipped if
# Exim is processing an EXPN command.

# The check_ancestor option means that if the forward file generates an
# address that is an ancestor of the current one, the current one gets
# passed on instead. This covers the case where A is aliased to B and B
# has a .forward file pointing to A.

# The three transports specified at the end are those that are used when
# forwarding generates a direct delivery to a file, or to a pipe, or sets
# up an auto-reply, respectively.

#userforward:
#  driver = redirect
#  check_local_user
# local_part_suffix = +* : -*
# local_part_suffix_optional
#  file = $home/.forward
# allow_filter
#  no_verify
#  no_expn
#  check_ancestor
#  file_transport = address_file
#  pipe_transport = address_pipe
#  reply_transport = address_reply
#  condition = ${if exists{$home/.forward} {yes} {no} }


# This router matches local user mailboxes. If the router fails, the error
# message is "Unknown user".

# If you want this router to treat local parts with suffixes introduced by "-"
# or "+" characters as if the suffixes did not exist, uncomment the two local_
# part_suffix options. Then, for example, xxxx-foo@your.domain will be treated
# in the same way as xxxx@your.domain by this router.

#localuser:
#  driver = accept
#  check_local_user
# local_part_suffix = +* : -*
# local_part_suffix_optional
#  transport = local_delivery
#  cannot_route_message = Unknown user



######################################################################
#                      TRANSPORTS CONFIGURATION                      #
######################################################################
#                       ORDER DOES NOT MATTER                        #
#     Only one appropriate transport is called for each delivery.    #
######################################################################

# A transport is used only when referenced from a router that successfully
# handles an address.

begin transports


# This transport is used for delivering messages over SMTP connections.

remote_smtp:
  driver = smtp


# This transport is used for local delivery to user mailboxes in traditional
# BSD mailbox format. By default it will be run under the uid and gid of the
# local user, and requires the sticky bit to be set on the /var/mail directory.
# Some systems use the alternative approach of running mail deliveries under a
# particular group instead of using the sticky bit. The commented options below
# show how this can be done.

local_delivery:
  driver = appendfile
  file = /var/mail/$local_part
  delivery_date_add
  envelope_to_add
  return_path_add
  group = mail
  user = $local_part
  mode = 0660
  no_mode_fail_narrower

mysql_delivery:
    driver = appendfile
    check_string = ""
    create_directory
    delivery_date_add
    directory = ${lookup mysql{SELECT CONCAT('/var/mail/exim/', `maildir`) \
                FROM `mailbox` WHERE `username`='${local_part}@${domain}'}}
    directory_mode = 770
    envelope_to_add
    group = mail
    maildir_format
    maildir_tag = ,S=$message_size
    message_prefix = ""
    message_suffix = ""
    mode = 0600
	


# This transport is used for handling pipe deliveries generated by alias or
# .forward files. If the pipe generates any standard output, it is returned
# to the sender of the message as a delivery error. Set return_fail_output
# instead of return_output if you want this to happen only when the pipe fails
# to complete normally. You can set different transports for aliases and
# forwards if you want to - see the references to address_pipe in the routers
# section above.

address_file:
    driver = appendfile
    delivery_date_add
    envelope_to_add
    return_path_add

# Имя программы
address_pipe:
  driver = pipe
  return_output

# Транспорт для автоответов
address_reply:
  driver = autoreply



######################################################################
#                      RETRY CONFIGURATION                           #
######################################################################

begin retry

# This single retry rule applies to all domains and all errors. It specifies
# retries every 15 minutes for 2 hours, then increasing retry intervals,
# starting at 1 hour and increasing each time by a factor of 1.5, up to 16
# hours, then retries every 6 hours until 4 days have passed since the first
# failed delivery.

# WARNING: If you do not have any retry rules at all (this section of the
# configuration is non-existent or empty), Exim will not do any retries of
# messages that fail to get delivered at the first attempt. The effect will
# be to treat temporary errors as permanent. Therefore, DO NOT remove this
# retry rule unless you really don't want any retries.

# Address or Domain    Error       Retries
# -----------------    -----       -------

*                      *           F,2h,15m; G,16h,1h,1.5; F,4d,6h



######################################################################
#                      REWRITE CONFIGURATION                         #
######################################################################

# There are no rewriting specifications in this default configuration file.

begin rewrite



######################################################################
#                   AUTHENTICATION CONFIGURATION                     #
######################################################################

# The following authenticators support plaintext username/password
# authentication using the standard PLAIN mechanism and the traditional
# but non-standard LOGIN mechanism, with Exim acting as the server.
# PLAIN and LOGIN are enough to support most MUA software.
#
# These authenticators are not complete: you need to change the
# server_condition settings to specify how passwords are verified.
# They are set up to offer authentication to the client only if the
# connection is encrypted with TLS, so you also need to add support
# for TLS. See the global configuration options section at the start
# of this file for more about TLS.
#
# The default RCPT ACL checks for successful authentication, and will accept
# messages from authenticated users from anywhere on the Internet.

begin authenticators

# PLAIN authentication has no server prompts. The client sends its
# credentials in one lump, containing an authorization ID (which we do not
# use), an authentication ID, and a password. The latter two appear as
# $auth2 and $auth3 in the configuration and should be checked against a
# valid username and password. In a real configuration you would typically
# use $auth2 as a lookup key, and compare $auth3 against the result of the
# lookup, perhaps using the crypteq{}{} condition.

#PLAIN:
#  driver                     = plaintext
#  server_set_id              = $auth2
#  server_prompts             = :
#  server_condition           = Authentication is not yet configured
#  server_advertise_condition = ${if def:tls_cipher }

# LOGIN authentication has traditional prompts and responses. There is no
# authorization ID in this mechanism, so unlike PLAIN the username and
# password are $auth1 and $auth2. Apart from that you can use the same
# server_condition setting for both authenticators.

#LOGIN:
#  driver                     = plaintext
#  server_set_id              = $auth1
#  server_prompts             = <| Username: | Password:
#  server_condition           = Authentication is not yet configured
#  server_advertise_condition = ${if def:tls_cipher }

# Секция авторизации при отправке писем. Ввиду того,
# что почтовых клиентов много, и все всё делают
# по-своему, то и механизмов авторизации три...
#begin authenticators

# А вот по какому методу авторизуется оутглюк - я уже и
# не помню... Хотя в своё время долго ковырялся,
# пока настроил... Толь plain, толь login...
auth_plain:
  driver = plaintext
  public_name = PLAIN
  server_condition = ${lookup mysql{SELECT `username` FROM \
                     `mailbox` WHERE `username` = \
                     '${quote_mysql:$1}' AND `password` = \
                     '${quote_mysql:$2}'}{yes}{no}}
  server_prompts = :
  server_set_id = $2

# Вроде по этому оутглюк, а по предыдущему нетскейп.
auth_login:
  driver = plaintext
  public_name = LOGIN
  server_condition = ${lookup mysql{SELECT `username` FROM \
                     `mailbox` WHERE `username` = \
                     '${quote_mysql:$1}' AND `password` = \
                     '${quote_mysql:$2}'}{yes}{no}}
  server_prompts = Username:: : Password::
  server_set_id = $1

# А так авторизуется "Летучая Мышь" - TheBat!
auth_cram_md5:
  driver = cram_md5
  public_name = CRAM-MD5
  server_secret = ${lookup mysql{SELECT `password` FROM \
                        `mailbox` WHERE `username` \
                        = '${quote_mysql:$1}'}{$value}fail}
  server_set_id = $1

######################################################################
#                   CONFIGURATION FOR local_scan()                   #
######################################################################

# If you have built Exim to include a local_scan() function that contains
# tables for private options, you can define those options here. Remember to
# uncomment the "begin" line. It is commented by default because it provokes
# an error with Exim binaries that are not built with LOCAL_SCAN_HAS_OPTIONS
# set in the Local/Makefile.

# begin local_scan


# End of Exim configuration file
Часть строчек писал вручную, часть скопировал прямо из статьи. Там в некоторых местах стоят апострофы. Может косяк в их написании - в статье они отличаются :unknown:
И вообще не понятно вот что - сообщения в которых говорится "assumed not in list" что означают? Может сообщение не проходит через черный список? И при чем тут вообще DNS :unknown:
Истина где-то рядом :smile:

Alex_hha
лейтенант
Сообщения: 755
Зарегистрирован: 2005-11-06 18:25:26
Контактная информация:

Re: exim не принимает почту, courier-authdaemond не запускается!

Непрочитанное сообщение Alex_hha » 2008-08-09 17:15:07

Пипец, ты бы еще Войну и мир выложил в полном объеме. Лично мне лень читать такой объем ненужной информации. Ты сначала разберись с одной проблемой - МТА, а потом переходи к другой - courier-imap.
С английским у меня проблем не возникает читать умею. Кстати в сообщении забыл указать - с хламав пытался разобраться - сокет на месте. пробовал даже его переустановить к чертям - не помогло!!!
# ls -la var/run/clamav/clamd.sock

?
Далее ставлю courier-imap, рихтую конфиг авторизации. Набираю
./couruer-authdaemond start
похоже, что нет записи в rc.conf

lomaker
рядовой
Сообщения: 20
Зарегистрирован: 2008-08-08 12:33:43

Re: exim не принимает почту, courier-authdaemond не запускается!

Непрочитанное сообщение lomaker » 2008-08-11 7:13:15

Код: Выделить всё

# ls -la /var/run/clamav/clamd.sock
srwxrwxrwx  1 clamav  clamav  0 Aug 10 08:49 /var/run/clamav/clamd.sock
В файле rc.conf есть строки:

Код: Выделить всё

courier_authdaemond_enable="YES"
Вот и я говорю, что вроде все сделал по статье - должно по идее работать

Гость
проходил мимо

Re: exim не принимает почту, courier-authdaemond не запускается!

Непрочитанное сообщение Гость » 2008-08-12 13:07:06

все - с одной проблемой разобрался - виной всему моя собственная невнимательность(как всегда :-D ), я в rc.conf вместо courier-authdaemond написал courier-authdaemon :-D
ну а с отправкой писем проблема остается нерешенной!!! Кстати после того как я запустил courier принял письмо с сервера, а затем попытался отправить батом на сервер - такая же история - говорит инвалидный ваш сокет clamd.sock. Захожу в mc в директорию /var/run/clamav/ - этот самый сокет там есть. Размер правда его 0. Это нормально или как? Ну и не поленитесь пожалуйста люди, прочтите конфиг!!! Может косяк всетаки в нем?

Аватара пользователя
Alex Keda
стреляли...
Сообщения: 35068
Зарегистрирован: 2004-10-18 14:25:19
Откуда: Made in USSR
Контактная информация:

Re: exim не принимает почту, courier-authdaemond не запускается!

Непрочитанное сообщение Alex Keda » 2008-08-12 13:17:49

логи давай
Убей их всех! Бог потом рассортирует...

lomaker
рядовой
Сообщения: 20
Зарегистрирован: 2008-08-08 12:33:43

Re: exim не принимает почту, courier-authdaemond не запускается!

Непрочитанное сообщение lomaker » 2008-08-12 14:58:24

Вот лог:

Код: Выделить всё

Aug 12 00:00:00 mydomain newsyslog[9343]: logfile turned over
Aug 12 00:01:09 mydomain exim[9355]: 2008-08-12 00:01:09 1KSZoQ-0002Qt-3T <=
root@mydomain.ru U=root P=local S=1426 from <root@mydomain.ru> for root
Aug 12 00:01:09 mydomain exim[9546]: 2008-08-12 00:01:09 1KSZoQ-0002Qt-3T **
root@mydomain.ru: Unrouteable address
Aug 12 00:01:10 mydomain exim[9547]: 2008-08-12 00:01:10 1KSZpW-0002Tz-2E <= <>
R=1KSZoQ-0002Qt-3T U=mailnull P=local S=2292 from <> for root@mydomain.ru
Aug 12 00:01:10 mydomain exim[9548]: 2008-08-12 00:01:10 1KSZpW-0002Tz-2E **
root@mydomain.ru: Unrouteable address
Aug 12 00:01:10 mydomain exim[9548]: 2008-08-12 00:01:10 1KSZpW-0002Tz-2E Frozen
(delivery error message)
Aug 12 00:01:10 mydomain exim[9546]: 2008-08-12 00:01:10 1KSZoQ-0002Qt-3T
Completed
Aug 12 00:19:20 mydomain exim[9611]: 2008-08-12 00:19:20 1KSZpW-0002Tz-2E
Message is frozen
Aug 12 00:49:19 mydomain exim[9841]: 2008-08-12 00:49:19 1KSZpW-0002Tz-2E
Unfrozen by errmsg timer
Aug 12 00:49:20 mydomain exim[9841]: 2008-08-12 00:49:20 1KSZpW-0002Tz-2E **
root@mydomain.ru: Unrouteable address
Aug 12 00:49:20 mydomain exim[9841]: 2008-08-12 00:49:20 1KSZpW-0002Tz-2E
root@mydomain.ru: error ignored
Aug 12 00:49:20 mydomain exim[9841]: 2008-08-12 00:49:20 1KSZpW-0002Tz-2E
Completed
Aug 12 03:04:24 mydomain exim[13646]: 2008-08-12 03:04:24 1KScgq-0003Y6-7X <=
root@mydomain.ru U=root P=local S=17546 from <root@mydomain.ru> for root
Aug 12 03:04:24 mydomain exim[13692]: 2008-08-12 03:04:24 1KScgq-0003Y6-7X **
root@mydomain.ru: Unrouteable address
Aug 12 03:04:24 mydomain exim[13700]: 2008-08-12 03:04:24 1KScgq-0003Yy-Nk <= <>
R=1KScgq-0003Y6-7X U=mailnull P=local S=18412 from <> for root@mydomain.ru
Aug 12 03:04:24 mydomain exim[13692]: 2008-08-12 03:04:24 1KScgq-0003Y6-7X
Completed
Aug 12 03:04:24 mydomain exim[13703]: 2008-08-12 03:04:24 1KScgq-0003Yy-Nk **
root@mydomain.ru: Unrouteable address
Aug 12 03:04:24 mydomain exim[13703]: 2008-08-12 03:04:24 1KScgq-0003Yy-Nk
Frozen (delivery error message)
Aug 12 03:04:24 mydomain exim[13712]: 2008-08-12 03:04:24 1KScgq-0003ZA-Vj <=
root@mydomain.ru U=root P=local S=2948 from <root@mydomain.ru> for root
Aug 12 03:04:25 mydomain exim[13714]: 2008-08-12 03:04:25 1KScgq-0003ZA-Vj **
root@mydomain.ru: Unrouteable address
Aug 12 03:04:25 mydomain exim[13715]: 2008-08-12 03:04:25 1KScgr-0003ZD-3y <= <>
R=1KScgq-0003ZA-Vj U=mailnull P=local S=3814 from <> for root@mydomain.ru
Aug 12 03:04:25 mydomain exim[13714]: 2008-08-12 03:04:25 1KScgq-0003ZA-Vj
Completed
Aug 12 03:04:25 mydomain exim[13716]: 2008-08-12 03:04:25 1KScgr-0003ZD-3y **
root@mydomain.ru: Unrouteable address
Aug 12 03:04:25 mydomain exim[13716]: 2008-08-12 03:04:25 1KScgr-0003ZD-3y
Frozen (delivery error message)
Aug 12 03:19:18 mydomain exim[14524]: 2008-08-12 03:19:18 1KScgq-0003Yy-Nk
Message is frozen
Aug 12 03:19:18 mydomain exim[14525]: 2008-08-12 03:19:18 1KScgr-0003ZD-3y
Message is frozen
Aug 12 03:49:18 mydomain exim[15105]: 2008-08-12 03:49:18 1KScgq-0003Yy-Nk
Message is frozen
Aug 12 03:49:18 mydomain exim[15106]: 2008-08-12 03:49:18 1KScgr-0003ZD-3y
Message is frozen
Aug 12 04:19:18 mydomain exim[15172]: 2008-08-12 04:19:18 1KScgq-0003Yy-Nk
Unfrozen by errmsg timer
Aug 12 04:19:18 mydomain exim[15172]: 2008-08-12 04:19:18 1KScgq-0003Yy-Nk **
root@mydomain.ru: Unrouteable address
Aug 12 04:19:18 mydomain exim[15172]: 2008-08-12 04:19:18 1KScgq-0003Yy-Nk
root@mydomain.ru: error ignored
Aug 12 04:19:18 mydomain exim[15172]: 2008-08-12 04:19:18 1KScgq-0003Yy-Nk
Completed
Aug 12 04:19:18 mydomain exim[15173]: 2008-08-12 04:19:18 1KScgr-0003ZD-3y
Unfrozen by errmsg timer
Aug 12 04:19:18 mydomain exim[15173]: 2008-08-12 04:19:18 1KScgr-0003ZD-3y **
root@mydomain.ru: Unrouteable address
Aug 12 04:19:18 mydomain exim[15173]: 2008-08-12 04:19:18 1KScgr-0003ZD-3y
root@mydomain.ru: error ignored
Aug 12 04:19:18 mydomain exim[15173]: 2008-08-12 04:19:18 1KScgr-0003ZD-3y
Completed
Aug 12 17:18:06 mydomain authdaemond: modules="authmysql", daemons=5
Aug 12 17:18:06 mydomain authdaemond: Installing libauthmysql
Aug 12 17:18:06 mydomain authdaemond: Installation complete: authmysql
Aug 12 17:28:55 mydomain pop3d: pupkin@mydomain.ru:
chdir(/var/mail/eximmydomain.ru/pupkin/) failed!!
Aug 12 17:28:55 mydomain pop3d: error: No such file or directory
Aug 12 17:28:55 mydomain pop3d: LOGIN FAILED, user=pupkin,
ip=[::ffff:192.168.16.100]
Aug 12 17:28:55 mydomain pop3d: authentication error: No such file or directory
Aug 12 17:29:17 mydomain pop3d: pupkin@mydomain.ru:
chdir(/var/mail/eximmydomain.ru/pupkin/) failed!!
Aug 12 17:29:17 mydomain pop3d: error: No such file or directory
Aug 12 17:29:17 mydomain pop3d: LOGIN FAILED, user=pupkin,
ip=[::ffff:192.168.16.100]
Aug 12 17:29:17 mydomain pop3d: authentication error: No such file or directory
Aug 12 17:29:18 mydomain pop3d: pupkin@mydomain.ru:
chdir(/var/mail/eximmydomain.ru/pupkin/) failed!!
Aug 12 17:29:18 mydomain pop3d: error: No such file or directory
Aug 12 17:29:18 mydomain pop3d: LOGIN FAILED, user=pupkin,
ip=[::ffff:192.168.16.100]
Aug 12 17:29:18 mydomain pop3d: authentication error: No such file or directory
Aug 12 17:29:19 mydomain pop3d: pupkin@mydomain.ru:
chdir(/var/mail/eximmydomain.ru/pupkin/) failed!!
Aug 12 17:29:19 mydomain pop3d: error: No such file or directory
Aug 12 17:29:19 mydomain pop3d: LOGIN FAILED, user=pupkin,
ip=[::ffff:192.168.16.100]
Aug 12 17:29:19 mydomain pop3d: authentication error: No such file or directory
Aug 12 17:29:20 mydomain pop3d: pupkin@mydomain.ru:
chdir(/var/mail/eximmydomain.ru/pupkin/) failed!!
Aug 12 17:29:20 mydomain pop3d: error: No such file or directory
Aug 12 17:29:20 mydomain pop3d: LOGIN FAILED, user=pupkin,
ip=[::ffff:192.168.16.100]
Aug 12 17:29:20 mydomain pop3d: authentication error: No such file or directory
Aug 12 17:30:15 mydomain pop3d: pupkin@mydomain.ru:
chdir(/var/mail/eximmydomain.ru/pupkin/) failed!!
Aug 12 17:30:15 mydomain pop3d: error: No such file or directory
Aug 12 17:30:15 mydomain pop3d: LOGIN FAILED,
user=pupkin@mydomain.ru, ip=[::ffff:192.168.16.100]
Aug 12 17:30:15 mydomain pop3d: authentication error: No such file or directory
Aug 12 17:30:18 mydomain pop3d: pupkin@mydomain.ru:
chdir(/var/mail/eximmydomain.ru/pupkin/) failed!!
Aug 12 17:30:18 mydomain pop3d: error: No such file or directory
Aug 12 17:30:18 mydomain pop3d: LOGIN FAILED,
user=pupkin@mydomain.ru, ip=[::ffff:192.168.16.100]
Aug 12 17:30:18 mydomain pop3d: authentication error: No such file or directory
Aug 12 17:50:27 mydomain authdaemond: stopping authdaemond children
Aug 12 17:50:27 mydomain authdaemond: modules="authmysql", daemons=5
Aug 12 17:50:27 mydomain authdaemond: Installing libauthmysql
Aug 12 17:50:27 mydomain authdaemond: Installation complete: authmysql
Aug 12 17:50:37 mydomain pop3d: LOGIN, user=pupkin@mydomain.ru,
ip=[::ffff:192.168.16.100], port=[4419]
Aug 12 17:50:49 mydomain pop3d: LOGOUT, user=pupkin@mydomain.ru,
ip=[::ffff:192.168.16.100], port=[4419], top=494, retr=1614, rcvd=53, sent=2476, time=12
Aug 12 17:51:26 mydomain exim[35491]: 2008-08-12 17:51:26 no host name found for
IP address 192.168.16.100
Aug 12 17:51:27 mydomain exim[35491]: 2008-08-12 17:51:27 1KSqXH-0009ER-3j
malware acl condition: clamd: invalid socket 'var/run/clamav/clamd.sock'
Aug 12 17:51:27 mydomain exim[35491]: 2008-08-12 17:51:27 1KSqXH-0009ER-3j
malware acl condition: clamd: invalid socket 'var/run/clamav/clamd.sock'
Aug 12 17:51:27 mydomain exim[35491]: 2008-08-12 17:51:27 1KSqXH-0009ER-3j
H=(localhost) [192.168.16.100] I=[213.24.155.53]:25 F=<pupkin@mydomain.ru>
temporarily rejected after DATA
Aug 12 17:51:27 mydomain exim[35491]: [1\22] 2008-08-12 17:51:27
1KSqXH-0009ER-3j H=(localhost) [192.168.16.100] I=[213.24.155.53]:25
F=<pupkin@mydomain.ru> temporarily rejected after DATA
Aug 12 17:51:27 mydomain exim[35491]: [2\22] Envelope-from:
<pupkin@mydomain.ru>
Aug 12 17:51:27 mydomain exim[35491]: [3\22] Envelope-to:
<root@mydomain.ru>
Aug 12 17:51:27 mydomain exim[35491]: [4\22] P Received: from [192.168.16.100]
(helo=localhost)
Aug 12 17:51:27 mydomain exim[35491]: [5\22]    by mail.mydomain.ru with
esmtp (Exim 4.68 (FreeBSD))
Aug 12 17:51:27 mydomain exim[35491]: [6\22]    (envelope-from
<pupkin@mydomain.ru>)
Aug 12 17:51:27 mydomain exim[35491]: [7\22]    id 1KSqXH-0009ER-3j
Aug 12 17:51:27 mydomain exim[35491]: [8\22]    for root@mydomain.ru;
Tue, 12 Aug 2008 17:51:27 +0800
Aug 12 17:51:27 mydomain exim[35491]: [9\22]   Date: Tue, 12 Aug 2008 17:52:30
+0800
Aug 12 17:51:27 mydomain exim[35491]: [10\22] F From:
=?Windows-1251?B?xODt6OvgX+3gX8zl5OLl5Pw=?= <pupkin@mydomain.ru>
Aug 12 17:51:27 mydomain exim[35491]: [11\22]   X-Mailer: The Bat! (v2.10) UNREG
/ CD5BF9353B3B7091
Aug 12 17:51:27 mydomain exim[35491]: [12\22] R Reply-To:
=?Windows-1251?B?xODt6OvgX+3gX8zl5OLl5Pw=?= <pupkin@mydomain.ru>
Aug 12 17:51:27 mydomain exim[35491]: [13\22]   Organization:
=?Windows-1251?B?zs7OICLM5eTi5eT8Ig==?=
Aug 12 17:51:27 mydomain exim[35491]: [14\22]   X-Priority: 3 (Normal)
Aug 12 17:51:27 mydomain exim[35491]: [15\22] I Message-ID:
<796318054.20080812175230@mydomain.ru>
Aug 12 17:51:27 mydomain exim[35491]: [16\22] T To: pupkin_root
<root@mydomain.ru>
Aug 12 17:51:27 mydomain exim[35491]: [17\22]   Subject: Re: test
Aug 12 17:51:27 mydomain exim[35491]: [18\22]   In-Reply-To:
<E1KQwbz-000HC2-GI@mail.mydomain.ru>
Aug 12 17:51:27 mydomain exim[35491]: [19\22]   References:
<E1KQwbz-000HC2-GI@mail.mydomain.ru>
Aug 12 17:51:27 mydomain exim[35491]: [20\22]   MIME-Version: 1.0
Aug 12 17:51:27 mydomain exim[35491]: [21\22]   Content-Type: text/plain;
charset=Windows-1251
Aug 12 17:51:27 mydomain exim[35491]: [22/22]   Content-Transfer-Encoding: 8bit

Аватара пользователя
Urgor
лейтенант
Сообщения: 663
Зарегистрирован: 2006-03-14 16:30:18
Откуда: Гилея (СПб)
Контактная информация:

Re: exim не принимает почту, courier-authdaemond не запускается!

Непрочитанное сообщение Urgor » 2008-08-12 15:14:54

Найди одно отличие
av_scanner = clamd:var/run/clamav/clamd.sock
av_scanner = clamd:/var/run/clamav/clamd.sock
:)
Власть в руках у чужаков, и ты им платишь дань...

Гость
проходил мимо

Re: exim не принимает почту, courier-authdaemond не запускается!

Непрочитанное сообщение Гость » 2008-08-12 18:48:25

Отлично - теперь на сокет не ругается, но остальные ошибки так и остались:

Код: Выделить всё

Aug 12 23:17:40 mydomain exim[36460]: 2008-08-12 23:17:40 exim 4.68 daemon
started: pid=36460, -q30m, listening for SMTP on port 25 (IPv4)
Aug 12 23:20:08 mydomain exim[36466]: 2008-08-12 23:20:08 1KSvfM-0009UA-Ph <=
root@mydomain.ru U=root P=local S=627 from <root@mydomain.ru> for
pupkin@mail.ru
Aug 12 23:20:11 mydomain exim[36467]: 2008-08-12 23:20:11 1KSvfM-0009UA-Ph =>
pupkin@mail.ru R=dnslookup T=remote_smtp H=mxs.mail.ru [194.67.23.20] C="250 OK
id=1KSvgS-0002C3-00"
Aug 12 23:20:11 mydomain exim[36467]: 2008-08-12 23:20:11 1KSvfM-0009UA-Ph
Completed
Aug 12 23:30:35 mydomain exim[36488]: 2008-08-12 23:30:35 DNS list lookup defer
(probably timeout) for 200.23.67.194.opm.blitzed.org: assumed not in list
Aug 12 23:30:55 mydomain exim[36488]: 2008-08-12 23:30:55 DNS list lookup defer
(probably timeout) for 200.23.67.194.dynablock.njabl.org: assumed not in list
Aug 12 23:30:55 mydomain exim[36488]: 2008-08-12 23:30:55 H=mx34.mail.ru
[194.67.23.200] I=[213.24.155.53]:25 F=<pupkin@mail.ru> rejected RCPT
<root@mydomain.ru>: Unrouteable address
Aug 12 23:30:55 mydomain exim[36488]: 2008-08-12 23:30:55 H=mx34.mail.ru
[194.67.23.200] I=[213.24.155.53]:25 F=<pupkin@mail.ru> rejected RCPT
<root@mydomain.ru>: Unrouteable address
Aug 12 23:38:57 mydomain exim[36536]: 2008-08-12 23:38:57
H=118-167-139-24.dynamic.hinet.net (213.24.155.77) [118.167.139.24] I=[213.24.155.77]:25
F=<support@microsoft.com> rejected RCPT <support@microsoft.com>: "this is my IP! fuck
off!"
Aug 12 23:38:57 mydomain exim[36536]: 2008-08-12 23:38:57
H=118-167-139-24.dynamic.hinet.net (213.24.155.77) [118.167.139.24] I=[213.24.155.77]:25
F=<support@microsoft.com> rejected RCPT <support@microsoft.com>: "this is my IP! fuck
off!"
Aug 12 23:38:58 mydomain exim[36536]: 2008-08-12 23:38:58 unexpected
disconnection while reading SMTP command from 118-167-139-24.dynamic.hinet.net
(213.24.155.77) [118.167.139.24] I=[213.24.155.77]:25
особенно прикололи последние строчки - получается, что мелкософт пихает в helo мой айпишнег? :-D

lomaker
рядовой
Сообщения: 20
Зарегистрирован: 2008-08-08 12:33:43

Re: exim не принимает почту, courier-authdaemond не запускается!

Непрочитанное сообщение lomaker » 2008-08-13 5:39:02

Пардон - предыдущее сообщение писал я, только авторизоваться забыл :)

Аватара пользователя
Urgor
лейтенант
Сообщения: 663
Зарегистрирован: 2006-03-14 16:30:18
Откуда: Гилея (СПб)
Контактная информация:

Re: exim не принимает почту, courier-authdaemond не запускается!

Непрочитанное сообщение Urgor » 2008-08-13 7:08:25

lomaker писал(а):Пардон - предыдущее сообщение писал я, только авторизоваться забыл :)
И шо тебя там не устраивает? Это?

Код: Выделить всё

[194.67.23.200] I=[213.24.155.53]:25 F=<pupkin@mail.ru> rejected RCPT
<root@mydomain.ru>: Unrouteable address
А в базе такой юзер есь?
Власть в руках у чужаков, и ты им платишь дань...

lomaker
рядовой
Сообщения: 20
Зарегистрирован: 2008-08-08 12:33:43

Re: exim не принимает почту, courier-authdaemond не запускается!

Непрочитанное сообщение lomaker » 2008-08-13 10:06:11

извиняюсь конечно за ламерский вопрос, просто руководства по использованию сей статьи не прилагалось, и так как я с этими прогами столкнулся впервые для меня немножко не явно, какие именно манипуляции нужно сделать, чтобы все заработало? Попытаюсь предположить - получается, что получить письма я могу получать только с тех ящиков, которые занесены в базу exim? Если так, то в какую таблу надо что прописать?
Хотя если вопрос был по поводу наличия в базе пользователя root@mydomain.ru то таковой имеется!
И еще вот не могу понять некоторые вещи. Заранее извинюсь за плохое знание протоколов и rfc :smile: :
1) К примеру сервер n собирается отправить мне спаммерское сообщение. Оно в любом случае попадет ко мне на сервер и обсчитается провайдером а потом отбросится как спам, или же exim по своим правилам на этапе соединения там или приветствия определит что это спам и не станет его даже вообще принимать - отвергнет соединение от данного сервера?

lomaker
рядовой
Сообщения: 20
Зарегистрирован: 2008-08-08 12:33:43

Re: exim не принимает почту, courier-authdaemond не запускается!

Непрочитанное сообщение lomaker » 2008-08-13 10:08:56

епт...!!! да, действительно нет такого юзера в базе!!! :oops: я просто супер внимательный чел!!!