Postfix-Probleme Allgemein (Relay-, Domain-Hilfe)

Postfix, QMail, Sendmail, Dovecot, Cyrus, Courier, Anti-Spam
thomy
Posts: 17
Joined: 2006-06-30 13:01

Postfix-Probleme Allgemein (Relay-, Domain-Hilfe)

Post by thomy » 2006-06-30 14:15

Ein nettes "Hallo" von mir!

Ich habe, wie viele andere hier, ein großes Problem!
Bei mir soll einfach der Mailserver nicht funktionieren. Egal was ich mache, es geht nicht. Ob ich nun Mails über Internet senden möchte oder empfangen möchte. Es klappt beides nicht. Und bei meiner letzten Installation (die 18. mitlerweile) auch lokale E-Mail-zustellungen nicht.

Ich bin am verzweifeln! :cry:

Also mein Plan ist natürlich kein offenes Relay zu sein.
Am besten wäre, dass kein User Mails verschicken könnte.
Nur mein Apache ist mir wichtig, und um den gehts mir letztendlich auch.
Später ist mir dann vielleicht recht, dass noch ein paar User E-Mails versende können.
Und natürlich möchte ich E-Mails empfangen können.


Die derzeitige Situation ist folgende:
-Server steht hinter Router (Port 25 ist offen, auch wenns unsicher ist)
-Serverhostname ist Jacques und Domain ist einfach mal jacques.de
(Ich weiß nicht, ob das soweit in Ordnung ist)
-mein Internetprovider ist 1und1 und wir haben natürlich die FLatrate und keine Standleitung!
-dadurch habe ich mir ein dyndns-Dienst genommen und bin darüber zu erriechen. (Werde ich noch nciht auflisten)
-Suse 10 habe ich auf dem Server


Ich habe aber vor, mir bald eine richtige Domain zu kaufen *.com und die mit dem DynDNS.org Dienst auszustatten. Ich weiß nicht, in wie weit das Vorteile bringt beim E-Mail senden!



Und jetzt das Problem:

Postfix sendet einfach keine Mails!
Ich muss ja über ein Relay E-Mails verschicken, so weit ich weiß!
Ansonsten nimmt zum Beispiel GMX keine Mails von mir an.
Ich habe jetzt schon vieles ausprobiert und keine Lösung dazu gefunden.


Ich poste mal kurz die letzten Fehler:

Code: Select all

Jun 30 12:37:58 jacques postfix/smtpd[5396]: fatal: dict_open: unsupported dictionary type: dbm:  Is the postfix-dbm package installed?
Jun 30 12:37:59 jacques postfix/master[4379]: warning: process /usr/lib/postfix/smtpd pid 5396 exit status 1
Jun 30 12:37:59 jacques postfix/master[4379]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling

Das sind meine jetzigen Probleme!
Bei jeder Installation habe ich neue!
Ich habe jetzt eine RPM-installation!


Ich möchte dazu sagen, dass ich kein kleines Dööfchen bin, auch wenn es hier so aussieht.
In Google und anderen Foren, auch hier, habe ich auch schon nachgeguckt. Tja, nix gefunden! :?


Bitte helft mir!!!!


Gruß
Thomy

sledge0303
RSAC
Posts: 767
Joined: 2005-09-16 00:06
Location: Berlin-Reinickendorf

Re: Postfix-Probleme Allgemein (Relay-, Domain-Hilfe)

Post by sledge0303 » 2006-06-30 14:41

Postfix sendet einfach keine Mails!
Ich muss ja über ein Relay E-Mails verschicken, so weit ich weiß!
Ansonsten nimmt zum Beispiel GMX keine Mails von mir an.
Ich habe jetzt schon vieles ausprobiert und keine Lösung dazu gefunden.
Benutzeraccounts sollten schon eingerichtet sein um e-Mails verschicken zu können.
GMX filtert evtl. deine Mails. Hast du schon mal im Spamordner nachgeschaut oder an eine andere Mailadresse versucht zu versenden?

Jun 30 12:37:58 jacques postfix/smtpd[5396]: fatal: dict_open: unsupported dictionary type: dbm: Is the postfix-dbm package installed?
Jun 30 12:37:59 jacques postfix/master[4379]: warning: process /usr/lib/postfix/smtpd pid 5396 exit status 1
Jun 30 12:37:59 jacques postfix/master[4379]: warning: /usr/lib/postfix/smtpd: bad command startup -- throttling
Da ich kein Postfix benutze kann ich dir da nicht 100%ig sagen was machen kannst, aber es sieht so aus ob da was fehlt. Throttling=gedrosselter Datenfluss
Wie sehen deine Configs aus?
Ich möchte dazu sagen, dass ich kein kleines Dööfchen bin, auch wenn es hier so aussieht
Sagt auch keiner, müsstest aber deine Anfrage mit dem was bereits gemacht hast komplettieren, so kann man besser und gezielter helfen!

rootsvr
Posts: 538
Joined: 2005-09-02 11:12

Re: Postfix-Probleme Allgemein (Relay-, Domain-Hilfe)

Post by rootsvr » 2006-06-30 14:51

Also da fehlt dir irgendein Postfix paket ich würde das mal runterschmeissen und per yast das postfix paket installieren, weil zumindest ein startup sollte ohne Probleme klappen (deine Fehlermeldung)

Mit der Basis oben braucht man erstmal nicht anfangen. ich rate dir einfach mal zum Suse Package.

den relay dann eintragen ist nicht schwer, das sind normalerweise nur 2 Zeilen, damit man senden kann fürs Empfangen brauchst Du natürlich nen MX auf deinen Server und für DSL halte ich das nicht optimal, da können deine Mails auch mal woanders landen (Zeitraum zwischen IP Änderung und MX Update).

thomy
Posts: 17
Joined: 2006-06-30 13:01

Re: Postfix-Probleme Allgemein (Relay-, Domain-Hilfe)

Post by thomy » 2006-06-30 14:52

schonmal danke für deine Antwort! :)
Benutzeraccounts sollten schon eingerichtet sein um e-Mails verschicken zu können.
GMX filtert evtl. deine Mails. Hast du schon mal im Spamordner nachgeschaut oder an eine andere Mailadresse versucht zu versenden?
Benutzeraccount??
Also ich denke die Systembenutzer reichen, oder habe ich das jetzt falsch interpretiert?? In der Aliastabelle habe ich auch schon was eingegeben!


ich werde mal meine main.cf posten:

Code: Select all

#
# -----------------------------------------------------------------------
# NOTE: Many parameters have already been added to the end of this file
#       by SuSEconfig.postfix. So take care that you don't uncomment
#       and set a parameter without checking whether it has been added
#       to the end of this file.
# -----------------------------------------------------------------------
#
# Global Postfix configuration file. This file lists only a subset
# of all 300+ parameters. See the postconf(5) manual page for a
# complete list.
#
# The general format of each line is: parameter = value. 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.
#
command_directory = /usr/sbin

# The daemon_directory parameter specifies the location of all Postfix
# daemon programs (i.e. programs listed in the master.cf file). This
# directory must be owned by root.
#
daemon_directory = /usr/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 = *meine Domain*
#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 = *nochmal meine Domain, und zwar wie oben!!*

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

# RECEIVING MAIL

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

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

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

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

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

# 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 postconf(5).
#
# 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 = 205.149.103.0/20, 127.0.0.0/8
#mynetworks = $config_directory/mynetworks
#mynetworks = hash:/etc/postfix/network_table

# The relay_domains parameter restricts what destinations this system will
# relay mail to.  See the smtpd_recipient_restrictions description in
# postconf(5) for detailed information.
#
# By default, Postfix relays mail
# - from "trusted" clients (IP address matches $mynetworks) to any destination,
# - from "untrusted" clients to destinations that match $relay_domains or
#   subdomains thereof, except addresses with sender-specified routing.
# The default relay_domains value is $mydestination.
# 
# In addition to the above, the Postfix SMTP server by default accepts mail
# that Postfix is final destination for:
# - destinations that match $inet_interfaces or $proxy_interfaces,
# - destinations that match $mydestination
# - destinations that match $virtual_alias_domains,
# - destinations that match $virtual_mailbox_domains.
# These destinations do not need to be listed in $relay_domains.
# 
# Specify a list of hosts or domains, /file/name patterns or type:name
# lookup tables, separated by commas and/or whitespace.  Continue
# long lines by starting the next line with whitespace. A file name
# is replaced by its contents; a type:name table is matched when a
# (parent) domain appears as lookup key.
#
# NOTE: Postfix will not automatically forward mail for domains that
# list this system as their primary or backup MX host. See the
# permit_mx_backup restriction description in postconf(5).
#
#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 = [smtp.1und1.de]
#relayhost = uucphost
#relayhost = [an.ip.add.ress]

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

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

# ADDRESS REWRITING
#
# The ADDRESS_REWRITING_README document gives information about
# address masquerading or other forms of address rewriting including
# username->Firstname.Lastname mapping.

# ADDRESS REDIRECTION (VIRTUAL DOMAIN)
#
# The VIRTUAL_README document gives information about the many forms
# of domain hosting that Postfix supports.

# "USER HAS MOVED" BOUNCE MESSAGES
#
# See the discussion in the ADDRESS_REWRITING_README document.

# TRANSPORT MAP
#
# See the discussion in the ADDRESS_REWRITING_README document.

# 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.
#
# NOTE: if you use this feature for accounts not in the UNIX password
# file, then you must update the "local_recipient_maps" setting in
# the main.cf file, otherwise the SMTP server will reject mail for    
# non-UNIX accounts with "User unknown in local recipient table".
#
#mailbox_transport = lmtp:unix:/file/name
#mailbox_transport = cyrus

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

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

# The header_checks parameter specifies an optional table with patterns
# that each logical message header is matched against, including
# headers that span multiple physical lines.
#
# By default, these patterns also apply to MIME headers and to the
# headers of attached messages. With older Postfix versions, MIME and
# attached message headers were treated as body text.
#
# For details, see "man header_checks".
#
#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".
# See the ETRN_README document for a detailed description.
# 
# The fast_flush_domains parameter controls what destinations are
# eligible for this service. By default, they are all domains that
# this server is willing to relay mail to.
# 
#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)

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

#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 20

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

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

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

# If you can't use X, use this to capture the call stack when a
# daemon crashes. The result is in a file in the configuration
# directory, and is named after the process name and the process ID.
#
# debugger_command =
#	PATH=/bin:/usr/bin:/usr/local/bin; export PATH; (echo cont;
#	echo where) | gdb $daemon_directory/$process_name $process_id 2>&1
#	>$config_directory/$process_name.$process_id.log & sleep 5
#
# Another possibility is to run gdb under a detached screen session.
# To attach to the screen sesssion, su root and run "screen -r
# <id_string>" where <id_string> uniquely matches one of the detached
# sessions (from "screen -list").
#
# debugger_command =
#	PATH=/bin:/usr/bin:/sbin:/usr/sbin; export PATH; screen
#	-dmS $process_name gdb $daemon_directory/$process_name
#	$process_id & sleep 1

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

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

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

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

# html_directory: The location of the Postfix HTML documentation.
#
html_directory = /usr/share/doc/packages/postfix/html

# 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.
# This parameter is obsolete as of Postfix 2.1.
#
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
inet_protocols = all
biff = no


# SASL

smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
smtpd_sasl_local_domain = 
broken_sasl_auth_clients = yes


# ANTI-SPAM
default_rbl_reply = $rbl_code RBLTRAP: You cant send us a mail today!!!

smtpd_helo_required = yes
smtpd_delay_reject = yes


mime_header_checks=pcre:/etc/postfix/body_check




Ich habe das Suse Package installiert!!! Halt als RPM!
Ich habe das ganze auch mit Yast installiert und auch mal konfiguriert kommt aber das gleiche bei raus!

rootsvr
Posts: 538
Joined: 2005-09-02 11:12

Re: Postfix-Probleme Allgemein (Relay-, Domain-Hilfe)

Post by rootsvr » 2006-06-30 14:57

Cool:
mynetworks = 205.149.103.0/20
alle Rechner Deines Providers (nehme ich mal an) dürfen über dich versenden (schön das es noch nicht geht..) mynetworks sollte IMMER nur 127.0.0.1 und ggf die eigene IP Sein, und nur wenn man ein Netzwerk betreibt und da einen anderen Mailserver stehen hat was anderes eintragen.. sollte bei Dir nicht der Fall sein.

die Alias Zeile mit dbm verursacht den Fehler.. kein DBM nutzen, wenn man keins installiert hat.

Aber das hast Du schon gemacht, gell?
# 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

thomy
Posts: 17
Joined: 2006-06-30 13:01

Re: Postfix-Probleme Allgemein (Relay-, Domain-Hilfe)

Post by thomy » 2006-06-30 15:00

ah cool! Danke! :wink: ich sehs *.dbm!

Gut der erste Fehler!!!
Also das ist unsere interne IP
ich habe keine 192.168.*.*!

Ich hatte das so verstanden, dass 205.149.103:0 für unsere interne Ip steht und die 20 danach für die anderen PCs, die auch noch senden dürfen!
Also 205.149.103.1, 205.149.103.2...205.149.103.20

Oder wie soll ich das verstehen????

Gruß
Thomy :wink:

[edit]

geht denn alias_maps=db:/etc/aliases???




[edit2]

Ich habe jetzt alias_maps kommentiert!
MyNetworks auch! Und e sklappt soweit auch!
Immerhin hat er die Mails lokal zugestellt!
Kann ich die Aliase die ich eingetragen habe trotzdem benutzen???

Wenn ich jetzt eine E-Mail an mich selbst bei GMX senden möchte kommt allerdings wieder das:

Code: Select all

connect to mx0.gmx.de[213.165.64.100]: server refused to talk to me: 554-{mx086} Your address is listed as dynamic on SORBS (dul.dnsbl.sorbs.net) 554 We are not accepting connections from such hosts. ( http://www.gmx.net/serverrules )
Und in der log Datei steht auch relay=none!
Aber ich habe doch einen eingegeben! :?

Oder wo soll ich nochmal den Relay eingeben???
Das ist ja bei mir 1und1 und da muss ich dann doch noch ein eine Authentication eingeben, oder?
Last edited by thomy on 2006-06-30 15:15, edited 1 time in total.

rootsvr
Posts: 538
Joined: 2005-09-02 11:12

Re: Postfix-Probleme Allgemein (Relay-, Domain-Hilfe)

Post by rootsvr » 2006-06-30 15:13

Rhetorische Frage: Hast Du irgendeine Ahnung von sowas?

Deine interne Adresse sollte sowas wie 192.x.x.x sein oder ist dieser Rechner dein einziger? Das heißt Du surfst und arbeitest auf deinem Linux(Mail)server und hast sooo wenig Ahnung?
die externe vom Provider zugewiesene ist 205.149.103.X. /20 Bedeutet eine 20 Bit Subnetzmaske, das heißt Du hast 205.149.96.0 - 205.149.111.255 freigegeben.

ich weiß nicht was normalerweise benutzt wird, ich benutze meist mysql oder hash datenbanken und kein db,.

thomy
Posts: 17
Joined: 2006-06-30 13:01

Re: Postfix-Probleme Allgemein (Relay-, Domain-Hilfe)

Post by thomy » 2006-06-30 15:18

ne ich habe AHnung, zumindest vom Netzwerk! :wink:
Nur halt nicht davon!

Meine externe IP-Adresse ist nicht 205.149.103.*

Das ist meine interne! Anstatt 192.168.0.* habe ich halt diese,
und das hat auch seine Gründe!
Aber das dürfte doch kein Problem darstellen!
Und deswegen habe ich mein internes Netz, welches hinter dem Router steht bei mynetwork eingegeben und zwar 205.149.103.0/20 damit noch alle Rechner in unserem Netz E-Mails senden können!


[edit]
Ich habe Alias getestet!
Also auch wenn Alias auskommentiert ist, kann ich das benutzen!

Ich habe allerdings ein anderes Problem gefunden, nämlich kann ich jetzt von keinem E-Mail-Klient auf Server konnekten!

Und halt immer noch das Problem mit dem Relay!
In der Log steht dann wie immer wenn eine E-Mail gesendet wird und dann die Antwort auf "Hallo" von GMX und relay=none!

rootsvr
Posts: 538
Joined: 2005-09-02 11:12

Re: Postfix-Probleme Allgemein (Relay-, Domain-Hilfe)

Post by rootsvr » 2006-06-30 16:38

Warum auch immer du als Heimnetz das der Uni in Hawaii einstellst. Warum keine RFC Addressen?

Und Wenn man Netzwerke kann sollte man eigentlich was von CIDR gehört haben (/20)

Deine Anderen Ausführungen verstehe ich nicht..

Meine Konfig für einen 'send-omly' host, keine lokalen User die Mails empfangen und Relay über gmx:

Code: Select all

smtpd_banner = $myhostname ESMTP $mail_name (Debian/GNU)
biff = no

# appending .domain is the MUA's job.
append_dot_mydomain = no

# Uncomment the next line to generate "delayed mail" warnings
#delay_warning_time = 4h

myhostname = Cerberus
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = /etc/mailname
mydestination = Cerberus.localdomain.de, Cerberus, localhost.localdomain, localhost
mynetworks = 127.0.0.0/8
mailbox_command = procmail -a "$EXTENSION"
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all

#SMTP Auth
#SMTP mit SASL-Authentification verwenden
smtp_sasl_auth_enable = yes

#Die Paßwörter stehen in der Datei /etc/postfix/smtp_auth
smtp_sasl_password_maps = hash:/etc/postfix/smtp_auth

#Zusatz-Optionen: Keine anonyme-Anmeldung verwenden
smtp_sasl_security_options = noanonymous

#Den Relayhost (der Server der unsere Emails annehmen soll)
relayhost = mail.gmx.de
in /etc/postfix/smtp_auth steht:
mail.gmx.de USERNAME:PASSWORT

danach einmal postmap auf /etc/postfix/smtp_auth und er erzeugt die hash db. danach kann mein Server mails über GMX verschicken, aber nur wenn der Absender mit dem Usernamen übereinstimmt. (GMX Policy) wenn Du generell andere Absender willst brauchst Du nen Relayhost, der z.B. bei Authentifizierten Mails alles annimmt.

thomy
Posts: 17
Joined: 2006-06-30 13:01

Re: Postfix-Probleme Allgemein (Relay-, Domain-Hilfe)

Post by thomy » 2006-06-30 16:52

hey, danke, das hat mich schon weiter gebracht!!! :o

Also sagen wir ich habe den relayhost "1und1"!
Dann kann ich auch bei 1und1 nur immer mit dem Absender abschicken, den ich auch in der smtp_auth-datei eingetragen habe???

Könntest du denn näher erläutern, wie ich das hinkriege, dass ich auch andere Absender benutzen kann??

Vielen Dank

Teste direkt mal!

rootsvr
Posts: 538
Joined: 2005-09-02 11:12

Re: Postfix-Probleme Allgemein (Relay-, Domain-Hilfe)

Post by rootsvr » 2006-06-30 17:40

Wie es bei eins und eins ist weiß ich nicht, habe da keinen Login. Wenn Dein Provider das nicht zuläßt mußt Du dir irgendwo anders einen Relay mieten wo das zugelassen ist. ich glaub die TKomn hat sowas mal für 2.99 € angeboten.

Wenn 1und1 das so wie gmx handelt kannst Du das nicht umgehen, da mails dann mit dem Hinweis das Absender nicht mit Login übereinstimmt.

thomy
Posts: 17
Joined: 2006-06-30 13:01

Re: Postfix-Probleme Allgemein (Relay-, Domain-Hilfe)

Post by thomy » 2006-06-30 20:59

bisher läuft der Server Fehlerfrei, aber die Mails nach außen klappen noch nciht so richtig!!!

Egal ob bei 1und1 oder bei GMX, bei beiden steht noch sowas:

Code: Select all

Need to authenticate via SMTP-AUTH-Login (in Reply to MAIL-FROM command)
ich habe die smtp_auth erstellt und auch gemapped, aber das klappt irgendwie nicht!!!
Muss ich den Benutzername direkt nach dem mail.*.de in der smtp_auth eingeben?
Zeigt halt auch keine Errörs und die Mails gehen auch soweit raus, also sie bleiben nicht in der queue. Nur ankommen tun sie nicht und GMX lässt dann sone Nachricht ab!




[edit=gelöst]

Habe es fertig!!!
Mein Problem war, dass ich smtpd_sasl_passwd... geschrieben habe.
Dadurch konnte ich mich nciht authentifizieren!
Wenn jemand noch nen Tipp hat, bitte reinschreiben!!!

Und ein großen Danke an meinen lieben schnellen Antworter! :wink:


Gruß
Vom glücklichen Thomy

Es funktioniert...