Postfix reagiert nicht mehr

Postfix, QMail, Sendmail, Dovecot, Cyrus, Courier, Anti-Spam
thomas.km
Posts: 364
Joined: 2003-09-14 11:35
Location: Schleswig-Holstein

Postfix reagiert nicht mehr

Post by thomas.km » 2003-09-23 17:04

Hi

Habe das problem das ich mein postfix über webmin nicht mehr aufrufen kann. Auch mails versenden bzw empfangen geht nicht.....

Mail log.

Sep 23 16:53:13 p15142372 postfix/showq[16025]: fatal: bad string length (0 < 1): empty_address_recipient =
Sep 23 16:53:14 p15142372 postfix/master[29605]: warning: process /usr/lib/postfix/showq pid 16025 exit status 1
Sep 23 16:53:14 p15142372 postfix/master[29605]: warning: /usr/lib/postfix/showq: bad command startup -- throttling
Sep 23 16:53:34 p15142372 postfix/cleanup[16026]: fatal: bad string length (0 < 1): empty_address_recipient =
Sep 23 16:53:35 p15142372 postfix/master[29605]: warning: process /usr/lib/postfix/cleanup pid 16026 exit status 1
Sep 23 16:53:35 p15142372 postfix/master[29605]: warning: /usr/lib/postfix/cleanup: bad command startup -- throttling
Sep 23 16:54:14 p15142372 postfix/showq[16031]: fatal: bad string length (0 < 1): empty_address_recipient =
Sep 23 16:54:15 p15142372 postfix/master[29605]: warning: process /usr/lib/postfix/showq pid 16031 exit status 1
Sep 23 16:54:15 p15142372 postfix/master[29605]: warning: /usr/lib/postfix/showq: bad command startup -- throttling
Sep 23 16:54:35 p15142372 postfix/cleanup[16032]: fatal: bad string length (0 < 1): empty_address_recipient =
Sep 23 16:54:36 p15142372 postfix/master[29605]: warning: process /usr/lib/postfix/cleanup pid 16032 exit status 1
Sep 23 16:54:36 p15142372 postfix/master[29605]: warning: /usr/lib/postfix/cleanup: bad command startup -- throttling
Sep 23 16:55:15 p15142372 postfix/showq[16067]: fatal: bad string length (0 < 1): empty_address_recipient =
Sep 23 16:55:16 p15142372 postfix/master[29605]: warning: process /usr/lib/postfix/showq pid 16067 exit status 1
Sep 23 16:55:16 p15142372 postfix/master[29605]: warning: /usr/lib/postfix/showq: bad command startup -- throttling
Sep 23 16:55:36 p15142372 postfix/cleanup[16068]: fatal: bad string length (0 < 1): empty_address_recipient =
Sep 23 16:55:37 p15142372 postfix/master[29605]: warning: process /usr/lib/postfix/cleanup pid 16068 exit status 1
Sep 23 16:55:37 p15142372 postfix/master[29605]: warning: /usr/lib/postfix/cleanup: bad command startup -- throttling
Sep 23 16:56:16 p15142372 postfix/showq[16073]: fatal: bad string length (0 < 1): empty_address_recipient =
Sep 23 16:56:17 p15142372 postfix/master[29605]: warning: process /usr/lib/postfix/showq pid 16073 exit status 1
Sep 23 16:56:17 p15142372 postfix/master[29605]: warning: /usr/lib/postfix/showq: bad command startup -- throttling
Sep 23 16:56:37 p15142372 postfix/cleanup[16074]: fatal: bad string length (0 < 1): empty_address_recipient =
Sep 23 16:56:38 p15142372 postfix/master[29605]: warning: process /usr/lib/postfix/cleanup pid 16074 exit status 1
Sep 23 16:56:38 p15142372 postfix/master[29605]: warning: /usr/lib/postfix/cleanup: bad command startup -- throttling
Sep 23 16:57:17 p15142372 postfix/showq[16082]: fatal: bad string length (0 < 1): empty_address_recipient =
Sep 23 16:57:18 p15142372 postfix/master[29605]: warning: process /usr/lib/postfix/showq pid 16082 exit status 1
Sep 23 16:57:18 p15142372 postfix/master[29605]: warning: /usr/lib/postfix/showq: bad command startup -- throttling
Sep 23 16:57:38 p15142372 postfix/cleanup[16083]: fatal: bad string length (0 < 1): empty_address_recipient =
Sep 23 16:57:39 p15142372 postfix/master[29605]: warning: process /usr/lib/postfix/cleanup pid 16083 exit status 1
Sep 23 16:57:39 p15142372 postfix/master[29605]: warning: /usr/lib/postfix/cleanup: bad command startup -- throttling
Sep 23 16:58:18 p15142372 postfix/showq[16146]: fatal: bad string length (0 < 1): empty_address_recipient =
Sep 23 16:58:19 p15142372 postfix/master[29605]: warning: process /usr/lib/postfix/showq pid 16146 exit status 1
Sep 23 16:58:19 p15142372 postfix/master[29605]: warning: /usr/lib/postfix/showq: bad command startup -- throttling
Sep 23 16:58:39 p15142372 postfix/cleanup[16147]: fatal: bad string length (0 < 1): empty_address_recipient =
Sep 23 16:58:40 p15142372 postfix/master[29605]: warning: process /usr/lib/postfix/cleanup pid 16147 exit status 1
Sep 23 16:58:40 p15142372 postfix/master[29605]: warning: /usr/lib/postfix/cleanup: bad command startup -- throttling


Ich poste hier mal mein Problem was ich habe, vielleicht hängt es damit zusammen.


Hi

Ich habe bei confixx einen Endkunden erstellt. habe eine pop3 Account erstellt (web4p2) und eine Mail Adresse XX@meine-domain.den die das Web4p2 Konto benutzt.

Nun nwenn ich es in Outlook einrichte funzt alles will ich aber von der besagten Mail Addy aus was versenden sagt er immer
:554 <XXXX@gmx.de>: Recipient address rejected: Relay access denied

genua das gleiche wenn ich an mich selber die Mail schicke, dann kommt aber user unkown.

kann mir jemand helfen?

Habe postfix laufen suse8.1 confix 2.0

EDIT: Auszug aus mail log:

Sep 22 20:13:18 p15142372 popper[21461]: Stats: web4p2 0 0 0 0 localhost.localdomain 127.0.0.1 [pop_updt.c:296]
Sep 22 20:13:23 p15142372 popper[21463]: Stats: web4p2 0 0 0 0 pD9527F4C.dip.t-dialin.net 217.82.127.76 [pop_updt.c:296]
Sep 22 20:13:23 p15142372 popper[21462]: Stats: web1p1 0 0 0 0 pD9527F4C.dip.t-dialin.net 217.82.127.76 [pop_updt.c:296]
Sep 22 20:13:29 p15142372 popper[21466]: Stats: web4p2 0 0 0 0 localhost.localdomain 127.0.0.1 [pop_updt.c:296]
Sep 22 20:13:32 p15142372 popper[21469]: Stats: web4p2 0 0 0 0 localhost.localdomain 127.0.0.1 [pop_updt.c:296]
Sep 22 20:13:49 p15142372 popper[21542]: Stats: web4p2 0 0 0 0 localhost.localdomain 127.0.0.1 [pop_updt.c:296]
Sep 22 20:13:52 p15142372 popper[21544]: Stats: web4p2 0 0 0 0 pD9527F4C.dip.t-dialin.net 217.82.127.76 [pop_updt.c:296]
Sep 22 20:13:52 p15142372 popper[21543]: Stats: web1p1 0 0 0 0 pD9527F4C.dip.t-dialin.net 217.82.127.76 [pop_updt.c:296]
Sep 22 20:14:09 p15142372 postfix/smtpd[21549]: connect from pD9527F4C.dip.t-dialin.net[217.82.127.76]
Sep 22 20:14:09 p15142372 postfix/smtpd[21549]: E379120406B: client=pD9527F4C.dip.t-dialin.net[217.82.127.76]
Sep 22 20:14:09 p15142372 postfix/smtpd[21549]: reject: RCPT from pD9527F4C.dip.t-dialin.net[217.82.127.76]: 554 <tnd600@gmx.de>: Recipient address rejected: Relay access denied; from=<wm@ivao-germany.de> to=<tnd600@gmx.de>
Sep 22 20:14:17 p15142372 postfix/smtpd[21549]: disconnect from pD9527F4C.dip.t-dialin.net[217.82.127.76]
Sep 22 20:14:31 p15142372 popper[21552]: Stats: web4p2 0 0 0 0 localhost.localdomain 127.0.0.1 [pop_updt.c:296]
Sep 22 20:17:55 p15142372 popper[21639]: Stats: web4p2 0 0 0 0 pD9527F4C.dip.t-dialin.net 217.82.127.76 [pop_updt.c:296]
Sep 22 20:17:55 p15142372 popper[21638]: Stats: web1p1 0 0 0 0 pD9527F4C.dip.t-dialin.net 217.82.127.76 [pop_updt.c:296]


EDIT2: MX1 ist auf meinem Server nicht bei 1 und 1

thomas.km
Posts: 364
Joined: 2003-09-14 11:35
Location: Schleswig-Holstein

Re: Postfix reagiert nicht mehr

Post by thomas.km » 2003-09-23 17:42

Hi

hier nochmal die postfix man.cf.

Habe sie die comments weg gelassen. Hoffentlich nicht zu viel weggenommen.


command_directory = /usr/sbin
daemon_directory = /usr/lib/postfix
default_privs = autoresp
myhostname = p15142372.pureserver.info
mydomain = ivao-de.net
mynetworks_style = host
local_recipient_maps = $alias_maps unix:passwd.byname
in_flow_delay = 0
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
mail_spool_directory = /var/mail
fast_flush_domains = $relay_domains
smtpd_banner = $myhostname ESMTP $mail_name
debug_peer_level = 2
debugger_command =
PATH=/usr/bin:/usr/X11R6/bin
xxgdb $daemon_directory/$process_name $process_id & sleep 5
sendmail_path = /usr/sbin/sendmail
newaliases_path = /usr/sbin/sendmail
mailq_path = /usr/bin/mailq
setgid_group = maildrop
manpage_directory = /usr/share/man
sample_directory = /usr/share/doc/packages/postfix/samples
readme_directory = /usr/share/doc/packages/postfix/README_FILES
#suseconfig:
canonical_maps = hash:/etc/postfix/canonical
virtual_maps = hash:/etc/postfix/virtual
relocated_maps = hash:/etc/postfix/relocated
transport_maps = hash:/etc/postfix/transport
sender_canonical_maps = hash:/etc/postfix/sender_canonical
masquerade_exceptions = root
masquerade_classes = envelope_sender, header_sender, header_recipient
masquerade_domains = ivao-de.net
smtpd_sender_restrictions = hash:/etc/postfix/access
smtpd_client_restrictions =
strict_rfc821_envelopes = no
#smtpd_recipient_restrictions = permit_mynetworks,check_relay_domains
smtpd_recipient_restrictions = permit_mynetworks,check_relay_domains

#SMTPD Auth
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
broken_sasl_auth_clients = yes

#TLS Support
smtpd_use_tls = yes
#smtpd_tls_auth_only = yes
smtpd_tls_key_file = /etc/postfix/key.pem
smtpd_tls_cert_file = /etc/postfix/cert.pem
smtpd_tls_CAfile = /etc/postfix/cacert.pem
smtpd_tls_loglevel = 1
smtpd_tls_received_header = yes
smtpd_tls_session_cache_timeout = 3600s
tls_random_source = dev:/dev/urandom

defer_transports =
disable_dns_lookups = no
content_filter =
mailbox_command =
mailbox_transport =
smtpd_helo_required = no
smtpd_helo_restrictions =
empty_address_recipient =
relayhost = smtp.ivao-de.net
inet_interfaces = all
mydestination = $myhostname, localhost.$mydomain

thomas.km
Posts: 364
Joined: 2003-09-14 11:35
Location: Schleswig-Holstein

Re: Postfix reagiert nicht mehr

Post by thomas.km » 2003-09-23 19:21

Hi

Habe nochmals alles gecheckt. Aber immer wenn ich Mails verschicken will egal welche adresse kommt realy access denied.

letzter mail log

Sep 23 19:04:15 p15142372 popper[22863]: Stats: web4p1 0 0 0 0 p5086BF4F.dip.t-dialin.net 80.134.191.79 [pop_updt.c:296]
Sep 23 19:06:03 p15142372 popper[22906]: Stats: web4p1 0 0 0 0 p5086BF4F.dip.t-dialin.net 80.134.191.79 [pop_updt.c:296]
Sep 23 19:07:03 p15142372 popper[22914]: Stats: web4p1 0 0 0 0 p5086BF4F.dip.t-dialin.net 80.134.191.79 [pop_updt.c:296]
Sep 23 19:11:59 p15142372 postfix/smtpd[22969]: connect from p5086BF4F.dip.t-dialin.net[80.134.191.79]
Sep 23 19:11:59 p15142372 postfix/smtpd[22969]: ABA3320406B: client=p5086BF4F.dip.t-dialin.net[80.134.191.79]
Sep 23 19:11:59 p15142372 postfix/smtpd[22969]: reject: RCPT from p5086BF4F.dip.t-dialin.net[80.134.191.79]: 554 <tnd600@gmx.de>: Recipient address rejected: Relay access denied; from=<marcus@ivao-de.net> to=<tnd600@gmx.de>
Sep 23 19:12:05 p15142372 popper[22976]: Stats: web4p1 0 0 0 0 p5086BF4F.dip.t-dialin.net 80.134.191.79 [pop_updt.c:296]
Sep 23 19:12:07 p15142372 postfix/smtpd[22969]: disconnect from p5086BF4F.dip.t-dialin.net[80.134.191.79]
Sep 23 19:13:38 p15142372 postfix/smtpd[22969]: connect from p5086BF4F.dip.t-dialin.net[80.134.191.79]
Sep 23 19:13:38 p15142372 postfix/smtpd[22969]: A82F620406B: client=p5086BF4F.dip.t-dialin.net[80.134.191.79]
Sep 23 19:13:38 p15142372 postfix/cleanup[22970]: A82F620406B: message-id=<20030923171338.A82F620406B@ivao-de.net>
Sep 23 19:13:38 p15142372 postfix/qmgr[22713]: A82F620406B: from=<marcus@ivao-de.net>, size=630, nrcpt=1 (queue active)
Sep 23 19:13:38 p15142372 postfix/smtpd[22969]: disconnect from p5086BF4F.dip.t-dialin.net[80.134.191.79]
Sep 23 19:13:38 p15142372 postfix/local[22987]: A82F620406B: to=<marcus@ivao-de.net>, relay=local, delay=0, status=bounced (unknown user: "marcus")
Sep 23 19:13:38 p15142372 postfix/cleanup[22970]: F00DC204070: message-id=<20030923171338.F00DC204070@ivao-de.net>
Sep 23 19:13:38 p15142372 postfix/qmgr[22713]: F00DC204070: from=<>, size=2139, nrcpt=1 (queue active)
Sep 23 19:13:39 p15142372 postfix/local[22987]: F00DC204070: to=<marcus@ivao-de.net>, relay=local, delay=0, status=bounced (unknown user: "marcus")
Sep 23 19:13:39 p15142372 popper[22990]: Stats: web4p1 0 0 0 0 p5086BF4F.dip.t-dialin.net 80.134.191.79 [pop_updt.c:296]

r00ty
Posts: 747
Joined: 2003-03-17 15:32

Re: Postfix reagiert nicht mehr

Post by r00ty » 2003-09-24 11:23

also irgendwie ist deine Config komisch:
benutzt du nun smpt_auth oder nicht ?
wenn ja soltle das hier auch drinnen stehen

Code: Select all

smtpd_recipient_restrictions = permit_mynetworks, check_relay_domains
da fehlt mir

Code: Select all

permit_sasl_authenticated, reject_unauth_destination
und das den checlk_realay_domains ist ne gefährliche Sache. Das ist ja ein quasi offenes realy, wenn da irgendwelche Domains von dir drinnenstehen
zudem meine ich in dem Log zu sehen, dass am Client eh smtp-auth nicht aktiviert ist. Das sollte antürlich aktiv sein und die Config (hash:/etc/postfix/virtual ) müssen natürlich auch stimmen

thomas.km
Posts: 364
Joined: 2003-09-14 11:35
Location: Schleswig-Holstein

Re: Postfix reagiert nicht mehr

Post by thomas.km » 2003-09-24 11:35

Hi

hier nochmal meine akt. main.cf vielleicht kannst du mir sagen was da ned stimmt


# Global Postfix configuration file. This file lists only a subset
# of all 100+ 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.
#

# The command_directory parameter specifies the location of all
# postXXX commands. The default value is $program_directory.
#
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). The
# default value is $program_directory. This directory must be owned
# by root.
#
daemon_directory = /usr/lib/postfix

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

# 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 = ivao-de.net
#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 = ivao-de.net

# 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.
#
#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].
#
#inet_interfaces = all
#inet_interfaces = $myhostname
#inet_interfaces = $myhostname, localhost

# The mydestination parameter specifies the list of domains that this
# machine considers itself the final destination for. That includes
# Sendmail-style virtual domains hosted on this machine.
#
# Do not include Postfix-style virtual domains - those domains are
# specified elsewhere (see sample-virtual.cf, and sample-transport.cf).
#
# The default is $myhostname + localhost.$mydomain. On a mail domain
# gateway, you should also include $mydomain. Do not specify the
# names of domains that this machine is backup MX host for. Specify
# those names via the relay_domains or permit_mx_backup settings for
# the SMTP server (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. Continue long lines by starting the
# next line with whitespace.
#
#mydestination = $myhostname, localhost.$mydomain
#mydestination = $myhostname, localhost.$mydomain $mydomain
#mydestination = $myhostname, localhost.$mydomain, $mydomain,
# mail.$mydomain, http://www.$mydomain, ftp.$mydomain

# 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 = 168.100.189.0/28, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table

# The relay_domains parameter restricts what clients this mail system
# will relay mail from, or 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 whose IP address matches $mynetworks,
# - from "trusted" clients matching $relay_domains or subdomains thereof,
# - 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_maps.
# 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

# 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 LOCAL USERS
#
# The local_recipient_maps parameter specifies optional lookup tables
# with all names (not 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.
#
# If you use the default Postfix local delivery agent for local
# delivery, uncomment the definition below.
#
# Beware: if the Postfix SMTP server runs chrooted, you may have to
# copy the passwd (not shadow) database into the jail. This is
# system dependent.
#
#local_recipient_maps = $alias_maps unix:passwd.byname

# 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 50 SMTP server process
# limit, this limits the mail inflow to 50 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/aliases
#alias_maps = hash:/etc/aliases, nis:mail.aliases
#alias_maps = netinfo:/aliases

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

# 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.
#
#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.
#
#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 local recipients
# is bounced.
#
# 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.
#
#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. Patterns are matched
# in the specified order, and the search stops upon the first match.
# When a pattern matches, what happens next depends on the associated
# action that is specified in the right-hand side of the table:
#
# REJECT the entire message is rejected.
# REJECT text.... The text is sent to the originator.
# IGNORE the header line is silently discarded.
# WARN the header is logged (not rejected) with a warning message.
# WARN text... as above, and the text is logged, too.
#
# These patterns do not apply to MIME headers in the message body.
#
# See also the body_checks example in the sample-filter.cf file.
#
#header_checks = regexp:/etc/postfix/header_checks

# FAST ETRN SERVICE
#
# Postfix maintains per-destination logfiles with information about
# deferred mail, so that mail can be flushed quickly with the SMTP
# "ETRN domain.tld" command, or by executing "sendmail -qRdomain.tld".
#
# 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 = 10

# 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=/usr/bin:/usr/X11R6/bin
xxgdb $daemon_directory/$process_name $process_id & 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/sbin/sendmail

# 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 = maildrop

maps_rbl_domains = relays.ordb.org proxy.relays.osirusoft.com socks.relays.osirusoft.com

smtpd_recipient_restrictions = permit_mynetworks, check_relay_domains


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

# sample_directory: The location of the Postfix sample configuration files.
#
sample_directory = /usr/share/doc/packages/postfix/samples

# readme_directory: The location of the Postfix README files.
#
readme_directory = /usr/share/doc/packages/postfix/README_FILES
mail_spool_directory = /var/mail
canonical_maps = hash:/etc/postfix/canonical
virtual_maps = hash:/etc/postfix/virtual
relocated_maps = hash:/etc/postfix/relocated
transport_maps = hash:/etc/postfix/transport
sender_canonical_maps = hash:/etc/postfix/sender_canonical
masquerade_exceptions = root
masquerade_classes = envelope_sender, header_sender, header_recipient
masquerade_domains = ivao-de.info
defer_transports =
disable_dns_lookups = no
content_filter =
mailbox_command =
mailbox_transport =
smtpd_sender_restrictions = hash:/etc/postfix/access
strict_rfc821_envelopes = no
alias_maps = hash:/etc/aliases
mydestination = ivao-de.net
myhostname = ivao-de.net




und hier die virtual


#
# VIRTUAL(5) VIRTUAL(5)
#
# NAME
# virtual - format of Postfix virtual table
#
# SYNOPSIS
# postmap /etc/postfix/virtual
#
# DESCRIPTION
# The optional virtual table specifies address redirections
# for local and non-local recipients or domains. The redi-
# rections are used by the cleanup(8) daemon. The redirec-
# tions are recursive.
#
# The virtual redirection is applied only to recipient enve-
# lope addresses, and does not affect message headers.
# Think Sendmail rule set S0, if you like. Use canonical(5)
# mapping to rewrite header and envelope addresses in gen-
# eral.
#
# Normally, the virtual table is specified as a text file
# that serves as input to the postmap(1) command. The
# result, an indexed file in dbm or db format, is used for
# fast searching by the mail system. Execute the command
# postmap /etc/postfix/virtual in order to rebuild the
# indexed file after changing the text file.
#
# When the table is provided via other means such as NIS,
# LDAP or SQL, the same lookups are done as for ordinary
# indexed files.
#
# Alternatively, the table can be provided as a regular-
# expression map where patterns are given as regular expres-
# sions. In that case, the lookups are done in a slightly
# different way as described below.
#
# POSTFIX-STYLE VIRTUAL DOMAINS
# With a Postfix-style virtual domain, the virtual domain
# has its own user name space. Local (i.e. non-virtual)
# usernames are not visible in a Postfix-style virtual
# domain. In particular, local aliases(5) and mailing lists
# are not visible as localname@virtual.domain.
#
# Use a Sendmail-style virtual domain (see below) if local
# usernames, aliases(5) or mailing lists should be visible
# as localname@virtual.domain.
#
# Support for a Postfix-style virtual domain looks like:
#
# /etc/postfix/virtual:
# virtual.domain anything (right-hand content does not matter)
# postmaster@virtual.domain postmaster
# user1@virtual.domain address1
# user2@virtual.domain address2, address3
#
# The virtual.domain anything entry is required for a Post-
# fix-style virtual domain.
#
# Do not list a Postfix-style virtual domain in the main.cf
# mydestination configuration parameter. Such an entry is
# required only for a Sendmail-style virtual domain.
#
# With a Postfix-style virtual domain, the Postfix SMTP
# server accepts mail for known-user@virtual.domain and
# rejects mail for unknown-user@virtual.domain as undeliver-
# able.
#
# SENDMAIL-STYLE VIRTUAL DOMAINS
# With a Sendmail-style virtual domain, every local (i.e.
# non-virtual) username is visible in the virtual domain. In
# particular, every local alias and mailing list is visible
# as localname@virtual.domain.
#
# Use a Postfix-style virtual domain (see above) if local
# usernames, aliases(5) or mailing lists should not be visi-
# ble as localname@virtual.domain.
#
# Support for a Sendmail-style virtual domain looks like:
#
# /etc/postfix/main.cf:
# mydestination = $myhostname localhost.$mydomain $mydomain
# virtual.domain
#
# /etc/postfix/virtual:
# user1@virtual.domain address1
# user2@virtual.domain address2, address3
#
# The main.cf mydestination entry is required for a Send-
# mail-style virtual domain.
#
# Do not specify a virtual.domain anything virtual map entry
# for a Sendmail-style virtual domain. Such an entry is
# required only with a Postfix-style virtual domain.
#
# With a Sendmail-style virtual domain, the Postfix local
# delivery agent delivers mail for an unknown user@vir-
# tual.domain to a local (i.e. non-virtual) user that has
# the same name; if no such recipient exists, the Postfix
# local delivery agent bounces the mail to the sender.
#
# TABLE FORMAT
# The format of the virtual table is as follows, mappings
# being tried in the order as listed in this manual page:
#
# pattern result
# When pattern matches a mail address, replace it by
# the corresponding result.
#
# blank lines and comments
# Empty lines and whitespace-only lines are ignored,
# as are lines whose first non-whitespace character
# is a `#'.
#
# multi-line text
# A logical line starts with non-whitespace text. A
# line that starts with whitespace continues a logi-
# cal line.
#
# With lookups from indexed files such as DB or DBM, or from
# networked tables such as NIS, LDAP or SQL, patterns are
# tried in the order as listed below:
#
# user@domain address, address, ...
# Mail for user@domain is redirected to address.
# This form has the highest precedence.
#
# user address, address, ...
# Mail for user@site is redirected to address when
# site is equal to $myorigin, when site is listed in
# $mydestination, or when it is listed in
# $inet_interfaces.
#
# This functionality overlaps with functionality of
# the local alias(5) database. The difference is that
# virtual mapping can be applied to non-local
# addresses.
#
# @domain address, address, ...
# Mail for any user in domain is redirected to
# address. This form has the lowest precedence.
#
# In all the above forms, when address has the form @other-
# domain, the result is the same user in otherdomain. This
# works for the first address in the expansion only.
#
# ADDRESS EXTENSION
# When a mail address localpart contains the optional recip-
# ient delimiter (e.g., user+foo@domain), the lookup order
# becomes: user+foo@domain, user@domain, user+foo, user, and
# @domain. An unmatched address extension (+foo) is propa-
# gated to the result of table lookup.
#
# REGULAR EXPRESSION TABLES
# This section describes how the table lookups change when
# the table is given in the form of regular expressions. For
# a description of regular expression lookup table syntax,
# see regexp_table(5) or pcre_table(5).
#
# Each pattern is a regular expression that is applied to
# the entire address being looked up. Thus, user@domain mail
# addresses are not broken up into their user and @domain
# constituent parts, nor is user+foo broken up into user and
# foo.
#
# Patterns are applied in the order as specified in the
# table, until a pattern is found that matches the search
# string.
#
# Results are the same as with indexed file lookups, with
# the additional feature that parenthesized substrings from
# the pattern can be interpolated as $1, $2 and so on.
#
# BUGS
# The table format does not understand quoting conventions.
#
# CONFIGURATION PARAMETERS
# The following main.cf parameters are especially relevant
# to this topic. See the Postfix main.cf file for syntax
# details and for default values. Use the postfix reload
# command after a configuration change.
#
# virtual_maps
# List of virtual mapping tables.
#
# Other parameters of interest:
#
# inet_interfaces
# The network interface addresses that this system
# receives mail on.
#
# mydestination
# List of domains that this mail system considers
# local.
#
# myorigin
# The domain that is appended to locally-posted mail.
#
# owner_request_special
# Give special treatment to owner-xxx and xxx-request
# addresses.
#
# SEE ALSO
# cleanup(8) canonicalize and enqueue mail
# postmap(1) create mapping table
# pcre_table(5) format of PCRE tables
# regexp_table(5) format of POSIX regular expression tables
#
# LICENSE
# The Secure Mailer license must be distributed with this
# software.
#
# AUTHOR(S)
# Wietse Venema
# IBM T.J. Watson Research
# P.O. Box 704
# Yorktown Heights, NY 10598, USA
#
# 1
#
Marcus web4p1

thomas.km
Posts: 364
Joined: 2003-09-14 11:35
Location: Schleswig-Holstein

Re: Postfix reagiert nicht mehr

Post by thomas.km » 2003-09-24 11:43

Hi

ok mails empfangen geht nun aber nicht senden.

Egal an welche Mail Addy ich sende es kommt immer:

554 <tnd600@gmx.de>: Recipient address rejected: Relay access denied

r00ty
Posts: 747
Joined: 2003-03-17 15:32

Re: Postfix reagiert nicht mehr

Post by r00ty » 2003-09-24 12:48

so, grad wollte ich dir ne Antwort schreiben, aber mir fällt auf, dass du ja confixx benutzt, oder ?

wie kommte es dann, dass in der config gar nix von confixx steht ?!?

das hier ist ne ordentliche config: (für suse 8.1 @ 1und1)
http://www.rootforum.org/forum/viewtop ... highlight=
^-- bei smtpd_recipient_restrictions noch permit_mynetworks dazu

zudem stimmt dein

Code: Select all

smtpd_recipient_restrictions
definitiv nicht

p.s.: bitte bitte poste beim nächsten mal nicht du unnötigen comments....

thomas.km
Posts: 364
Joined: 2003-09-14 11:35
Location: Schleswig-Holstein

Re: Postfix reagiert nicht mehr

Post by thomas.km » 2003-09-24 13:08

Hi

Hat wunderbar geklappt

Vielen dank an dich.

Eine frage noch. Habe ich nun in der main.cf (habe die einfach übernommen die du mir gepostet hast und habe meine domain ersetzt und host) auch alles getan um ein open relay auf meinem server zu verhindern? Also ist klar mann kann mehr tun aber nur von seiten der configmöglichkeiten in der main.cf

r00ty
Posts: 747
Joined: 2003-03-17 15:32

Re: Postfix reagiert nicht mehr

Post by r00ty » 2003-09-24 14:06

mit der config bist du sicher gegen ein relay...
du kannst auch nochmal
http://www.abuse.net/relay.html
drüber laufen lassen (<- wobei dass auch keine 100%tiger Nachweis ist)

Normalerweise sollte nichts passieren, weil du ja mit dieser config nur smtp-auth zulässt

thomas.km
Posts: 364
Joined: 2003-09-14 11:35
Location: Schleswig-Holstein

Re: Postfix reagiert nicht mehr

Post by thomas.km » 2003-09-24 14:14

Hi

Vielen dank.

Habe da noch eine etwas andere Frage. Und zwar will ich über webmin einen user anlegen der nur FTP Zugang bekommen soll. Leider weis ich nciht wie ich das machen soll da er ja nur bis auf eine bestimmte Directory Ebene kommen soll,bloß das kann ich nicht beim ersten definieren. Auch wenn ich als usergruppe FTP only angebe, kann ich mich nicht einloggen.

Any ideas? sowas zu lösen?

r00ty
Posts: 747
Joined: 2003-03-17 15:32

Re: Postfix reagiert nicht mehr

Post by r00ty » 2003-09-24 20:24

also ich hab kein plan vom Webmin....
aber dazu gibts nen Haufen posts im Forum
(p.s.: confixx kann auch ftp user anlegen)

thomas.km
Posts: 364
Joined: 2003-09-14 11:35
Location: Schleswig-Holstein

Re: Postfix reagiert nicht mehr

Post by thomas.km » 2003-09-24 20:38

Hi

Das mit confixx ist richtig, hilft mir aber nicht da, man nur FTP user auf Kundenebene erstellen kann. Ich brauche ihn aber auf reseller ebene mit er Zugriff auf alle Kunnden über FTP hat.

Any ideas?

r00ty
Posts: 747
Joined: 2003-03-17 15:32

Re: Postfix reagiert nicht mehr

Post by r00ty » 2003-09-24 21:18

uiuiui

das halte ich für ein gewagtes vorhaben.....
welcher sinn hätte so eine Aktion ?
(du müsstest halt mal schauen wei confixx die ftp-user einträgt bzw. doch mal die Forumsuche bemühen :)