exim+mysql-users - не работает =(

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

Модератор: xM

Правила форума
Убедительная просьба юзать теги [code] при оформлении листингов.
Сообщения не оформленные должным образом имеют все шансы быть незамеченными.
stark
мл. сержант
Сообщения: 79
Зарегистрирован: 2008-10-26 10:07:03
Контактная информация:

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение stark » 2009-09-18 14:14:03

vot tolko vopros, vot eti znacheniya

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

Server:         94.101.xxx.xxx
Address:        94.101.xxx.xxx#53
dolzhen bit moy ipaddress
ili dns provaidera ?
Последний раз редактировалось stark 2009-09-23 9:19:45, всего редактировалось 2 раза.

Хостинговая компания 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/

kerilka
сержант
Сообщения: 193
Зарегистрирован: 2008-11-18 18:38:48

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение kerilka » 2009-09-18 14:25:03

это должны быть рабочие ДНС. ваши или нет - не важно

в первом случае судя по логу соединение завершилось по таймауту (причин великое множество почему это могло произойти, например обрыв связи), вторая - не резолвнул имя хоста. может быть тоже по той же причине обрыва связи или потери пакетов? udp в отличии от tcp не гарантирует доставку.

stark
мл. сержант
Сообщения: 79
Зарегистрирован: 2008-10-26 10:07:03
Контактная информация:

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение stark » 2009-09-18 15:57:48

spasibo za otveti
delo dolzhno bit v zakritix portax u provaidera !
pozvanyuka ya im :x

stark
мл. сержант
Сообщения: 79
Зарегистрирован: 2008-10-26 10:07:03
Контактная информация:

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение stark » 2009-09-18 20:49:39

destvitelno provaider zakrival smtp port na upload !
1. teper s konsoli vse otpravlyaeetsya ,
2. no poluchit ne mogu s google.com
3. v logax "messages", soderzhanie takogo tipa

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

Sep 18 20:44:09 mx exim[3554]: 1MokJN-0000vK-Rx malware acl condition: unable to connect to sophie UNIX socket (/var/run/sophie). errno=2
4. pri otpravke s pochtovogo klienta iz nutri seti svoey pishet

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

Temporaly local problem, try later

kerilka
сержант
Сообщения: 193
Зарегистрирован: 2008-11-18 18:38:48

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение kerilka » 2009-09-21 9:43:46

покажите конфиг эксима

stark
мл. сержант
Сообщения: 79
Зарегистрирован: 2008-10-26 10:07:03
Контактная информация:

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение stark » 2009-09-21 9:53:05

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

# $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 = mx.mydomain.com

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 = @
#domainlist relay_to_domains =
#hostlist   relay_from_hosts = localhost

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.98.98.0/28

# 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:/tmp/clamd
#av_scanner = clamd:/var/run/clamav/clamd

# 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 =
qualify_domain = mx.mydomain.com

# 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 =
qualify_recipient = mx.mydomain.com

# 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
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 = 0s


# 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 = 15d
freeze_tell = mail@mydomain.com
helo_accept_junk_hosts = 192.98.98.0/28 
auto_thaw = 1h
smtp_banner = "$primary_hostname, ESMTP EXIM $version_number"
smtp_accept_max = 50
smtp_connect_backlog = 30
smtp_accept_max_per_host = 20

# 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
split_spool_directory = true
remote_max_parallel = 15
return_size_limit = 70k
message_size_limit = 24M
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_timestamp = no
system_filter = /usr/local/etc/exim/copy_mail.conf



######################################################################
#                       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       = "Restricted characters in address"
          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       = "Restricted characters in address"
          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

  # 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

deny    message       = "HELO/EHLO bla bla? SMTP RFC"
          condition     = ${if eq{$sender_helo_name}{}{yes}{no}}

deny    message       = "Do not write your IP in quaility HELO!"
          hosts         =  *:!+relay_from_hosts
          condition     = ${if eq{$sender_helo_name}{$sender_host_address}{true}{false}}

deny    condition     = ${if eq{$sender_helo_name}{$interface_address}{yes}{no}}
          hosts         = !127.0.0.1 : !localhost : *
          message       = "This my  IP-adress! Go away!"

deny    condition     = ${if match{$sender_helo_name}{\N^\d+$\N}{yes}{no}}
          hosts         = !127.0.0.1:!localhost:*
          message       = "In  HELO can't be only digits!"

deny    message       = "Im not realy like your host"
       #   condition     = ${if match{$sender_host_name} {adsl|dialup|pool|peer|dhcp} {yes}{no}}
condition     = ${if match{$sender_host_name} {adsl} {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 : \

warn
	set acl_m0 = 20s
warn
	hosts = +relay_from_hosts : 
        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

accept  domains       = +local_domains
          endpass
          message       = "In this domain no exists that customer"
          verify        = recipient

accept  domains       = +relay_to_domains
          endpass
          message       = "My server do not know way for your host ..."
          verify        = recipient

accept  hosts         = +relay_from_hosts


deny    message       = "You are free man, go home junky"

  # 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


# 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"

  # 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


# 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}}
data = ${lookup mysql{SELECT `goto` FROM `alias` WHERE `address`='${quote_mysql:$local_part@$domain}' OR `address`='${quote_mysql:@$domain}'}}

#  user = mailnull
#  group = mail
#  file_transport = address_file
#  pipe_transport = address_pipe

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

# 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

address_file:
    driver = appendfile
    delivery_date_add
    envelope_to_add
    return_path_add


# 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_pipe:
  driver = pipe
  return_output


# This transport is used for handling deliveries directly to files that are
# generated by aliasing or forwarding.

#address_file:
#  driver = appendfile
#  delivery_date_add
#  envelope_to_add
#  return_path_add


# This transport is used for handling autoreplies generated by the filtering
# option of the userforward router.

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.

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

#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.

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

#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 }

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
Последний раз редактировалось stark 2009-09-23 9:23:05, всего редактировалось 1 раз.

kerilka
сержант
Сообщения: 193
Зарегистрирован: 2008-11-18 18:38:48

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение kerilka » 2009-09-21 9:59:56

у вас не используется антивирус, но в конфиге не закоментировано:

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

deny    malware    = *
message    = "This message contains a virus - $malware_name"

stark
мл. сержант
Сообщения: 79
Зарегистрирован: 2008-10-26 10:07:03
Контактная информация:

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение stark » 2009-09-21 10:11:12

spasibo posmotryu.
ya pomnyu ne smog postavit iz portov clamav, pisal chto-to mesto raspolozheniya izmenino. operaciya make vivalivalas oshibkoy.
a chto mozhet bit naschet chto do menya ne dohodit pisma s mira ?
ne prailno nastoeniy firewall ?
podskazhite pravilnie rabochie pravila dlya pochti dlya raboti s naruzhi i za Natom !

kerilka
сержант
Сообщения: 193
Зарегистрирован: 2008-11-18 18:38:48

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение kerilka » 2009-09-21 10:16:30

правила? да элементарные :)
разрешить всем ломиться на 25 110 993 995 на все интерфейсы :) 465 я думаю вам не пригодится :)

kerilka
сержант
Сообщения: 193
Зарегистрирован: 2008-11-18 18:38:48

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение kerilka » 2009-09-21 10:18:40

совсем забыл, еще 143 :)

stark
мл. сержант
Сообщения: 79
Зарегистрирован: 2008-10-26 10:07:03
Контактная информация:

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение stark » 2009-09-21 10:54:26

spasibo, tak i sdelayu ! :good:
mozhete podskazat kak mne clamav postavit ?

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

[10:56]  /home/stark >cd /usr/ports/security/clamav
[10:56]  /usr/ports/security/clamav >make
===>  Found saved configuration for clamav-0.95.2
===>  Extracting for clamav-0.95.2
=> MD5 Checksum mismatch for clamav-0.95.2.tar.gz.
=> SHA256 Checksum mismatch for clamav-0.95.2.tar.gz.
===>  Refetch for 1 more times files: clamav-0.95.2.tar.gz clamav-0.95.2.tar.gz
===>  Found saved configuration for clamav-0.95.2
=> clamav-0.95.2.tar.gz doesn't seem to exist in /usr/ports/distfiles/.
=> Attempting to fetch from http://heanet.dl.sourceforge.net/project/clamav/clamav/0.95.2/.
fetch: clamav-0.95.2.tar.gz: local modification time does not match remote
=> Attempting to fetch from http://sunet.dl.sourceforge.net/project/clamav/clamav/0.95.2/.
fetch: clamav-0.95.2.tar.gz: local modification time does not match remote
=> Attempting to fetch from http://iweb.dl.sourceforge.net/project/clamav/clamav/0.95.2/.
fetch: clamav-0.95.2.tar.gz: local modification time does not match remote
=> Attempting to fetch from http://switch.dl.sourceforge.net/project/clamav/clamav/0.95.2/.
fetch: clamav-0.95.2.tar.gz: local modification time does not match remote
=> Attempting to fetch from http://surfnet.dl.sourceforge.net/project/clamav/clamav/0.95.2/.
fetch: clamav-0.95.2.tar.gz: local modification time does not match remote
=> Attempting to fetch from http://kent.dl.sourceforge.net/project/clamav/clamav/0.95.2/.
fetch: clamav-0.95.2.tar.gz: local modification time does not match remote
=> Attempting to fetch from http://freefr.dl.sourceforge.net/project/clamav/clamav/0.95.2/.
fetch: clamav-0.95.2.tar.gz: local modification time does not match remote
=> Attempting to fetch from http://voxel.dl.sourceforge.net/project/clamav/clamav/0.95.2/.
fetch: clamav-0.95.2.tar.gz: local modification time does not match remote
=> Attempting to fetch from http://jaist.dl.sourceforge.net/project/clamav/clamav/0.95.2/.
fetch: clamav-0.95.2.tar.gz: local modification time does not match remote
=> Attempting to fetch from http://osdn.dl.sourceforge.net/project/clamav/clamav/0.95.2/.
fetch: clamav-0.95.2.tar.gz: local modification time does not match remote
=> Attempting to fetch from http://nchc.dl.sourceforge.net/project/clamav/clamav/0.95.2/.
fetch: clamav-0.95.2.tar.gz: local modification time does not match remote
=> Attempting to fetch from http://transact.dl.sourceforge.net/project/clamav/clamav/0.95.2/.
fetch: clamav-0.95.2.tar.gz: local modification time does not match remote
=> Attempting to fetch from http://softlayer.dl.sourceforge.net/project/clamav/clamav/0.95.2/.
fetch: clamav-0.95.2.tar.gz: local modification time does not match remote
=> Attempting to fetch from http://internode.dl.sourceforge.net/project/clamav/clamav/0.95.2/.
fetch: clamav-0.95.2.tar.gz: local modification time does not match remote
=> Attempting to fetch from http://biznetnetworks.dl.sourceforge.net/project/clamav/clamav/0.95.2/.
fetch: clamav-0.95.2.tar.gz: local modification time does not match remote
=> Attempting to fetch from http://upfr.dl.sourceforge.net/project/clamav/clamav/0.95.2/.
fetch: http://upfr.dl.sourceforge.net/project/clamav/clamav/0.95.2/clamav-0.95.2.tar.gz: Not Found
=> Attempting to fetch from ftp://ftp.FreeBSD.org/pub/FreeBSD/ports/distfiles/.
fetch: clamav-0.95.2.tar.gz: local modification time does not match remote
=> Couldn't fetch it - please try to retrieve this
=> port manually into /usr/ports/distfiles/ and try again.
*** Error code 1

Stop in /usr/ports/security/clamav.
*** Error code 1

Stop in /usr/ports/security/clamav.
*** Error code 1

Stop in /usr/ports/security/clamav.

kerilka
сержант
Сообщения: 193
Зарегистрирован: 2008-11-18 18:38:48

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение kerilka » 2009-09-21 11:04:10

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

#rm /usr/ports/distfiles/clamav-0.95.2.tar.gz
#cd /usr/ports/security/clamav
#make install clean
Последний раз редактировалось Laa 2009-09-22 14:46:46, всего редактировалось 1 раз.
Причина: Убедительная просьба юзать теги [code] при оформлении листингов.

Аватара пользователя
Laa
ст. лейтенант
Сообщения: 1032
Зарегистрирован: 2008-02-21 18:25:33
Откуда: Украина, Россия

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение Laa » 2009-09-21 11:04:36

Удали clamav-0.95.2.tar.gz из /usr/ports/distfiles. Попробуй еще раз установить.
Время впредь меняй только тогда, когда не запущены сборки чего-бы то ни было.
exim: помните, что выдавая deny, вы можете недоставить ваше же письмо, зарубив sender-verify удаленного MTA к вашему MTA!!!

stark
мл. сержант
Сообщения: 79
Зарегистрирован: 2008-10-26 10:07:03
Контактная информация:

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение stark » 2009-09-21 11:45:38

spasibo ogromnoe :good:
clamav ustanovilsya kak nado !
porti nastoil . Vecherom proveryu kak exm rabotaet po localke.

stark
мл. сержант
Сообщения: 79
Зарегистрирован: 2008-10-26 10:07:03
Контактная информация:

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение stark » 2009-09-22 9:00:12

seychas vse otlichno begaet po lokalke ,
v mir tozhe otsilaetsya ,
no vot prinyat s mira ne mogu ! :(
kakie misli naschet etogo imeyutsya , podskazhite

kerilka
сержант
Сообщения: 193
Зарегистрирован: 2008-11-18 18:38:48

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение kerilka » 2009-09-22 9:23:43

телепаты сменили место жительства! ЛОГИ!!!!!

stark
мл. сержант
Сообщения: 79
Зарегистрирован: 2008-10-26 10:07:03
Контактная информация:

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение stark » 2009-09-22 9:32:05

tut vot takoe v maillog

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

Sep 22 09:15:17 mx exim[5222]: 1Mq1Su-0001ME-VP <= nagios@mx.mydomain.com U=nagios P=local S=568 from <nagios@mx.mydomain.com> for nagios@mydomain.com
Sep 22 09:15:17 mx exim[5223]: 1Mq1Su-0001ME-VP => nagios <nagios@mydomain.com> R=mysqluser T=mysql_delivery
Sep 22 09:15:17 mx exim[5223]: 1Mq1Su-0001ME-VP Completed
Sep 22 09:16:01 mx imapd: LOGOUT, ip=[::ffff:94.101.xxx.xxx], rcvd=11, sent=307
Sep 22 09:20:06 mx exim[5947]: 1Mq1Xa-0001Xv-Cw <= nagios@mx.mydomain.com U=nagios P=local S=577 from <nagios@mx.mydomain.com> for nagios@mydomain.com
Sep 22 09:20:07 mx exim[5948]: 1Mq1Xa-0001Xv-Cw => nagios <nagios@mydomain.com> R=mysqluser T=mysql_delivery
Sep 22 09:20:07 mx exim[5948]: 1Mq1Xa-0001Xv-Cw Completed
Sep 22 09:20:15 mx pop3d: LOGOUT, ip=[::ffff:94.101.xxx.xxx]
Sep 22 09:26:01 mx imapd: LOGOUT, ip=[::ffff:94.101.xxx.xxx], rcvd=11, sent=307
Sep 22 09:30:15 mx pop3d: LOGOUT, ip=[::ffff:94.101.xxx.xxx]
Ni chego bolshe,
ya opravlyayu s gmail.com na moy pochtoviy servak. v logax neyu nichego o tom chto kto-to lomitsya
Последний раз редактировалось stark 2009-09-23 9:26:01, всего редактировалось 1 раз.

kerilka
сержант
Сообщения: 193
Зарегистрирован: 2008-11-18 18:38:48

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение kerilka » 2009-09-22 9:40:33

если в логах ничего нету, то тут 2 варианта:

на ваш домен прикручена MX запись? если да, то та, которая имеет наименьший приоритет, указывает на ваш сервер?
попробуйте из мира прицепиться к себе на 25 порт, получится или нет

ну и вероятно поможет вам письмо о недоставке, которое, судя по всему, придёт к вам на gmail

kerilka
сержант
Сообщения: 193
Зарегистрирован: 2008-11-18 18:38:48

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение kerilka » 2009-09-22 9:41:41

да, и покажите лог exima, а не maillog, или у вас exim всё туда кидает? лог exima как правило называется maiNlog и лежит в /var/log/exim/
там же может находиться rejectlog и т.д.

stark
мл. сержант
Сообщения: 79
Зарегистрирован: 2008-10-26 10:07:03
Контактная информация:

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение stark » 2009-09-22 10:01:32

nu togda po poryadku:
1. zapisk prikruzhena s pripritetom 10
2. poprobuete prikonektirsta s mira ko mne telnet 94.101.xxx.xxx . s raboti ya ne mogu , tut vse zakrito
3. pismo s gmaila

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

This is an automatically generated Delivery Status Notification

Delivery to the following recipient failed permanently:

    test1@mydomain.com

Technical details of permanent failure:
The recipient server did not accept our requests to connect. Learn more at http://mail.google.com/support/bin/answer.py?answer=7720
[mx.mydomain.com. (10): Connection timed out]
4. v /var/log/exim/ pusto
Последний раз редактировалось stark 2009-09-23 9:26:56, всего редактировалось 1 раз.

kerilka
сержант
Сообщения: 193
Зарегистрирован: 2008-11-18 18:38:48

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение kerilka » 2009-09-22 10:10:07

я солидарен с гмэйлом, 25 порт у вас закрыт, подключиться не удаётся. разбирайтесь. как откроете - и почта побежит)

Аватара пользователя
Laa
ст. лейтенант
Сообщения: 1032
Зарегистрирован: 2008-02-21 18:25:33
Откуда: Украина, Россия

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение Laa » 2009-09-22 10:12:39

kerilka писал(а):я солидарен с гмэйлом, 25 порт у вас закрыт, подключиться не удаётся. разбирайтесь. как откроете - и почта побежит)
+1 -- тоже не могу подключиться. :Search:
exim: помните, что выдавая deny, вы можете недоставить ваше же письмо, зарубив sender-verify удаленного MTA к вашему MTA!!!

stark
мл. сержант
Сообщения: 79
Зарегистрирован: 2008-10-26 10:07:03
Контактная информация:

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение stark » 2009-09-22 10:15:30

u menya vot takie pravila v ipfw:

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

${FwCMD} add allow udp from any to ${oip} 25 in recv ${oif}
${FwCMD} add allow udp from ${oip} 25 to any out xmit ${oif}
${FwCMD} add allow udp from any 25 to ${oip} in recv ${oif}
${FwCMD} add allow udp from ${oip} to any 25 out xmit ${oif}
${FwCMD} add allow tcp from any to ${oip} 25 in recv ${oif}
#${FwCMD} add allow tcp from any to ${oip} 25 in recv ${oif} setup

kerilka
сержант
Сообщения: 193
Зарегистрирован: 2008-11-18 18:38:48

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение kerilka » 2009-09-22 10:18:01

правильней будет показать ipfw sh со счётчиком правил) а то иголку в стогу долго искать будем)

stark
мл. сержант
Сообщения: 79
Зарегистрирован: 2008-10-26 10:07:03
Контактная информация:

Re: exim+mysql-users - не работает =(

Непрочитанное сообщение stark » 2009-09-22 10:21:34

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

00100 check-state
00200 allow ip from any to any via lo0
00300 deny ip from any to 127.0.0.0/8
00400 deny ip from 127.0.0.0/8 to any
00500 allow ip from any to 172.27.11.0/24 via fxp0
00600 allow ip from any to 192.98.98.0/28 via xl0
00700 deny ip from any to 10.0.0.0/8 in via fxp0
00800 deny ip from any to 172.16.0.0/12 in via fxp0
00900 deny ip from any to 192.168.0.0/16 in via fxp0
01000 deny ip from any to 0.0.0.0/8 in via fxp0
01100 deny ip from any to 169.254.0.0/16 in via fxp0
01200 deny ip from any to 240.0.0.0/4 in via fxp0
01300 deny icmp from any to any frag
01400 deny log logamount 100 icmp from any to 255.255.255.255 in via fxp0
01500 deny log logamount 100 icmp from any to 255.255.255.255 out via fxp0
01600 divert 8668 ip from 192.98.98.0/28 to any out via fxp0
01700 divert 8668 ip from any to 94.101.xxx.xxx in via fxp0
01800 deny ip from 10.0.0.0/8 to any out via fxp0
01900 deny ip from 172.16.0.0/12 to any out via fxp0
02000 deny ip from 192.168.0.0/16 to any out via fxp0
02100 deny ip from 0.0.0.0/8 to any out via fxp0
02200 deny ip from 169.254.0.0/16 to any out via fxp0
02300 deny ip from 224.0.0.0/4 to any out via fxp0
02400 deny ip from 240.0.0.0/4 to any out via fxp0
02500 allow ip from any to any via fxp0
02600 allow icmp from any to any icmptypes 0,8,11
02700 allow ip from any to any via xl0
02800 allow ip from 192.98.98.0/28 to any out via fxp0
02900 allow ip from any to any via {oif}
03000 allow tcp from any to any established
03100 allow ip from 94.101.xxx.xxx to any out xmit fxp0
03200 allow udp from any to 94.101.xxx.xxx dst-port 53 in via fxp0
03300 allow udp from 94.101.xxx.xxx 53 to any out via fxp0
03400 allow udp from any 53 to 94.101.xxx.xxx in via fxp0
03500 allow udp from 94.101.xxx.xxx to any dst-port 53 out via fxp0
03600 allow tcp from any to 94.101.xxx.xxx dst-port 53 in via fxp0
03700 allow udp from any to 192.98.98.1 dst-port 53 in via xl0
03800 allow udp from 192.98.98.1 53 to any out via xl0
03900 allow udp from any 53 to 192.98.98.1 in via xl0
04000 allow udp from 192.98.98.1 to any dst-port 53 out via xl0
04100 allow tcp from any to 192.98.98.1 dst-port 53 in via xl0
04200 allow udp from any to any dst-port 123 in via fxp0
04300 allow tcp from any to 94.101.xxx.xxx dst-port 443 via fxp0
04400 allow tcp from any to 192.98.98.1 dst-port 443 via xl0
04500 allow tcp from any to 94.101.xxx.xxx dst-port 22 via fxp0
04600 allow tcp from any to 94.101.xxx.xxx dst-port 21 via fxp0
04700 allow udp from any to 94.101.xxx.xxx dst-port 25 in recv fxp0
04800 allow udp from 94.101.xxx.xxx 25 to any out xmit fxp0
04900 allow udp from any 25 to 94.101.xxx.xxx in recv fxp0
05000 allow udp from 94.101.xxx.xxx to any dst-port 25 out xmit fxp0
05100 allow tcp from any to 94.101.xxx.xxx dst-port 25 in recv fxp0
05200 allow tcp from any to 94.101.xxx.xxx dst-port 110 in via fxp0
05300 allow udp from any to 94.101.xxx.xxx dst-port 110 in via fxp0
05400 allow tcp from any to 192.98.98.1 dst-port 110 in via xl0
05500 allow udp from any to 192.98.98.1 dst-port 110 in via xl0
05600 allow tcp from any to 94.101.xxx.xxx dst-port 143 in via fxp0
05700 allow udp from any to 94.101.xxx.xxx dst-port 143 in via fxp0
05800 allow tcp from any to 192.98.98.1 dst-port 143 in via xl0
05900 allow udp from any to 192.98.98.1 dst-port 143 in via xl0
06000 allow ip from any to 94.101.xxx.xxx dst-port 45098 via fxp0
06100 allow udp from any to 94.101.xxx.xxx dst-port 49152-65535 via fxp0
06200 deny log logamount 100 tcp from any to 94.101.xxx.xxx in via fxp0 setup
06300 allow tcp from 94.101.xxx.xxx to any out via fxp0 setup
06400 allow tcp from any to 94.101.xxx.xxx in via xl0 setup
06500 allow ip from any to any via fxp0
06600 allow ip from 192.98.98.4 to not 192.98.98.0/28
06700 allow ip from 192.98.98.2 to not 192.98.98.0/28
06800 allow ip from 192.98.98.14 to not 192.98.98.0/28
06900 allow ip from not 192.98.98.0/28 to 192.98.98.0/28
07000 deny ip from any to any
65535 allow ip from any to any
Последний раз редактировалось stark 2009-09-23 9:28:22, всего редактировалось 1 раз.