Großes Postfix Problem - Mails können nicht empfangen werden

Postfix, QMail, Sendmail, Dovecot, Cyrus, Courier, Anti-Spam
taker
Posts: 71
Joined: 2004-01-25 14:08

Großes Postfix Problem - Mails können nicht empfangen werden

Post by taker » 2004-04-25 16:15

Hallo,

also mein Rootserver läuft jetzt soweit recht gut und ich bin mit mir selber schon recht zufrieden.. Zufrieden soweit das ich schon viel gelernt habe! Daher auch mal DANKE an Euch hier weil ich mir hier viel angelesen habe!

Zum Thema:

Ich hab mich jetzt mal mit dem MailServer meines Rooties beschäftigt..
Auf meinem Server läuft (standartmäßig) Postfix! Das Ganze auf Suse 8,1 Basis. Is nen 1und1 Rootie!

Jetzt ist das Problem wie folgt, ich Kann zwar vom Panal aus (Confixx 2) Mails verschicken zb. an meine "GMX ADRESSE" aber ich kann keine empfangen. Ich bekomme auch keine Fehlermail zurück geschickt.. Gar nix es sieht so aus als ob die Mail im Nirvana verschwindet.. Ich hab keine Ahnung Warum?!

Das Problem tritt immer auf , auch wenn ich von name@meinedomain.de an eine andere Mail Addy sende, wie zb. name2@meinedomain.de
=> AUch Intern keine funktion.

Ich bekomme, wi ebeschrieben, keine Meldung zurück.. Rein Gar NICHTS!

An was kann das liegen, bzw. was bräuchtet ihr um mir genauer zu helfen? Habe im 1und1 Panal (interface) meinen mailserver auf meine Domain gelegt, also "Eigenes MailSystem" verwenden.. Hoffe dass das richtig war..

Hoffe es hilft mir jemand, bin schon am Verzweifeln.

Grüße

Taker

schl
Posts: 343
Joined: 2003-02-05 11:26
Location: München/Unterschleißheim

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by schl » 2004-04-25 16:17

und wo sind die logeinträge?

<glaskugel> falsche konfiguration </glaskugel>

ffl
Userprojekt
Userprojekt
Posts: 269
Joined: 2002-10-23 08:28
Location: Karlsruhe

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by ffl » 2004-04-25 16:21

<loriot>Ach!</loriot>

SCNR

Im Ernst: /var/log/mail.log bzw. syslog. Schau da mal rein was abgeht :)

taker
Posts: 71
Joined: 2004-01-25 14:08

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by taker » 2004-04-25 19:06

Also das Hier war in der "mail"

Code: Select all

Apr 25 18:52:53 p15149767 postfix/master[13176]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 25 18:53:35 p15149767 popper[5361]: Stats: web1p1 0 0 0 0 pD9E5434A.dip.t-dialin.net 217.229.67.74 [pop_updt.c:296]
Apr 25 18:53:53 p15149767 postfix/smtpd[5362]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 25 18:53:54 p15149767 postfix/master[13176]: warning: process /usr/lib/postfix/smtpd pid 5362 exit status 1
Apr 25 18:53:54 p15149767 postfix/master[13176]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 25 18:54:36 p15149767 popper[5368]: Stats: web1p1 0 0 0 0 pD9E5434A.dip.t-dialin.net 217.229.67.74 [pop_updt.c:296]
Apr 25 18:54:54 p15149767 postfix/smtpd[5369]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 25 18:54:55 p15149767 postfix/master[13176]: warning: process /usr/lib/postfix/smtpd pid 5369 exit status 1
Apr 25 18:54:55 p15149767 postfix/master[13176]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 25 18:55:55 p15149767 postfix/smtpd[5384]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 25 18:55:56 p15149767 postfix/master[13176]: warning: process /usr/lib/postfix/smtpd pid 5384 exit status 1
Apr 25 18:55:56 p15149767 postfix/master[13176]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 25 18:56:56 p15149767 postfix/smtpd[5398]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 25 18:56:57 p15149767 postfix/master[13176]: warning: process /usr/lib/postfix/smtpd pid 5398 exit status 1
Apr 25 18:56:57 p15149767 postfix/master[13176]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 25 18:57:57 p15149767 postfix/smtpd[5409]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 25 18:57:58 p15149767 postfix/master[13176]: warning: process /usr/lib/postfix/smtpd pid 5409 exit status 1
Apr 25 18:57:58 p15149767 postfix/master[13176]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling



So.. Hoffe das hilft euch weiter...

Hoffende Grüße

Taker

mackshot
Posts: 16
Joined: 2004-03-28 17:22

lol

Post by mackshot » 2004-04-25 19:09

der versucht auf die datei /usr/local/etc/postfix/relaydomains.db zuzugreifen! diese gibt es aber nicht und somit ist der hund begraben!

einfach den richtigen pfad einstellen, bzw das auskommentieren :D

taker
Posts: 71
Joined: 2004-01-25 14:08

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by taker » 2004-04-25 19:20

Habs mal in der main.cf auskommentiert.. Postfix neu gestartet und gut.. So jetzt hab ich von nem "Fremden" konto aus ne mail geschickt.. Da komm folgendes Zurück:
Hi. This is the qmail-send program at mail.xyz.de.
I'm afraid I wasn't able to deliver your message to the following addresses. This is a permanent error; I've given up. Sorry it didn't work out.

<Mail@meinedomain.de>: 217.160.207.65_does_not_like_recipient./Remote_host_said:_554_<xyz@xyz.de>:_Recipient_address_rejected:_Relay_access_denied/Giving_up_on_217.160.207.65./
Desweiteren ist im Confixx jetzt der Fehler "Unknown key"

Dick in Rot auf der RECHTEN Seite.. Unter Hilfe..

Ich hab nach der .db datei gesucht aber hab nichts gefunden! Kanns sein das ich die von Confixx nutzen muss?!

Grüße

Taker
Last edited by taker on 2009-01-25 20:39, edited 1 time in total.

mackshot
Posts: 16
Joined: 2004-03-28 17:22

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by mackshot » 2004-04-25 19:30

ich benutze auch confixx und habe sie auskommentiert bisjetzt ohne probleme! hast du denn die ganze zeile auskommentiert? das solltest du nämlich machen und nicht nur ab "hash"

desweiteren glaube ich, dass diese mail die du bekommen hast einfach nur eine von FRÃ?HER ist, wo er jetzt aufgegeben hat sie an dich zu schicken, weil es keinen sinn hat


p.s.: wär gut, wenn jemand mit mehr ahnung helfen könnte, ich bin ja auch net der beste :lol:

taker
Posts: 71
Joined: 2004-01-25 14:08

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by taker » 2004-04-25 19:41

Code: Select all

#relay_domains = $mydestination, hash:/usr/local/etc/postfix/relaydomains
habs ganz auskommentiert.. geht aber trotzdem net.. schnief...

Taker

mackshot
Posts: 16
Joined: 2004-03-28 17:22

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by mackshot » 2004-04-25 19:42

was steht denn jetzt in der mail.log wenn du ne mail wegschickst?

taker
Posts: 71
Joined: 2004-01-25 14:08

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by taker » 2004-04-25 21:05

Code: Select all

Apr 25 19:42:15 p15149767 postfix/qmgr[8838]: 79A777BC95: from=<root@xyz.de>, size=4586, nrcpt=1 (queue active)
Apr 25 19:42:15 p15149767 postfix/qmgr[8838]: 8ABBF7BC96: from=<root@xyz.de>, size=1372, nrcpt=1 (queue active)
Apr 25 19:42:15 p15149767 postfix/smtpd[9000]: reject: RCPT from pop.xyz.de[213.165.64.20]: 554 <xyz@xyz.de>: Recipient address rejected: Relay access denied; from=<xyz@xyz.de> to=<xyz@xyz.de>
Apr 25 19:42:15 p15149767 postfix/smtp[9031]: warning: mailer loop: best MX host for xyz is local
Apr 25 19:42:15 p15149767 postfix/smtp[9032]: warning: mailer loop: best MX host for xyz is local
Apr 25 19:42:15 p15149767 postfix/smtp[9034]: warning: mailer loop: best MX host for xyz is local
Apr 25 19:42:15 p15149767 postfix/smtp[9031]: 506067BC24: to=<root@xyz.de>, relay=none, delay=0, status=bounced (mail for xyz.de loops back to myself)
Apr 25 19:42:15 p15149767 postfix/cleanup[9028]: B921A7BC97: message-id=<20040425174215.B921A7BC97@p15149767.pureserver.info>
Apr 25 19:42:15 p15149767 postfix/qmgr[8838]: B921A7BC97: from=<>, size=2992, nrcpt=1 (queue active)
Apr 25 19:42:15 p15149767 postfix/smtp[9031]: warning: mailer loop: best MX host for xyz.de is local
Apr 25 19:42:15 p15149767 postfix/smtp[9032]: 79A777BC95: to=<root@xyz.de>, relay=none, delay=0, status=bounced (mail for xyz.de loops back to myself)
Apr 25 19:42:15 p15149767 postfix/cleanup[9028]: BE86F7BC24: message-id=<20040425174215.BE86F7BC24@p15149767.pureserver.info>
Apr 25 19:42:15 p15149767 postfix/smtp[9031]: B921A7BC97: to=<root@xyz.de>, relay=none, delay=0, status=bounced (mail for xyz.de loops back to myself)
Apr 25 19:42:15 p15149767 postfix/smtp[9034]: 8ABBF7BC96: to=<root@xyz.de>, relay=none, delay=0, status=bounced (mail for xyz.de loops back to myself)
Apr 25 19:42:15 p15149767 postfix/qmgr[8838]: BE86F7BC24: from=<>, size=6270, nrcpt=1 (queue active)
Apr 25 19:42:15 p15149767 postfix/smtp[9032]: warning: mailer loop: best MX host for xyz.de is local
Apr 25 19:42:15 p15149767 postfix/cleanup[9028]: C32967BC97: message-id=<20040425174215.C32967BC97@p15149767.pureserver.info>
Apr 25 19:42:15 p15149767 postfix/qmgr[8838]: C32967BC97: from=<>, size=3056, nrcpt=1 (queue active)
Apr 25 19:42:15 p15149767 postfix/smtp[9031]: warning: mailer loop: best MX host for xyz.de is local
Apr 25 19:42:15 p15149767 postfix/smtp[9032]: BE86F7BC24: to=<root@xyz.de>, relay=none, delay=0, status=bounced (mail for xyz.de loops back to myself)
Apr 25 19:42:15 p15149767 postfix/smtp[9031]: C32967BC97: to=<root@xyz.de>, relay=none, delay=0, status=bounced (mail for xyz.de loops back to myself)
Apr 25 19:42:18 p15149767 postfix/smtpd[9037]: connect from moutng.kundenserver.de[212.227.126.173]
Apr 25 19:42:18 p15149767 postfix/smtpd[9037]: 16FED7BC24: client=moutng.kundenserver.de[212.227.126.173]
Apr 25 19:42:18 p15149767 postfix/smtpd[9037]: reject: RCPT from moutng.kundenserver.de[212.227.126.173]: 554 <markus@xyz.de>: Recipient address rejected: Relay access denied; from=<xyz@xyz.de> to=<markus@xyz.de>
Apr 25 19:42:20 p15149767 postfix/smtpd[9000]: disconnect from pop.xyz.de[213.165.64.20]
Apr 25 19:42:28 p15149767 postfix/smtpd[9037]: disconnect from moutng.kundenserver.de[212.227.126.173]
Apr 25 19:43:05 p15149767 popper[9045]: Stats: web1p1 0 0 0 0 pD9E5434A.dip.t-dialin.net 217.229.67.74 [pop_updt.c:296]
Apr 25 19:44:03 p15149767 popper[9051]: Stats: web1p1 0 0 0 0 pD9E5434A.dip.t-dialin.net 217.229.67.74 [pop_updt.c:296]
Apr 25 19:45:11 p15149767 popper[9077]: Stats: web1p1 0 0 0 0 pD9E5434A.dip.t-dialin.net 217.229.67.74 [pop_updt.c:296]
Apr 25 19:45:40 p15149767 postfix/master[5977]: terminating on signal 15
Apr 25 19:47:04 p15149767 postfix/postfix-script: starting the Postfix mail system
Apr 25 19:47:04 p15149767 postfix/master[343]: daemon started
Apr 25 20:20:56 p15149767 postfix/postfix-script: starting the Postfix mail system
Apr 25 20:20:56 p15149767 postfix/master[399]: daemon started
Apr 25 20:25:53 p15149767 postfix/master[399]: terminating on signal 15
Apr 25 20:26:59 p15149767 postfix/postfix-script: starting the Postfix mail system
Apr 25 20:26:59 p15149767 postfix/master[405]: daemon started
Apr 25 20:36:22 p15149767 postfix/smtpd[675]: connect from unknown[221.154.186.238]
Apr 25 20:36:23 p15149767 postfix/smtpd[675]: 27DF77BC24: client=unknown[221.154.186.238]
Apr 25 20:36:23 p15149767 postfix/smtpd[675]: reject: RCPT from unknown[221.154.186.238]: 554 <china9988@21cn.com>: Recipient address rejected: Relay access denied; from=<china9988@21cn.com> to=<china9988@21cn.com>
Apr 25 20:36:28 p15149767 postfix/smtpd[675]: disconnect from unknown[221.154.186.238]
Apr 25 20:42:44 p15149767 postfix/smtpd[719]: connect from moutng.kundenserver.de[212.227.126.186]
Apr 25 20:42:44 p15149767 postfix/smtpd[719]: B8FA17BC24: client=moutng.kundenserver.de[212.227.126.186]
Apr 25 20:42:44 p15149767 postfix/smtpd[719]: reject: RCPT from moutng.kundenserver.de[212.227.126.186]: 554 <xyz@xyz.de>: Recipient address rejected: Relay access denied; from=<xyz@xyz.de> to=<xyz@xyz.de>
Apr 25 20:42:54 p15149767 postfix/smtpd[719]: disconnect from moutng.kundenserver.de[212.227.126.186]
Apr 25 20:42:54 p15149767 postfix/smtpd[719]: connect from moutng.kundenserver.de[212.227.126.186]
Apr 25 20:42:54 p15149767 postfix/smtpd[719]: D94707BC24: client=moutng.kundenserver.de[212.227.126.186]
Apr 25 20:42:54 p15149767 postfix/smtpd[719]: reject: RCPT from moutng.kundenserver.de[212.227.126.186]: 554 <xyz@xyz.de>: Recipient address rejected: Relay access denied; from=<> to=<xyz@xyz.de>
Apr 25 20:43:04 p15149767 postfix/smtpd[719]: disconnect from moutng.kundenserver.de[212.227.126.186]
Apr 25 20:57:40 p15149767 postfix/pickup[418]: 27A357BC24: uid=30 from=<wwwrun>
Apr 25 20:57:40 p15149767 postfix/cleanup[878]: 27A357BC24: message-id=<5556d399202a3fcbc65ac89f1268c91b@www.xyz.de>
Apr 25 20:57:40 p15149767 postfix/qmgr[419]: 27A357BC24: from=<wwwrun@xyz.de>, size=1006, nrcpt=1 (queue active)
Apr 25 20:57:40 p15149767 postfix/smtp[880]: 27A357BC24: to=<Mystic-Vegeta@web.de>, relay=mx-ha01.web.de[217.72.192.149], delay=0, status=sent (250 OK id=1BHoou-0004A1-00)
Apr 25 20:58:11 p15149767 postfix/master[405]: terminating on signal 15
Apr 25 20:58:11 p15149767 postfix/postfix-script: starting the Postfix mail system
Apr 25 20:58:11 p15149767 postfix/master[969]: daemon started
Apr 25 20:59:29 p15149767 postfix/smtpd[992]: connect from pop.xyz.de[213.165.64.20]
Apr 25 20:59:29 p15149767 postfix/smtpd[992]: D002C7BC24: client=pop.xyz.de[213.165.64.20]
Apr 25 20:59:29 p15149767 postfix/smtpd[992]: reject: RCPT from pop.xyz.de[213.165.64.20]: 554 <xyz@xyz.de>: Recipient address rejected: Relay access denied; from=<xyz@xyz.de> to=<xyz@xyz.de>
Apr 25 20:59:34 p15149767 postfix/smtpd[992]: disconnect from pop.xyz.de[213.165.64.20]

Hab jetzt nich meine Domain rausgemacht, ich mein is ja eh egal*lol*

An was kann es jetzt liegen..?!

Grüße
Taker
Last edited by taker on 2009-01-25 20:39, edited 2 times in total.

mackshot
Posts: 16
Joined: 2004-03-28 17:22

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by mackshot » 2004-04-25 22:39

hmm....

ich würd vorschlagen du postest jetzt nochmal den inhalt deiner /etc/postfix/main.cf und ich hoffe dir dann endgültig helfen zu können :lol:

taker
Posts: 71
Joined: 2004-01-25 14:08

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by taker » 2004-04-26 17:09

Joah na gut.. Also meine Main.cf

Code: Select all

# 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.
#
queue_directory = /var/spool/postfix

# 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.
#
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
default_privs = autoresp

# 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 = host.domain.tld
#myhostname = virtual.domain.tld
myhostname = pXXXXXXX.pureserver.info

# 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 = domain.tld
mydomain = xyz.de
#Hab aber noch mehrere Domains.. müssen die da auch eingetragen werden?

# 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, www.$mydomain, ftp.$mydomain
mydestination = $myhostname, localhost.$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, hash:/usr/local/etc/postfix/relaydomains

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

# 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
alias_maps = hash:/etc/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
alias_database = hash:/etc/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
mail_spool_directory = /var/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 =
fast_flush_domains = $relay_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)
smtpd_banner = $myhostname ESMTP $mail_name

# 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

# 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

#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
inet_interfaces = all
masquerade_domains = xyz.de
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
relayhost = 
content_filter = 
mailbox_command = 
mailbox_transport = 
smtpd_helo_required = no
smtpd_helo_restrictions = 

Hoffe das dir das hilft.. Bist ja sozusagen meine letzte Hoffnung*gg*

Grüße

Taker


EDIT:

Hier nochmal nen Aktueller Auszug aus meiner "warn"

Code: Select all

Apr 26 21:18:09 p15149767 postfix/smtpd[768]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 26 21:18:10 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 768 exit status 1
Apr 26 21:18:10 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling

Hoffe mir kann jetzt jemand Helfen.. Ich versteht das nicht das er nach der "relaydomains.db" sucht.. wenn ich es auskommentier ists auch nicht viel besser...

Grüße

Taker
Last edited by taker on 2009-01-25 20:42, edited 1 time in total.

michaelzz5
Posts: 14
Joined: 2002-12-07 22:32
Location: Zeitz

Großes Postfix Problem - Mails können nicht empfangen werden

Post by michaelzz5 » 2004-04-26 23:58

Hallo,

da sind einige Fehler drin,

1. mit diesem eintrag funzt SMTP-Auth nicht!
smtpd_recipient_restrictions = permit_mynetworks,check_relay_domains
2. diese Datei muss exestieren weil da die Domains drin stehen und Du es ja bei smtpd_recipient_restrictions angegeben hast.
relay_domains = $mydestination, hash:/usr/local/etc/postfix/relaydomains
3. bei:
mydestination = $myhostname, localhost.$mydomain
füg den eintrag $mydomain hinzu, denn so wie Du es hast fühlt Postfix sich nicht zuständig für Deine Domain garfield0815.de.

mfg. micha

mackshot
Posts: 16
Joined: 2004-03-28 17:22

hmmm

Post by mackshot » 2004-04-27 15:17

probier einfach mal aus diese settings zu setzen -> einige alte musst du da umschreiben bzw evtl sind auch paar neue dabei:

Code: Select all

myhostname = pXXXXXX.pureserver.info # die richtie ID eintragen für XXX
mydomain = garfield0815.de
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = /etc/mailname
mydestination = $myhostname, $mydomain, localhost.$mydomain
relayhost = 
mynetworks = 127.0.0.0/8

recipient_delimiter = +
#smtpd_sasl_local_domain = <- AUSKOMMENTIEREN !!
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
broken_sasl_auth_clients = yes
smtpd_recipient_restrictions = permit_sasl_authenticated,permit_mynetworks,reject_unauth_destination
#smtpd_sender_restrictions = <- auskommtieren!!!
smtpd_sender_login_maps = hash:/etc/postfix/confixx_virtualUsers
#relay_domains =<-- auskommentieren !!!
maps_rbl_domains = relays.ordb.org proxy.relays.osirusoft.com socks.relays.osirusoft.com

taker
Posts: 71
Joined: 2004-01-25 14:08

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by taker » 2004-04-27 18:39

Also das hier ist jetzt aaus der WARN ..

Code: Select all

Apr 27 18:23:20 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:24:20 p15149767 postfix/smtpd[10035]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:24:21 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10035 exit status 1
Apr 27 18:24:21 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:25:21 p15149767 postfix/smtpd[10040]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:25:22 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10040 exit status 1
Apr 27 18:25:22 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:26:22 p15149767 postfix/smtpd[10046]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:26:23 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10046 exit status 1
Apr 27 18:26:23 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:27:23 p15149767 postfix/smtpd[10051]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:27:24 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10051 exit status 1
Apr 27 18:27:24 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:28:24 p15149767 postfix/smtpd[10057]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:28:25 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10057 exit status 1
Apr 27 18:28:25 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:29:25 p15149767 postfix/smtpd[10063]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:29:26 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10063 exit status 1
Apr 27 18:29:26 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:30:26 p15149767 postfix/smtpd[10086]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:30:27 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10086 exit status 1
Apr 27 18:30:27 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:31:27 p15149767 postfix/smtpd[10092]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:31:28 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10092 exit status 1
Apr 27 18:31:28 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:32:28 p15149767 postfix/smtpd[10097]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:32:29 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10097 exit status 1
Apr 27 18:32:29 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:33:29 p15149767 postfix/smtpd[10103]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:33:30 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10103 exit status 1
Apr 27 18:33:30 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling

So hier jetzt nen Auszug aus der "mail"

Code: Select all

Apr 27 18:21:18 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:22:18 p15149767 postfix/smtpd[10025]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:22:19 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10025 exit status 1
Apr 27 18:22:19 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:23:19 p15149767 postfix/smtpd[10030]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:23:20 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10030 exit status 1
Apr 27 18:23:20 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:24:20 p15149767 postfix/smtpd[10035]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:24:21 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10035 exit status 1
Apr 27 18:24:21 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:25:21 p15149767 postfix/smtpd[10040]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:25:22 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10040 exit status 1
Apr 27 18:25:22 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:26:01 p15149767 popper[10043]: Stats: web1p1 0 0 0 0 p50849891.dip.t-dialin.net 80.132.152.145 [pop_updt.c:296]
Apr 27 18:26:22 p15149767 postfix/smtpd[10046]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:26:23 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10046 exit status 1
Apr 27 18:26:23 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:27:23 p15149767 postfix/smtpd[10051]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:27:23 p15149767 popper[10052]: Stats: web1p1 0 0 0 0 p50849891.dip.t-dialin.net 80.132.152.145 [pop_updt.c:296]
Apr 27 18:27:24 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10051 exit status 1
Apr 27 18:27:24 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:28:24 p15149767 postfix/smtpd[10057]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:28:25 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10057 exit status 1
Apr 27 18:28:25 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:28:43 p15149767 popper[10058]: Stats: web1p1 0 0 0 0 p50849891.dip.t-dialin.net 80.132.152.145 [pop_updt.c:296]
Apr 27 18:29:25 p15149767 postfix/smtpd[10063]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:29:26 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10063 exit status 1
Apr 27 18:29:26 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:30:26 p15149767 postfix/smtpd[10086]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:30:27 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10086 exit status 1
Apr 27 18:30:27 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:30:43 p15149767 popper[10087]: Stats: web1p1 0 0 0 0 p50849891.dip.t-dialin.net 80.132.152.145 [pop_updt.c:296]
Apr 27 18:31:27 p15149767 postfix/smtpd[10092]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:31:28 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10092 exit status 1
Apr 27 18:31:28 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:32:28 p15149767 postfix/smtpd[10097]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:32:29 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10097 exit status 1
Apr 27 18:32:29 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:32:44 p15149767 popper[10098]: Stats: web1p1 0 0 0 0 p50849891.dip.t-dialin.net 80.132.152.145 [pop_updt.c:296]
Apr 27 18:33:29 p15149767 postfix/smtpd[10103]: fatal: open database /usr/local/etc/postfix/relaydomains.db: No such file or directory
Apr 27 18:33:30 p15149767 postfix/master[493]: warning: process /usr/lib/postfix/smtpd pid 10103 exit status 1
Apr 27 18:33:30 p15149767 postfix/master[493]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Apr 27 18:34:04 p15149767 postfix/master[493]: terminating on signal 15
Apr 27 18:34:10 p15149767 postfix/postfix-script: starting the Postfix mail system
Apr 27 18:34:10 p15149767 postfix/master[10188]: daemon started
Apr 27 18:34:18 p15149767 postfix/smtpd[10196]: connect from p50849891.dip.t-dialin.net[80.132.152.145]
Apr 27 18:34:19 p15149767 postfix/smtpd[10196]: 0D64C7BC96: client=p50849891.dip.t-dialin.net[80.132.152.145]
Apr 27 18:34:19 p15149767 postfix/smtpd[10196]: reject: RCPT from p50849891.dip.t-dialin.net[80.132.152.145]: 554 <xyz@xyz.de>: Relay access denied; from=<xyz@xyz.de> to=<xyz@xyz.de>
Apr 27 18:34:19 p15149767 popper[10195]: Stats: web1p1 0 0 0 0 p50849891.dip.t-dialin.net 80.132.152.145 [pop_updt.c:296]
Apr 27 18:34:27 p15149767 postfix/smtpd[10196]: disconnect from p50849891.dip.t-dialin.net[80.132.152.145]
Apr 27 18:34:46 p15149767 postfix/smtpd[10196]: connect from p50849891.dip.t-dialin.net[80.132.152.145]
Apr 27 18:34:46 p15149767 postfix/smtpd[10196]: 700A67BC96: client=p50849891.dip.t-dialin.net[80.132.152.145]
Apr 27 18:34:46 p15149767 postfix/smtpd[10196]: reject: RCPT from p50849891.dip.t-dialin.net[80.132.152.145]: 550 <xyz@xyz.de>: User unknown; from=<xyz@xyz.de> to=<xyz@xyz.de>
Apr 27 18:34:52 p15149767 popper[10199]: Stats: web1p1 0 0 0 0 p50849891.dip.t-dialin.net 80.132.152.145 [pop_updt.c:296]
Apr 27 18:34:54 p15149767 postfix/smtpd[10196]: disconnect from p50849891.dip.t-dialin.net[80.132.152.145]
Apr 27 18:35:25 p15149767 postfix/smtpd[10196]: connect from p50849891.dip.t-dialin.net[80.132.152.145]
Apr 27 18:35:25 p15149767 postfix/smtpd[10196]: EAAA37BC96: client=p50849891.dip.t-dialin.net[80.132.152.145]
Apr 27 18:35:26 p15149767 postfix/smtpd[10196]: reject: RCPT from p50849891.dip.t-dialin.net[80.132.152.145]: 554 <xyz@xyz.de>: Relay access denied; from=<xyz@xyz.de> to=<xyz@xyz.de>
Apr 27 18:35:33 p15149767 postfix/smtpd[10196]: disconnect from p50849891.dip.t-dialin.net[80.132.152.145]
Apr 27 18:36:01 p15149767 popper[10208]: Stats: web1p1 0 0 0 0 p50849891.dip.t-dialin.net 80.132.152.145 [pop_updt.c:296]
Apr 27 18:37:08 p15149767 popper[10213]: Stats: web1p1 0 0 0 0 p50849891.dip.t-dialin.net 80.132.152.145 [pop_updt.c:296]
Apr 27 18:38:08 p15149767 popper[10218]: Stats: web1p1 0 0 0 0 p50849891.dip.t-dialin.net 80.132.152.145 [pop_updt.c:296]
Apr 27 18:39:08 p15149767 popper[10223]: Stats: web1p1 0 0 0 0 p50849891.dip.t-dialin.net 80.132.152.145 [pop_updt.c:296]
Apr 27 18:40:14 p15149767 popper[10229]: Stats: web1p1 0 0 0 0 p50849891.dip.t-dialin.net 80.132.152.145 [pop_updt.c:296]
Apr 27 18:41:09 p15149767 popper[10239]: Stats: web1p1 0 0 0 0 p50849891.dip.t-dialin.net 80.132.152.145 [pop_updt.c:296]
Apr 27 18:42:10 p15149767 popper[10246]: Stats: web1p1 0 0 0 0 p50849891.dip.t-dialin.net 80.132.152.145 [pop_updt.c:296]
Apr 27 18:43:09 p15149767 popper[10251]: Stats: web1p1 0 0 0 0 p50849891.dip.t-dialin.net 80.132.152.145 [pop_updt.c:296]
Apr 27 18:44:10 p15149767 popper[10256]: Stats: web1p1 0 0 0 0 p50849891.dip.t-dialin.net 80.132.152.145 [pop_updt.c:296]
Apr 27 18:45:10 p15149767 popper[10279]: Stats: web1p1 0 0 0 0 p50849891.dip.t-dialin.net 80.132.152.145 [pop_updt.c:296]
Apr 27 18:46:10 p15149767 popper[10284]: Stats: web1p1 0 0 0 0 p50849891.dip.t-dialin.net 80.132.152.145 [pop_updt.c:296]
Apr 27 18:47:10 p15149767 popper[10289]: Stats: web1p1 0 0 0 0 p50849891.dip.t-dialin.net 80.132.152.145 [pop_updt.c:296]
Apr 27 18:48:07 p15149767 postfix/master[10188]: terminating on signal 15
Apr 27 18:49:20 p15149767 postfix/postfix-script: starting the Postfix mail system
Apr 27 18:49:20 p15149767 postfix/master[486]: daemon started
Apr 27 18:50:41 p15149767 postfix/master[486]: terminating on signal 15
Apr 27 18:50:42 p15149767 postfix/postfix-script: starting the Postfix mail system
Apr 27 18:50:42 p15149767 postfix/master[692]: daemon started


Hi, danke für die Hilfe, hab jetzt die Daten so eingesetzt wie du sie angegeben hast.. Ich bekomme jetzt auch eine Mail vom Systemadministrator zurpck das die Mail nicht zugestellt WURDE..

Ich check nochmal die Einstellungen, vielleicht ist da ja noch was Faul.. DAnke erstmal für die Hilfe, hoffe ihr könnt mir jetzt noch "zuende" helfen.

Beste Grüße

Taker


EDIT: DAS HIER ist jetzt meine Aktuelle Config...

Code: Select all

# 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.
#
queue_directory = /var/spool/postfix

# 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.
#
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
default_privs = autoresp

# 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 = host.domain.tld
#myhostname = virtual.domain.tld
myhostname = p15149767.pureserver.info

# 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 = domain.tld
mydomain = xyz.de


# 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 = /etc/mailname


# 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, www.$mydomain, ftp.$mydomain
mydestination = $myhostname, $mydomain, localhost.$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
mynetworks = 127.0.0.0/8

# 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, hash:/usr/local/etc/postfix/relaydomains
maps_rbl_domains = relays.ordb.org proxy.relays.osirusoft.com socks.relays.osirusoft.com

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

# 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
alias_maps = hash:/etc/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
alias_database = hash:/etc/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
mail_spool_directory = /var/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 =
fast_flush_domains = $relay_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)
smtpd_banner = $myhostname ESMTP $mail_name

# 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

# 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

#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
inet_interfaces = all
masquerade_domains = xyz.de
#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_sasl_authenticated,permit_mynetworks,reject_unauth_destination 

#SMTPD Auth
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
broken_sasl_auth_clients = yes
#smtpd_sasl_local_domain =
smtpd_sender_login_maps = hash:/etc/postfix/confixx_virtualUsers

#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
relayhost = 
content_filter = 
mailbox_command = 
mailbox_transport = 
smtpd_helo_required = no
smtpd_helo_restrictions = 
Last edited by taker on 2009-01-25 20:44, edited 1 time in total.

mackshot
Posts: 16
Joined: 2004-03-28 17:22

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by mackshot » 2004-04-27 19:10

hmm

lösch am besten mal die zeile mit


#relay_domains = $mydestination, hash:/usr/local/etc/postfix/relaydomains

und schau dann nochmal was dann so klappt und welche fehler dann noch kommen!

taker
Posts: 71
Joined: 2004-01-25 14:08

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by taker » 2004-04-27 19:31

Code: Select all

Apr 27 19:26:57 p15149767 postfix/postfix-script: starting the Postfix mail system
Apr 27 19:26:58 p15149767 postfix/master[493]: daemon started
Apr 27 19:27:40 p15149767 postfix/smtpd[601]: connect from pop.gmx.net[213.165.64.20]
Apr 27 19:27:40 p15149767 postfix/smtpd[601]: C85337BC96: client=pop.gmx.net[213.165.64.20]
Apr 27 19:27:40 p15149767 postfix/smtpd[601]: reject: RCPT from pop.gmx.net[213.165.64.20]: 550 <xyz@xyz.de>: User unknown; from=<xyz@xyz.de> to=<xyz@xyz.de>
Apr 27 19:27:45 p15149767 postfix/smtpd[601]: disconnect from pop.gmx.net[213.165.64.20]

Sieht doch eigentlich alles ganz normal aus oder? Aber den NAMEN, bzw. die Mail Addy "xyz@xyz.de" gibt es , für den hab ich nen PoP Fach erstellt und im Confixx stehts auch drin. Unter Yast (User) steht das Postfach auch drin, also stimmt irgendwas nicht.. Ich kann auch nicht zum POP3 Server connecten. Weder per Outlook noch per "Confixx Webmail"

Wo könnte der Fehler noch liegen?

Grüße

Taker

PS: In der Warn Steht jetzt GAR NIX mehr drin, das find ich schon mal toll!
Last edited by taker on 2009-01-25 20:44, edited 1 time in total.

mackshot
Posts: 16
Joined: 2004-03-28 17:22

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by mackshot » 2004-04-27 19:34

Taker wrote: Sieht doch eigentlich alles ganz normal aus oder? Aber den NAMEN, bzw. die Mail Addy "garfield@garfield0815.de" gibt es , für den hab ich nen PoP Fach erstellt und im Confixx stehts auch drin. Unter Yast (User) steht das Postfach auch drin, also stimmt irgendwas nicht.. Ich kann auch nicht zum POP3 Server connecten. Weder per Outlook noch per "Confixx Webmail"

Wo könnte der Fehler noch liegen?

Grüße

Taker

PS: In der Warn Steht jetzt GAR NIX mehr drin, das find ich schon mal toll!
find ich mindestens genauso toll :D

führ einfachmal folgendes aus:

/root/confixx/admin/subs/postfix_install.pl

(du hast doch confixx installiert, seh ich doch richtig ne?)

einmal postfix neustarten, darin bist du ja geübt und dann sollte es klappen :-D

taker
Posts: 71
Joined: 2004-01-25 14:08

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by taker » 2004-04-27 20:19

ok, ich führ das mal aus und starte postix neu, alles klar^^

taker

Also das steht jetzt in der mail

Code: Select all

Apr 27 19:26:57 p15149767 postfix/postfix-script: starting the Postfix mail system
Apr 27 19:26:58 p15149767 postfix/master[493]: daemon started
Apr 27 19:27:40 p15149767 postfix/smtpd[601]: connect from pop.gmx.net[213.165.64.20]
Apr 27 19:27:40 p15149767 postfix/smtpd[601]: C85337BC96: client=pop.gmx.net[213.165.64.20]
Apr 27 19:27:40 p15149767 postfix/smtpd[601]: reject: RCPT from pop.gmx.net[213.165.64.20]: 550 <garfield@xyz.de>: User unknown; from=<xyz@xyz.de> to=<garfield@xyz.de>
Apr 27 19:27:45 p15149767 postfix/smtpd[601]: disconnect from pop.gmx.net[213.165.64.20]
Apr 27 19:32:38 p15149767 postfix/smtpd[689]: connect from p50849891.dip.t-dialin.net[80.132.152.145]
Apr 27 19:32:38 p15149767 postfix/smtpd[689]: AB0747BC96: client=p50849891.dip.t-dialin.net[80.132.152.145]
Apr 27 19:32:38 p15149767 postfix/smtpd[689]: reject: RCPT from p50849891.dip.t-dialin.net[80.132.152.145]: 550 <markus@xyz.de>: User unknown; from=<garfield@xyz.de> to=<markus@xyz.de>
Apr 27 19:32:46 p15149767 postfix/smtpd[689]: disconnect from p50849891.dip.t-dialin.net[80.132.152.145]
Apr 27 19:33:09 p15149767 postfix/smtpd[689]: connect from pop.gmx.net[213.165.64.20]
Apr 27 19:33:09 p15149767 postfix/smtpd[689]: 019E67BC96: client=pop.gmx.net[213.165.64.20]
Apr 27 19:33:09 p15149767 postfix/smtpd[689]: reject: RCPT from pop.gmx.net[213.165.64.20]: 550 <markus@xyz.de>: User unknown; from=<xyz@xyz.de> to=<markus@xyz.de>
Apr 27 19:33:14 p15149767 postfix/smtpd[689]: disconnect from pop.gmx.net[213.165.64.20]
Apr 27 19:55:02 p15149767 postfix/postfix-script: refreshing the Postfix mail system
Apr 27 19:55:02 p15149767 postfix/master[493]: reload configuration
Apr 27 20:19:54 p15149767 postfix/master[493]: terminating on signal 15
Apr 27 20:19:54 p15149767 postfix/postfix-script: starting the Postfix mail system
Apr 27 20:19:54 p15149767 postfix/master[1124]: daemon started

Hab deine Anweisung ausgeführt, bin ins Verzeichnis gewechselt und hab dann mit ./postfix_install.pl gestartet.. Daraufhin hat er die Config "editiert".. So dann hab ich mich "rcpostfix restart" postfix neu gestartet.. Da stand auch *DONE*
Aber ich bekomm ich noch keinen Connect zum Server..

Grüße

Taker

PS: Ist der POP3 vielleicht noch sonst irgendwie anders eingebaut? Das da ein Fehler liegen könnte?!
Last edited by taker on 2009-01-25 20:45, edited 1 time in total.

mackshot
Posts: 16
Joined: 2004-03-28 17:22

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by mackshot » 2004-04-28 00:08

aber der auszug des logfiles zeigt doch jetzt die alten fehler bevor du das gemacht hast (oder bin ich jetzt mit den uhrzeiten durcheinander gekommen) check das nochmal...

und dann check auchmal deinen mailclienten! wie genau logst du dich da ein? was hast du aktiviert für optionen?

adjustman
Posts: 1132
Joined: 2003-03-26 23:29
Location: SA

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by adjustman » 2004-04-28 00:20

Code: Select all

Apr 27 19:27:40 p15149767 postfix/smtpd[601]: reject: RCPT from pop.gmx.net[213.165.64.20]: 550 <garfield@garfield0815.de>: User unknown; from=<markus.fortak@gmx.de> to=<garfield@garfield0815.de>
steht doch alles da. garfield@garfield0815.de gibt es nicht.

wgot
RSAC
Posts: 1707
Joined: 2003-07-06 02:03

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by wgot » 2004-04-28 00:26

Hallo,

ist die Confixx-Lizenz gültig?
Kannst Du lokal senden (test@garfield0815.de an garfield@garfield0815.de)?
Schau mal in die Postfächer unter /var/spool/mail.

Gruß, Wolfgang

taker
Posts: 71
Joined: 2004-01-25 14:08

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by taker » 2004-04-28 17:19

Hi,

also

Die Mail Adresse GIBT ES DEFINITIV!!!
Ich kann Lokal auch nicht Senden.. Confixx zb. gibt mir die Fehlermeldung "Bekomme keinen Connect zum Server. Vielleicht ist der POP3-Server gerade nicht zu erreichen. " aus und sonst gehts auch NICHT!

Die Lizens ist definitiv ebenfalls GÃ?LTIG!

In dem /var/spool/Mail sind alle "Postfächer" angelegt aber alle mit 0 KB gekenntzeichnet. Web1P1 zb. ist LEER! Genauso wie alle anderen auch!

Ich hab mich per Outlook eingeloggt. "pop.garfield0815.de" und "smtp.garfield0815.de"
dann die Daten: Benutzername mein "POP Postfach Name" und dann eben das Passwort! Aber ich bekomme keine POP Verbindung, so sagts ja zb. auch Confixx!

SSL Verschlüsselung ist auch nicht Aktiv in Outlook für das Postfach..

Hoffe wir kriegen das noch raus..

Grüße

Taker
Last edited by taker on 2009-01-25 20:47, edited 1 time in total.

adjustman
Posts: 1132
Joined: 2003-03-26 23:29
Location: SA

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by adjustman » 2004-04-28 17:25

Taker wrote:...Confixx zb. gibt mir die Fehlermeldung "Bekomme keinen Connect zum Server. Vielleicht ist der POP3-Server gerade nicht zu erreichen. " aus....
Welche Version? Wenn 2.* dann Suche benutzen. Ist ein Bug. Das hat aber überhaupt nix mit dem anderen Fehler zu tun.

taker
Posts: 71
Joined: 2004-01-25 14:08

Re: Großes Postfix Problem - Mails können nicht empfangen werden

Post by taker » 2004-04-28 17:28

Ja ne 2.X.X.X Version. An ein Update hab ich mnich noch nicht rangetraut.. Hab da etwas schiss vor.. Das mir dann alles futsch geht.. Ich warte bis es nen Update aufm "1und1" Server gibt.. Dann passt das vielleicht.. Aber egal, das ist ja nicht das Thema. OK danke ich werd mal die Suche anschmeißen 8)

Taker