顯示文章

這裡允許您檢視這個會員的所有文章。請注意, 您只能看見您有權限閱讀的文章。


文章 - peteryang

頁: 1 2 3 [4]
91
BSD 討論版 / Postfix + SASL2不能認證
« 於: 2004-07-06 10:53 »
小弟後來再重灌一次,這次就成功了
小弟先用ports裝sasl2
之後再裝postfix,然後設再設定/usr/lib/sasl2/smtpd.con及main.cf
以及在/etc/rc.conf裡加
引用
sendmail_enable="NONE"
saslauthd_enable="YES"

之後重開就好了,這次的感覺是先裝sasl2,然後在安裝postfix時會去找到sasl2的DB,因此就可以讀到SASL2的資料,認證就可以過了,謝謝梁楓及各位先進的指教,謝謝

92
BSD 討論版 / Postfix + SASL2不能認證
« 於: 2004-06-30 11:34 »
小弟用ports安裝至於sasl2小弟是參考了這篇
http://phorum.study-area.org/viewtopic.php?t=21388&highlight=postfix
到SASL2之前都沒問題,一加上去就會有問題,不知是那裡的設定有漏了,煩請先進指導

93
BSD 討論版 / Postfix + SASL2不能認證
« 於: 2004-06-30 10:03 »
小弟是用FreeBSD 5.2.1的有試過
引用
/usr/local/etc/rc.d/saslauthd start

但是還是沒有用

94
BSD 討論版 / Postfix + SASL2不能認證
« 於: 2004-06-29 23:27 »
小弟都沒有新增任何東西,按照預設值,若是smtpd n n那個也是預設,所以小弟沒有動

95
BSD 討論版 / Postfix + SASL2不能認證
« 於: 2004-06-29 23:18 »
各位先進大家好:
小弟的環境是FreeBSD 5.2.1,參考網路上的文章架postfix sasl2,小弟用postfix,沒問題,但是加入了sasl2時,發生了不能認證,在maillog裡的訊息如下
引用

Jun 29 23:15:50 pbsd postfix/smtpd[8204]: connect from unknown[192.168.0.2]
Jun 29 23:15:50 pbsd postfix/smtpd[8204]: warning: SASL authentication failure: cannot connect to saslauthd server: No such fi
le or directory
Jun 29 23:15:50 pbsd postfix/smtpd[8204]: warning: unknown[192.168.0.2]: SASL LOGIN authentication failed
Jun 29 23:15:50 pbsd postfix/smtpd[8204]: disconnect from unknown[192.168.0.2]
Jun 29 23:15:55 pbsd postfix/smtpd[8204]: connect from unknown[192.168.0.2]
Jun 29 23:15:55 pbsd postfix/smtpd[8204]: warning: SASL authentication failure: cannot connect to saslauthd server: No such file or directory
Jun 29 23:15:55 pbsd postfix/smtpd[8204]: warning: unknown[192.168.0.2]: SASL LOGIN authentication failed
Jun 29 23:15:55 pbsd postfix/smtpd[8204]: disconnect from unknown[192.168.0.2]

不知是不是找不到檔案,還是那邊少設定了,煩請各位先進不吝指教,謝謝

96
小弟買了那本書後,照那本書去設定,但是還是不行,好像會寄不過去,下面是main.cf的設定
引用

# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the sample-xxx.cf files for a full list.
#
# The general format is lines with parameter = value pairs. Lines
# that begin with whitespace continue the previous line. A value can
# contain references to other $names or ${name}s.
#
# NOTE - CHANGE NO MORE THAN 2-3 PARAMETERS AT A TIME, AND TEST IF
# POSTFIX STILL WORKS AFTER EVERY CHANGE.

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

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

# The command_directory parameter specifies the location of all
# postXXX commands.
#
command_directory = /usr/sbin

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

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

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

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

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

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

# RECEIVING MAIL

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

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

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

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

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

# TRUST AND RELAY CONTROL

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

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

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

# INTERNET OR INTRANET

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

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

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

# ADDRESS REWRITING
#
# Insert text from sample-rewrite.cf if you need to do address
# masquerading.
#
# Insert text from sample-canonical.cf if you need to do address
# rewriting, or if you need username->Firstname.Lastname mapping.

# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
#
# Insert text from sample-virtual.cf if you need virtual domain support.

# "USER HAS MOVED" BOUNCE MESSAGES
#
# Insert text from sample-relocated.cf if you need "user has moved"
# style bounce messages. Alternatively, you can bounce recipients
# with an SMTP server access table. See sample-smtpd.cf.

# TRANSPORT MAP
#
# Insert text from sample-transport.cf if you need explicit routing.

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

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

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

# DELIVERY TO MAILBOX
#
# The home_mailbox parameter specifies the optional pathname of a
# mailbox file relative to a user's home directory. The default
# mailbox file is /var/spool/mail/user or /var/mail/user.  Specify
# "Maildir/" for qmail-style delivery (the / is required).
#
#home_mailbox = Mailbox
#home_mailbox = Maildir/

# The mail_spool_directory parameter specifies the directory where
# UNIX-style mailboxes are kept. The default setting depends on the
# system type.
#
#mail_spool_directory = /var/mail
#mail_spool_directory = /var/spool/mail

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

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

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

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

# JUNK MAIL CONTROLS
#
# The controls listed here are only a very small subset. See the file
# sample-smtpd.cf for an elaborate list of anti-UCE controls.

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

# FAST ETRN SERVICE
#
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
#
# By default, Postfix maintains deferred mail logfile information
# only for destinations that Postfix is willing to relay to (as
# specified in the relay_domains parameter). For other destinations,
# Postfix attempts to deliver ALL queued mail after receiving the
# SMTP "ETRN domain.tld" command, or after execution of "sendmail
# -qRdomain.tld". This can be slow when a lot of mail is queued.
#
# The fast_flush_domains parameter controls what destinations are
# eligible for this "fast ETRN/sendmail -qR" service.
#
#fast_flush_domains = $relay_domains
#fast_flush_domains =

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

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

#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20

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

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

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

# If you don't have X installed on the Postfix machine, try:
# debugger_command =
#       PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
#       echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
#       >$config_directory/$process_name.$process_id.log & sleep 5

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

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

# mailq_path: The full pathname of the Postfix mailq command.  This
# is the Sendmail-compatible mail queue listing command.
#
mailq_path = /usr/bin/mailq

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

# manpage_directory: The location of the Postfix on-line manual pages.
#
manpage_directory = /usr/local/man

# sample_directory: The location of the Postfix sample configuration files.
#
sample_directory = /etc/postfix/sample

# readme_directory: The location of the Postfix README files.
#
readme_directory = /etc/postfix/readme_files

#queue
queue_run_delay = 500

notify_classes = bounce,2bounce,protocol,resource,software,policy
transport_maps = hash:/etc/postfix/transport
#canonical_maps = hash:/etc/postfix/canonical
smtp_skip_4xx_greeting = no
smtp_skip_5xx_greeting = no
smtpd_sasl_auth_enable = yes
smtpd_sasl_local_domain =
smtpd_helo_required = yes
disable_vrfy_command = yes
smtpd_recipient_restrictions = reject_invalid_hostname, reject_non_fqdn_sender, reject_non_fqdn_recipient, reject_unknown_sender_domain, reject_unknown_recipient_domain, permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination reject_rbl_client relays.ordb.org, reject_rbl_client opm.blitzed.org, reject_rbl_client list.dsbl.org, reject_rbl_client sbl.spamhaus.org, reject_rbl_client cbl.abuseat.org, reject_rbl_client dul.dnsbl.sorbs.net, permit
smtpd_client_restrictions = permit_sasl_authenticated
smtpd_sasl_security_options = noanonymous
smtpd_data_restrictions = reject_unauth_pipelining, permit

下面是transport的設定
代碼: [選擇]
msb.tai-one.com.tw      relay:[msa.tai-one.com.tw]

最後是maillog的訊息
引用

May  7 12:26:19 msb postfix/smtpd[7698]: disconnect from unknown[192.168.1.3]
May  7 12:26:20 msb postfix/smtpd[7641]: 697EE17CB3: client=unknown[192.168.1.3]
May  7 12:26:21 msb postfix/cleanup[7684]: 8B45217CB5: message-id=<20040507042559.ED98917CA9@msb.tai-one.com.tw>
May  7 12:26:22 msb postfix/cleanup[7632]: 697EE17CB3: message-id=<20040507042611.16A3017D75@msb.tai-one.com.tw>
May  7 12:26:22 msb postfix/smtp[7634]: 361D117C85: to=<postmaster@msb.tai-one.com.tw>, relay=msa.tai-one.com.tw[192.168.1.3], delay=7, status=sent (250 Ok: queued as 7BD7E765D7)
May  7 12:26:22 msb postfix/smtpd[7698]: connect from unknown[192.168.1.3]
May  7 12:26:23 msb postfix/qmgr[6464]: 697EE17CB3: from=<>, size=13066, nrcpt=1 (queue active)
May  7 12:26:23 msb postfix/smtpd[7631]: disconnect from unknown[192.168.1.3]
May  7 12:26:23 msb postfix/smtpd[7641]: disconnect from unknown[192.168.1.3]
May  7 12:26:23 msb postfix/smtpd[7698]: 5D2BF17D7D: client=unknown[192.168.1.3]
May  7 12:26:23 msb postfix/qmgr[6464]: 8B45217CB5: from=<double-bounce@msb.tai-one.com.tw>, size=3181, nrcpt=1 (queue active)
May  7 12:26:24 msb postfix/cleanup[7689]: 5D2BF17D7D: message-id=<20040507042611.D417317C93@msb.tai-one.com.tw>
May  7 12:26:24 msb postfix/smtpd[7631]: connect from unknown[192.168.1.3]
May  7 12:26:24 msb postfix/smtp[7634]: 8B45217CB5: to=<postmaster@msb.tai-one.com.tw>, relay=msa.tai-one.com.tw[192.168.1.3], delay=3, status=sent (250 Ok: queued as 4C685765D3)
May  7 12:26:24 msb postfix/smtpd[7641]: connect from unknown[192.168.1.3]
May  7 12:26:24 msb postfix/smtp[7693]: 697EE17CB3: to=<peter@msb.tai-one.com.tw>, relay=msa.tai-one.com.tw[192.168.1.3], delay=2, status=sent (250 Ok: queued as 4BB02765CF)
May  7 12:26:25 msb postfix/smtpd[7631]: 69B0F17CB1: client=unknown[192.168.1.3]
May  7 12:26:30 msb postfix/qmgr[6464]: 5D2BF17D7D: from=<double-bounce@msb.tai-one.com.tw>, size=11921, nrcpt=1 (queue active)
May  7 12:26:30 msb postfix/smtpd[7698]: disconnect from unknown[192.168.1.3]
May  7 12:26:31 msb postfix/smtpd[7641]: 358C817CBC: client=unknown[192.168.1.3]

不知這是什麼問題,不知有那位先進可以指導一下,謝謝

97
LDAP 討論區 / [問題]
« 於: 2004-05-04 10:45 »
小弟使用
代碼: [選擇]
/usr/local/bin/ldapsearch dc=tai-one,dc=com,dc=tw
出現下面的回應
引用
# extended LDIF
#
# LDAPv3
# base <> with scope sub
# filter: dc=tai-one,dc=com,dc=tw
# requesting: ALL
#

# search reference
ref: ldap://tai-one.com.tw/CN=Configuration,DC=tai-one,DC=com,DC=tw

# search result
search: 2
result: 0 Success

# numResponses: 2
# numReferences: 1

看起來是沒有找到,不知是否還有其它東西要設定呢???

98
LDAP 討論區 / [問題]
« 於: 2004-05-03 16:17 »
小弟照著zoob的做法感覺上應該好了,但是小弟卻不能與AD用LDAP連接,小弟用
代碼: [選擇]
make makefiles CCARGS="-I/usr/local/include -DHAS_LDAP" \
        AUXLIBS="-L/usr/local/lib -lldap -L/usr/local/lib -llber"

時發生錯誤訊息如下:
代碼: [選擇]
ldap_bind: Invalid credentials (49)
        additional info: 80090308: LdapErr: DSID-0C09030B, comment: AcceptSecurityContext error, data 52e, v893

請問各位先進,這是什麼錯誤呢??
另外小弟先講一下小弟的環境,小弟是用iptables做firewall,有三個lan,一是對外
一是DMZ(postfix放在這裡)最後是公司內部的LAN(Exchange 2000放在這裡)小弟原本是把DMZ的僅開放mail所用的port但是測不出來,所以小弟現在全開,但是也是一樣,不知ldap是走那幾個port,以及這種架構下會有問題嗎??小弟有把postfix的resole.conf的dns指定到內部的AD上,不知這個是不是也有影响,煩請各先進不吝指教,謝謝

99
Linux 討論版 / [問題]請問iptables的規則????
« 於: 2004-04-22 23:53 »
各位先進大家好
小弟目前遇到一個問題,就是在iptables裡,它的規則是以我們在script裡所寫的為準,還是是以/etc/sysconfig/iptables裡的為準,因為小弟目前有一script,用iptables-save之後去看,是nat 先,而不是filter先,因此小弟想若是以iptables-save來看,是nat先,那不就沒有filter的功能了,所以小弟想問一下,是否有記錯,因為同一支script跑,一個是以filter在上面先,而另一個卻是nat在上面,因此才會覺得很奇怪,煩請各位先進不吝指教,謝謝

100
酷!學園 精華區 / [問題]出現找不到execvp
« 於: 2004-04-21 16:26 »
請問小弟按照Pail兄安裝ntop,到最後用script來啟動,發生找不到execvp這個檔案,不知這個檔案是做什麼的,有人有遇到嗎????煩請各知,謝謝
小弟是用fedora

101
謝謝damon大大
小弟馬上去買來看看
找到方法再來這邊分享,謝謝

102
各位先進大家好:
小弟目前公司有一台exchange2000,但是害怕會中毒,公司又不願換掉,所以小弟想用postfix來做mail gateway,mail 先寄到postfix,沒問題就轉到內部的exchange,但是小弟查了很多的資料,都沒有找到,不知是否有先進有這方面的資料或是經驗,可以提供給小弟,謝謝.

103
謝謝jou及netman兩位的指導
感恩啦 :D

104
netman兄你好:
謝謝你的程式,這隻程式太好用了,太感謝你了
不過小弟想請問一下,這隻程式它跑出來是直接用iptables是嗎,還是有產生script檔呢,因為小弟找不到這隻程式產生出的script檔案在那,可以告知嗎??
小弟目前是用iptables-save來看,
另外小弟有個問題想請教,就是小弟沒有用PREROUTING及postrouting來讓封包進來,所以原本的script就無法讓外面的人進來是嗎??
謝謝指教

105
各位先進大家好:
小弟目前在試三張網卡的iptables,目前遇到一個困難,就是重內部到DMZ都可以過,但是從外部要到DMZ卻不能過,小弟是參考石牌國小李老師的去改,但是卻不能從外部連到DMZ,不知是那裡有問題,以下是小弟目前所用的iptables,請各位先進不吝指教,謝謝

代碼: [選擇]

# Generated by iptables-save v1.2.8 on Tue Apr  6 12:49:15 2004
*filter
:INPUT DROP [8416:610384]
:FORWARD DROP [326:15916]
:OUTPUT DROP [0:0]
:icmp_allowed - [0:0]
:tcp_allowed - [0:0]
-A INPUT -d 192.168.1.1 -i eth1 -j ACCEPT
-A INPUT -d 192.168.1.255 -i eth1 -j ACCEPT
-A INPUT -d 10.1.2.251 -i eth2 -j ACCEPT
-A INPUT -d 10.1.2.255 -i eth2 -j ACCEPT
-A INPUT -d 61.222.xxx.xx -m state --state RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -p tcp -m multiport --dports 135,445,137,138,139 -j DROP
-A FORWARD -p udp -m multiport --dports 135,445,137,138,139 -j DROP
-A FORWARD -i eth2 -j ACCEPT
-A FORWARD -i eth1 -j ACCEPT
-A FORWARD -i eth0 -m state --state RELATED,ESTABLISHED -j ACCEPT
-A FORWARD -s 192.168.1.3 -i eth1 -o eth0 -p udp -m udp --sport 53 --dport 53 -m state --state NEW -j ACCEPT
-A FORWARD -s 192.168.1.3 -i eth1 -o eth0 -p udp -m udp --sport 1024:65535 --dport 53 -m state --state NEW -j ACCEPT
-A FORWARD -s 192.168.1.3 -i eth1 -o eth0 -p tcp -m tcp --sport 1024:65535 --dport 53 -m state --state NEW -j ACCEPT
-A OUTPUT -s 127.0.0.1 -j ACCEPT
-A OUTPUT -s 10.1.2.251 -j ACCEPT
-A OUTPUT -s 192.168.1.1 -j ACCEPT
-A OUTPUT -s 61.222.xxx.xx -j ACCEPT
-A icmp_allowed -p icmp -m icmp --icmp-type 11 -j ACCEPT
-A icmp_allowed -p icmp -m icmp --icmp-type 8 -j ACCEPT
-A icmp_allowed -p icmp -j DROP
-A tcp_allowed -p tcp -m tcp --tcp-flags SYN,RST,ACK SYN -j ACCEPT
-A tcp_allowed -p tcp -m state --state RELATED,ESTABLISHED -j ACCEPT
-A tcp_allowed -p tcp -j DROP
COMMIT
# Completed on Tue Apr  6 12:49:15 2004
# Generated by iptables-save v1.2.8 on Tue Apr  6 12:49:15 2004
*nat
:PREROUTING ACCEPT [17640:1797914]
:POSTROUTING ACCEPT [12:738]
:OUTPUT ACCEPT [12:738]
:ping_death - [0:0]
:port_scan - [0:0]
:syn_flood - [0:0]
-A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG NONE -j DROP
-A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,SYN,RST,PSH,ACK,URG -j DROP
-A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,SYN -j DROP
-A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,PSH,URG -j DROP
-A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN -j DROP
-A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN,RST,PSH,ACK,URG FIN,SYN,PSH,URG -j DROP
-A PREROUTING -p tcp -m tcp --tcp-flags SYN,RST SYN,RST -j DROP
-A PREROUTING -p tcp -m tcp ! --tcp-flags SYN,RST,ACK SYN -m state --state NEW -j DROP
-A PREROUTING -p tcp -m tcp --tcp-flags FIN,SYN,RST,ACK RST -j port_scan
-A PREROUTING -p icmp -m icmp --icmp-type 8 -j ping_death
-A PREROUTING -s 10.0.0.0/255.0.0.0 -i eth0 -j DROP
-A PREROUTING -s 127.0.0.0/255.0.0.0 -i eth0 -j DROP
-A PREROUTING -s 172.16.0.0/255.240.0.0 -i eth0 -j DROP
-A PREROUTING -s 192.168.0.0/255.255.0.0 -i eth0 -j DROP
-A PREROUTING -s 224.0.0.0/240.0.0.0 -i eth0 -j DROP
-A PREROUTING -s 240.0.0.0/248.0.0.0 -i eth0 -j DROP
-A PREROUTING -d 61.222.xxx.xx -p tcp -m tcp --dport 25 -j DNAT --to-destination 192.168.1.3:25
-A PREROUTING -d 61.222.xxx.xx -p tcp -m tcp --dport 80 -j DNAT --to-destination 192.168.1.3:80
-A POSTROUTING -s 192.168.1.3 -o eth0 -j SNAT --to-source 61.222.xxx.xx
-A POSTROUTING -s 10.1.2.0/255.255.255.0 -o eth0 -j MASQUERADE
-A ping_death -m limit --limit 1/sec --limit-burst 4 -j RETURN
-A ping_death -j DROP
-A port_scan -m limit --limit 1/sec --limit-burst 4 -j RETURN
-A port_scan -j DROP
-A syn_flood -m limit --limit 3/min --limit-burst 3 -j RETURN
-A syn_flood -j DROP
COMMIT
# Completed on Tue Apr  6 12:49:15 2004
# Generated by iptables-save v1.2.8 on Tue Apr  6 12:49:15 2004
*mangle
:PREROUTING ACCEPT [152867:18780921]
:INPUT ACCEPT [218175:17100538]
:FORWARD ACCEPT [19382:7897021]
:OUTPUT ACCEPT [26260:6624488]
:POSTROUTING ACCEPT [19622:7974191]
COMMIT
# Completed on Tue Apr  6 12:49:15 2004

麻煩各位先進了,謝謝

頁: 1 2 3 [4]