Postfix + POP3 + SMTP + Relay Access Denied

Postfix, QMail, Sendmail, Dovecot, Cyrus, Courier, Anti-Spam
User avatar
TDS
Posts: 71
Joined: 2004-03-25 07:53
Location: Hannover

Postfix + POP3 + SMTP + Relay Access Denied

Post by TDS » 2004-12-06 20:07

Hab heute mal wieder nen Postfix installiert. Als POP3 hab ich imap. Mails empfangen geht. Mails versenden zum eigenene Server geht auch. Mails zu yahoo, gmx und Co funktionieren nicht.

Dec 6 22:15:24 vi-colo-978 postfix/smtpd[6932]: 06988A18006: reject: RCPT from unknown[80.184.152.150]: 554 <smartprog4u@yahoo.de>: Relay access denied; from=<service@heartbooker.de> to=<smartprog4u@yahoo.de> proto=SMTP helo=<mathias>

main.cf:

command_directory = /usr/sbin
program_directory = /usr/libexec/postfix
daemon_directory = /usr/libexec/postfix
mail_spool_directory = /var/spool/mail
disable_dns_lookups = no
myhostname = heartbooker.de
mydomain = heartbooker.de
mynetworks_style = host
alias_maps = hash:/etc/postfix/aliases
# folgendes zur spam-verhinderung
# nur authorisierte benutzer duerfen mails versenden
smtp_sasl_auth_enable = yes
smtp_sasl_security_options = noanonymous
#smt_sasl_local_domain =
smtp_sasl_password_maps = hash:/etc/postfix/smtpauth
smtp_banner = $myhostname SMTP $mail_name ($mail_version)
smtpd_recipient_restrictions = permit_sasl_authenticated, reject_unauth_destination
smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination
broken_sasl_auth_clients = yes
mailbox_size_limit = 0
message_size_limit = 10240000
mydestination = $myhostname, localhost.$mydomain, $mydomain, smtp.$mydomain

Was mache ich falsch?

charlie
Posts: 78
Joined: 2002-09-30 23:36

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by charlie » 2004-12-08 16:25

HI,

na mal vor dem versenden authentifizieren versucht?

charlie

User avatar
TDS
Posts: 71
Joined: 2004-03-25 07:53
Location: Hannover

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by TDS » 2004-12-08 17:15

Hab doch schon geschrieben, das ich Mails an interne Mailboxen schicken kann, also alles mit @heartbooker.de. Hab aber schon nen Tip mit DNS bekommen, sprich beim ISP mx.xxx.de und so einrichten.

Roger Wilco
Administrator
Administrator
Posts: 6001
Joined: 2004-05-23 12:53

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by Roger Wilco » 2004-12-08 18:41

TDS wrote:Hab doch schon geschrieben, das ich Mails an interne Mailboxen schicken kann, also alles mit @heartbooker.de.
Natürlich kannst du Mails an heartbooker.de schreiben, die Domain steht ja auch in mydestination.
Lies dir mal den Kommentar aus deiner main.cf durch:

Code: Select all

# folgendes zur spam-verhinderung 
# nur authorisierte benutzer duerfen mails versenden 
smtp_sasl_auth_enable = yes 
smtp_sasl_security_options = noanonymous
;)
TDS wrote:Hab aber schon nen Tip mit DNS bekommen, sprich beim ISP mx.xxx.de und so einrichten.
Das würde mich doch sehr überraschen, wenn es wirklich daran liegen sollte.

cws-trummer
Posts: 4
Joined: 2004-12-08 19:42

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by cws-trummer » 2004-12-08 19:46

ich hab genau das selbe problem

wenn ich in outlook die einstellungen test (jedoch ohne authentifizierung beim smtp server) funktioniert alles da eine mail an meine mail (also intern) gesendet wird

sobald ich jedoch an eine andere mail senden will kommt die gleiche fehlermeldung

an mx records liegts glaub ich nicht..hab die schon eingerichtet..

komisch ist nur dass die standarfkonfiguration ist die am anfang auf meinem vserver war...hab meinen vserver bei vanager.de und da gibts ein webinterface mit dem man ganz einfach sagen kann "linux mit confixx 3 installiern" und das wird dann alles erledigt und alles wird automatisch installiert..kann mir nicht vorstellen dass diese standardkonfiguration falsch ist....

Roger Wilco
Administrator
Administrator
Posts: 6001
Joined: 2004-05-23 12:53

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by Roger Wilco » 2004-12-08 20:08

*seufz*
Ok, nochmal von vorne:
Mails an die Domains, die in mydestination stehen funktioniert immer, wie sollte man euch auch sonst eine Mail schicken können.
Mails über den MTA an eine andere / fremde Domain erfordert eine Authentifizierung am SMTP-Server und das ist auch gut so[tm].
Woher sich der MTA die Benutzerdaten holt, kommt auf die Konfiguration an, im obigen Beispiel sollten es aber die Daten aus /etc/shadow sein.
Das hat (primär) nichts mit den MX-Records der Domain zu tun...

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

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by wgot » 2004-12-08 21:31

Hallo,

und natürlich SMTPauth im Client aktivieren bevor man den Fehler in der Serverconfig sucht.

Gruß, Wolfgang

cws-trummer
Posts: 4
Joined: 2004-12-08 19:42

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by cws-trummer » 2004-12-10 19:36

ja ist schon klar mit smtp authentifizierung

nur wenn ich ein standard system eingerichtet bekomme (das auf 100 anderen server läuft) geh ich mal davon aus dass man für das versenden der mails die gleichen login daten wie beim empfangen braucht

empfangen funzt aber beim versenden kommt immer der fehler dass der benutzernname/passwort nicht stimmt..hab ausgewählt dass die gleichen daten wie bei pop genommen werden..

und wenn schon confixx drauf is (für solche die sich also nix auskennen mit server konfigurieren) dann wird confixx das wohl so einrichten dass das die gleichen login daten wie beim abrufen der mails sind, steht ja auch so in der beschreibung drinnen

trotzdem funktionierts nicht..

antondollmaier
Posts: 485
Joined: 2004-03-30 10:06

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by antondollmaier » 2004-12-10 19:38

/var/log/messages überprüfen ... außerdem /var/log/mail ...


tippe auf ausgeschalteten / falsch eingestellten saslauthd ...

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

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by wgot » 2004-12-10 20:18

Hallo,

telnet domain 25

ehlo test

was wird für AUTH zurückgegeben?

Outlook Express akzeptiert nur Login, manche anderen Clients nur plain.

Gruß, Wolfgang

cws-trummer
Posts: 4
Joined: 2004-12-08 19:42

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by cws-trummer » 2004-12-10 22:13

mit telnet hab ichs schon probiert

kommt der esmtp banner u wenn ich ehlo test eingib kommt die meldung dass es die funktion nicht gibt
aber hab dass mal in einem config file gefunde wo steht ehlo/helo nicht benötigt..

auth kommt gar keine

hab in messages und mail nachgesehen steht irgendwie nix drinnen..

bei sasl steht nur eine zeile in smtpd.conf und zwar auth ist pam

und in pam.d/smtp steht
auth required pam_unix.so ....

ich kanns einfach nicht glauben dass ein standard paket nicht funktioniert..

als pop daemon wird qpopper eingesetzt
wo sehe ich welche datei er zum authentifizieren benutzt dann weiß ich ja auch welche postfix verwenden soll oder?

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

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by wgot » 2004-12-10 22:27

Hallo,

die Standardkonfiguration ist vermutlich nicht falsch, aber unvollständig.

smtpd_helo_required = yes hat mit Deinem Problem bzw der fehlenden ehlo-Ausgabe nix zu tun.

Welches Linux, welcher MTA?

Gruß, Wolfgang

cws-trummer
Posts: 4
Joined: 2004-12-08 19:42

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by cws-trummer » 2004-12-10 22:48

cwsTrummer:~# cat /proc/version
Linux version 2.4.20-021stab022.3.777-enterprise (st@current.eng.sw.ru) (gcc version 2.96 20000731 (Red Hat Linux 7.3 2.96-110)) #1 SMP Wed Aug 4 19:02:12 MSD 2004

mta ist postfix..


ich verzweifle gleich...und i glaubs dass es nur mir so geht..vanager.de hat ja mehrer kunden u dass die alle keine mails versenden können glaub ich einfach nicht

User avatar
TDS
Posts: 71
Joined: 2004-03-25 07:53
Location: Hannover

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by TDS » 2004-12-16 18:41

Sorry, bin gerad erst wieder zurück :-)

User avatar
TDS
Posts: 71
Joined: 2004-03-25 07:53
Location: Hannover

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by TDS » 2004-12-16 18:47

Also erstmal alle Fragen beantworten:

Hier ist der Log von Postfix (der MTA).
Dec 16 19:23:04 vi-colo-978 postfix/smtpd[6471]: connection established
Dec 16 19:23:04 vi-colo-978 postfix/smtpd[6471]: master_notify: status 0
Dec 16 19:23:04 vi-colo-978 postfix/smtpd[6471]: name_mask: resource
Dec 16 19:23:04 vi-colo-978 postfix/smtpd[6471]: name_mask: software
Dec 16 19:23:04 vi-colo-978 postfix/smtpd[6471]: name_mask: noanonymous
Dec 16 19:23:04 vi-colo-978 postfix/smtpd[6471]: connect from p3EE2FF03.dip.t-dialin.net[62.226.255.3]
Dec 16 19:23:04 vi-colo-978 postfix/smtpd[6471]: > p3EE2FF03.dip.t-dialin.net[62.226.255.3]: 220 Heartbooker ESMTP Heartbooker MailServer (2.0.18)
Dec 16 19:23:04 vi-colo-978 postfix/smtpd[6471]: watchdog_pat: 0x90c5bc0
Dec 16 19:23:04 vi-colo-978 postfix/smtpd[6471]: < p3EE2FF03.dip.t-dialin.net[62.226.255.3]: XXXX 127.0.0.1
Dec 16 19:23:04 vi-colo-978 postfix/smtpd[6471]: > p3EE2FF03.dip.t-dialin.net[62.226.255.3]: 402 Error: command not implemented
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: watchdog_pat: 0x90c5bc0
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: < p3EE2FF03.dip.t-dialin.net[62.226.255.3]: HELO 127.0.0.1
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: > p3EE2FF03.dip.t-dialin.net[62.226.255.3]: 250 mail.heartbooker.de
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: watchdog_pat: 0x90c5bc0
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: < p3EE2FF03.dip.t-dialin.net[62.226.255.3]: MAIL FROM:<service@heartbooker.de>
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: extract_addr: input: <service@heartbooker.de>
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: extract_addr: result: service@heartbooker.de
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: fsspace: .: block size 4096, blocks free 92261351
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: smtpd_check_size: blocks 4096 avail 92261351 min_free 0 size 0
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: connect to subsystem public/cleanup
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: public/cleanup socket: wanted attribute: queue_id
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: input attribute name: queue_id
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: input attribute value: 8E49365C006
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: public/cleanup socket: wanted attribute: (list terminator)
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: input attribute name: (end)
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: send attr flags = 2
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: 8E49365C006: client=p3EE2FF03.dip.t-dialin.net[62.226.255.3]
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: > p3EE2FF03.dip.t-dialin.net[62.226.255.3]: 250 Ok
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: watchdog_pat: 0x90c5bc0
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: < p3EE2FF03.dip.t-dialin.net[62.226.255.3]: RCPT TO:<webmaster@tds-net.de>
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: extract_addr: input: <webmaster@tds-net.de>
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: extract_addr: result: webmaster@tds-net.de
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: generic_checks: START
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: generic_checks: name=permit_mynetworks
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: permit_mynetworks: p3EE2FF03.dip.t-dialin.net 62.226.255.3
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: match_hostname: p3EE2FF03.dip.t-dialin.net ~? 127.0.0.0/8
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: match_hostaddr: 62.226.255.3 ~? 127.0.0.0/8
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: match_list_match: p3EE2FF03.dip.t-dialin.net: no match
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: match_list_match: 62.226.255.3: no match
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: generic_checks: name=permit_mynetworks status=0
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: generic_checks: name=permit_sasl_authenticated
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: generic_checks: name=permit_sasl_authenticated status=0
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: generic_checks: name=reject_unauth_destination
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: reject_unauth_destination: webmaster@tds-net.de
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: permit_auth_destination: webmaster@tds-net.de
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: ctable_locate: leave existing entry key webmaster@tds-net.de
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: 8E49365C006: reject: RCPT from p3EE2FF03.dip.t-dialin.net[62.226.255.3]: 454 <webmaster@tds-net.de>: Relay access denied; from=<service@heartbooker.de> to=<webmaster@tds-net.de> proto=SMTP helo=<127.0.0.1>
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: generic_checks: name=reject_unauth_destination status=2
Dec 16 19:23:05 vi-colo-978 postfix/smtpd[6471]: > p3EE2FF03.dip.t-dialin.net[62.226.255.3]: 454 <webmaster@tds-net.de>: Relay access denied
Dec 16 19:23:06 vi-colo-978 postfix/smtpd[6471]: watchdog_pat: 0x90c5bc0
Dec 16 19:23:06 vi-colo-978 postfix/smtpd[6471]: < p3EE2FF03.dip.t-dialin.net[62.226.255.3]: RSET
Dec 16 19:23:06 vi-colo-978 postfix/smtpd[6471]: > p3EE2FF03.dip.t-dialin.net[62.226.255.3]: 250 Ok
Dec 16 19:23:06 vi-colo-978 postfix/smtpd[6471]: watchdog_pat: 0x90c5bc0
Dec 16 19:23:06 vi-colo-978 postfix/smtpd[6471]: < p3EE2FF03.dip.t-dialin.net[62.226.255.3]: RSET
Dec 16 19:23:06 vi-colo-978 postfix/smtpd[6471]: > p3EE2FF03.dip.t-dialin.net[62.226.255.3]: 250 Ok
Dec 16 19:23:06 vi-colo-978 postfix/smtpd[6471]: watchdog_pat: 0x90c5bc0
Dec 16 19:23:07 vi-colo-978 postfix/smtpd[6471]: < p3EE2FF03.dip.t-dialin.net[62.226.255.3]: QUIT
Dec 16 19:23:07 vi-colo-978 postfix/smtpd[6471]: > p3EE2FF03.dip.t-dialin.net[62.226.255.3]: 221 Bye
Dec 16 19:23:07 vi-colo-978 postfix/smtpd[6471]: disconnect from p3EE2FF03.dip.t-dialin.net[62.226.255.3]
Dec 16 19:23:07 vi-colo-978 postfix/smtpd[6471]: master_notify: status 1
Dec 16 19:23:07 vi-colo-978 postfix/smtpd[6471]: connection closed
Dec 16 19:23:07 vi-colo-978 postfix/smtpd[6471]: watchdog_stop: 0x90c5bc0
Dec 16 19:23:07 vi-colo-978 postfix/smtpd[6471]: watchdog_start: 0x90c5bc0


Nun kann ich aber nicht mal mehr intern Mails versenden außer ich bin auf localhost via ssh.

/etc/postfix/aliases
# Default aliases file for postfix
#
# this file should be in /etc or in /etc/postfix but if you want it in
# /etc/postfix you'll have to adjust your /etc/postfix/main.cf file accordingly
#
# Aliases in this file will NOT be expanded in the header from
# mail, but WILL be visible over networks or from /bin/mail.
#
# Following alias is required by the mail protocol, RFC 822 (and by RFC2142)
# Set it to the address of a HUMAN who deals with this system's mail problems.
#
# For various security reasons, postfix WILL NOT deliver mail as root, so
# ensure that the root alias is aliased to a HUMAN user, as otherwise
# mail may get delivered to the $default_privs user (nobody).
postmaster: root

# Many mailers use this address to represent the empty SMTP return
# path
MAILER-DAEMON: postmaster


# Common aliases for system accounts.
bin: root
daemon: root
games: root
ingres: root
nobody: root
system: root
toor: root
foo: root
falken: root

# Well-known aliases.
admin: root
manager: root
dumper: root
operator: root

# traps to catch security attacks
decode: root
moof: root
moog: root

# The following aliases are required by RFC 2142
marketing: staff
sales: staff
support: staff

# Standard aliases also defined by RFC 2142
abuse: postmaster
# reports of network infrastructure difficulties
noc: root
# address to report secuirty problems
security: root
# DNS administrator (DNS soa records should use this)
hostmaster: root
# Usenet news service administrator
news: usenet
usenet: root
# http/web service administrator
www: webmaster
webmaster: root
# UUCP service administrator
uucp: root
# FTP administrator (especially anonymouse FTP)
ftp: root

# Commonly used group aliases:
#
staff: postmaster
office: postmaster
all: postmaster
tech: postmaster
ops: postmaster

# Person who should get root's mail. This alias
# must exist.
# CHA4~NGE THIS LINE to an account of a HUMAN
root: web0p0
info: service
welcome: service
heartbooker: service
service: web0p1

# Note to the user: You must create the alias above!
# The root alias *must* exist under postfix because
# postfix runs as a non-privileged user and cannot
# touch a spool file which is UID/GID root
# The mapping to the postfix user is to ensure that root's mail
# doesn't get lost on a system installed out of the box.

main.cf
# Global Postfix configuration file. This file lists only a subset
# of all 250+ 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 = yes

# 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/libexec/postfix

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

# 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 = mail.heartbooker.de

# 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 = mail.heartbooker.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.
#
# 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

# 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, localhost

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

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

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

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

# TRUST AND RELAY CONTROL

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

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

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

# 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 50 SMTP server process
# limit, this limits the mail inflow to 50 messages a second more
# than the number of messages delivered per second.
#
# Specify 0 to disable the feature. Valid delays are 0..10.
#
#in_flow_delay = 1s

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

#local_destination_concurrency_limit = 2
#default_destination_concurrency_limit = 10

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

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

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

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

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

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

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

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

#defer_transports = smtp
# 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/postfix-2.0.11/samples

# readme_directory: The location of the Postfix README files.
#
readme_directory = /usr/share/doc/postfix-2.0.11/README_FILES
alias_database = hash:/etc/postfix/aliases

disable_dns_lookups = no
smtpd_sasl_local_domain =
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
broken_sasl_auth_clients = yes
local_recipient_maps = $relocated_maps $alias_maps unix:passwd.byname
smtpd_client_restrictions =
smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject
#, reject_unauth_destination
smtpd_helo_required = no
relay_domain = mail.tds-net.de
#maps_rbl_domains = relays.ordb.org proxy.relays.osirusoft.com socks.rleays.osirusoft.com
#content_filter = vscan:
soft_bounce = yes

master.cf
#
# Postfix master process configuration file. Each logical line
# describes how a Postfix daemon program should be run.
#
# A logical line starts with non-whitespace, non-comment text.
# Empty lines and whitespace-only lines are ignored, as are comment
# lines whose first non-whitespace character is a `#'.
# A line that starts with whitespace continues a logical line.
#
# The fields that make up each line are described below. A "-" field
# value requests that a default value be used for that field.
#
# Service: any name that is valid for the specified transport type
# (the next field). With INET transports, a service is specified as
# host:port. The host part (and colon) may be omitted. Either host
# or port may be given in symbolic form or in numeric form. Examples
# for the SMTP server: localhost:smtp receives mail via the loopback
# interface only; 10025 receives mail on port 10025.
#
# Transport type: "inet" for Internet sockets, "unix" for UNIX-domain
# sockets, "fifo" for named pipes.
#
# Private: whether or not access is restricted to the mail system.
# Default is private service. Internet (inet) sockets can't be private.
#
# Unprivileged: whether the service runs with root privileges or as
# the owner of the Postfix system (the owner name is controlled by the
# mail_owner configuration variable in the main.cf file). Only the
# pipe, virtual and local delivery daemons require privileges.
#
# Chroot: whether or not the service runs chrooted to the mail queue
# directory (pathname is controlled by the queue_directory configuration
# variable in the main.cf file). Presently, all Postfix daemons can run
# chrooted, except for the pipe, virtual and local delivery daemons.
# The proxymap server can run chrooted, but doing so defeats most of
# the purpose of having that service in the first place.
# The files in the examples/chroot-setup subdirectory describe how
# to set up a Postfix chroot environment for your type of machine.
#
# Wakeup time: automatically wake up the named service after the
# specified number of seconds. A ? at the end of the wakeup time
# field requests that wake up events be sent only to services that
# are actually being used. Specify 0 for no wakeup. Presently, only
# the pickup, queue manager and flush daemons need a wakeup timer.
#
# Max procs: the maximum number of processes that may execute this
# service simultaneously. Default is to use a globally configurable
# limit (the default_process_limit configuration parameter in main.cf).
# Specify 0 for no process count limit.
#
# Command + args: the command to be executed. The command name is
# relative to the Postfix program directory (pathname is controlled by
# the daemon_directory configuration variable). Adding one or more
# -v options turns on verbose logging for that service; adding a -D
# option enables symbolic debugging (see the debugger_command variable
# in the main.cf configuration file). See individual command man pages
# for specific command-line options, if any.
#
# In order to use the "uucp" message tranport below, set up entries
# in the transport table.
#
# In order to use the "cyrus" message transport below, configure it
# in main.cf as the mailbox_transport.
#
# SPECIFY ONLY PROGRAMS THAT ARE WRITTEN TO RUN AS POSTFIX DAEMONS.
# ALL DAEMONS SPECIFIED HERE MUST SPEAK A POSTFIX-INTERNAL PROTOCOL.
#
# DO NOT SHARE THE POSTFIX QUEUE BETWEEN MULTIPLE POSTFIX INSTANCES.
#
# ==========================================================================
# service type private unpriv chroot wakeup maxproc command + args
# (yes) (yes) (yes) (never) (100)
# ==========================================================================
smtp inet n - n - - smtpd -v
#smtps inet n - n - - smtpd
# -o smtpd_tls_wrappermode=yes -o smtpd_sasl_auth_enable=yes
#submission inet n - n - - smtpd
# -o smtpd_enforce_tls=yes -o smtpd_sasl_auth_enable=yes
#628 inet n - n - - qmqpd
#587 inet n - n - - smtpd
pickup fifo n - - 60 1 pickup
cleanup unix n - - - 0 cleanup
qmgr fifo n - - 300 1 qmgr
#qmgr fifo n - n 300 1 nqmgr
#tlsmgr fifo - - n 300 1 tlsmgr
rewrite unix - - - - - trivial-rewrite
bounce unix - - - - 0 bounce
defer unix - - - - 0 bounce
flush unix n - - 1000? 0 flush
smtp unix - - - - - smtp -v
showq unix n - - - - showq
error unix - - - - - error
local unix - n n - - local
virtual unix - n n - - virtual
lmtp unix - - n - - lmtp
#
# Interfaces to non-Postfix software. Be sure to examine the manual
# pages of the non-Postfix software to find out what options it wants.
#
# maildrop. See the Postfix MAILDROP_README file for details.
#
maildrop unix - n n - - pipe
flags=DRhu user=vmail argv=/usr/local/bin/maildrop -d ${recipient}
#
# The Cyrus deliver program has changed incompatibly, multiple times.
#
old-cyrus unix - n n - - pipe
flags=R user=cyrus argv=/cyrus/bin/deliver -e -m ${extension} ${user}
# Cyrus 2.1.5 (Amos Gouaux)
cyrus unix - n n - - pipe
user=cyrus argv=/cyrus/bin/deliver -e -r ${sender} -m ${extension} ${user}
uucp unix - n n - - pipe
flags=Fqhu user=uucp argv=uux -r -n -z -a$sender - $nexthop!rmail ($recipient)
ifmail unix - n n - - pipe
flags=F user=ftn argv=/usr/lib/ifmail/ifmail -r $nexthop ($recipient)
bsmtp unix - n n - - pipe
flags=Fq. user=foo argv=/usr/local/sbin/bsmtp -f $sender $nexthop $recipient
#vscan unix - n n - 10 pipe
# user=vscan argv=/usr/sbin/amavis ${sender} ${recipient}
#localhost:10025 inet n - n - - smtpd
# -o content_filter=

So, nun helft mir mal bitte :-)
Last edited by TDS on 2004-12-16 19:28, edited 2 times in total.

User avatar
TDS
Posts: 71
Joined: 2004-03-25 07:53
Location: Hannover

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by TDS » 2004-12-16 18:47

Ach so, und wenn ich von meinem richtigen Mail-Account etwas versenden möchte kommt folgendes:

The original message was received at Thu, 16 Dec 2004 18:44:06 +0100
from p3EE2FF03.dip.t-dialin.net [62.226.255.3]

----- The following addresses had permanent fatal errors -----
<service@heartbooker.de>
(reason: 501 5.7.1 This system is not configured to relay mail from <webmaster@tds-net.de> to <service@heartbooker.de> for 217.20.113.102)

----- Transcript of session follows -----
... while talking to mx1.activeisp.com.:
>>> RCPT To:<service@heartbooker.de>
<<< 501 5.7.1 This system is not configured to relay mail from <webmaster@tds-net.de> to <service@heartbooker.de> for 217.20.113.102
554 5.0.0 Service unavailable

Es muss also irgend etwas mit relay_domains oder so sein...

User avatar
TDS
Posts: 71
Joined: 2004-03-25 07:53
Location: Hannover

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by TDS » 2004-12-16 19:04

Also um gleich noch ein paar Fragen auszuräumen :idea:

mydestination = xyz -> das die mails da angenommen werden ist klar

sasl und sasl2 -> konfiguriert mit saslauthd, mech_list = PLAIN LOGIN
saslauthd ist gestart mit paramter "pam", nicht "shadow"

smtpd_helo_required = no hilft auch nicht weiter da es ja nicht zwingend erforderlich ist

Alle 3rd-Level-Domains sind eingerichtet (mx, mail, smtp, pop3).

So, nun bin ich mal auf die Antworten von Profis gespannt 8O

kostya
Posts: 89
Joined: 2003-01-22 17:23

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by kostya » 2004-12-16 20:47

In dem Logauszug sieht man ganz gut, dass der verbundene Client nicht aus mynetwork stam (kann ja auch keiner nach deiner Einstellung) und auch nicht authorisiert ist.

Man sieht gar nicht, dass der Client versucht hat, sich zu authorisieren. Ist den SMTP-AUTH beim Client aktiv?

Wenn du schon als default reject am Ende von smtpd_recipient_restrictions hast, dann solltest du auch permit_auth_destination in diesen restrictions haben, weil sonst alles rejected wird, was nicht aus mynetworks kommt und nicht sasl_authenticated ist.

Zu mynetworks bei dir gehört komischerweise nur 127.0.0.0/8. Ich bin mir nicht sicher, aber ich glaube, dass dies nicht korrekt ist. Man sollte entweder mynetworks_style oder mynetworks benutzen. Falls beide gesetzt sind, gewinnt mynetworks, wo auch die richtigen Werte sein sollten.


Ausserdem würde ich "mydomain = heartbooker.de" setzen und relay_domain entfernen, da der Parameter falsch geschrieben ist. Für relay_domains ist aber der Defaultwert gut genug.

User avatar
TDS
Posts: 71
Joined: 2004-03-25 07:53
Location: Hannover

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by TDS » 2004-12-16 20:59

Also hab mynetworks auskommentiert und nur mynetworks_style=host gesetzt. Ich denke mal das SASL_AUTH gestartet ist (hab mit saslauthd gestartet). Habe auch permit_auth_destination vor reject_unauth_destination gesetzt. Intern versenden geht, aber nicht extern. relay_domains hab ich entfernt. Aber habe trotzdem nocht folgendes Problem:

Dec 16 20:52:42 vi-colo-978 postfix/smtpd[6604]: resolve_clnt_query: `webmaster@tds-net.de' -> t=`smtp' h=`tds-net.de' r=`webmaster@tds-net.de'
Dec 16 20:52:42 vi-colo-978 postfix/smtpd[6604]: ctable_locate: install entry key webmaster@tds-net.de
Dec 16 20:52:42 vi-colo-978 postfix/smtpd[6604]: generic_checks: name=permit_auth_destination status=0
Dec 16 20:52:42 vi-colo-978 postfix/smtpd[6604]: generic_checks: name=reject_unauth_destination
Dec 16 20:52:42 vi-colo-978 postfix/smtpd[6604]: reject_unauth_destination: webmaster@tds-net.de
Dec 16 20:52:42 vi-colo-978 postfix/smtpd[6604]: permit_auth_destination: webmaster@tds-net.de
Dec 16 20:52:42 vi-colo-978 postfix/smtpd[6604]: ctable_locate: leave existing entry key webmaster@tds-net.de
Dec 16 20:52:42 vi-colo-978 postfix/smtpd[6604]: 1FF4965C001: reject: RCPT from p3EE2F39A.dip.t-dialin.net[62.226.243.154]: 454 <webmaster@tds-net.de>: Relay access denied; from=<service@heartbooker.de> to=<webmaster@tds-net.de> proto=SMTP helo=<127.0.0.1>
Dec 16 20:52:42 vi-colo-978 postfix/smtpd[6604]: generic_checks: name=reject_unauth_destination status=2
Dec 16 20:52:42 vi-colo-978 postfix/smtpd[6604]: > p3EE2F39A.dip.t-dialin.net[62.226.243.154]: 454 <webmaster@tds-net.de>: Relay access denied
Dec 16 20:52:43 vi-colo-978 postfix/smtpd[6604]: watchdog_pat: 0x9c8c460
Dec 16 20:52:43 vi-colo-978 postfix/smtpd[6604]: < p3EE2F39A.dip.t-dialin.net[62.226.243.154]: RSET
Dec 16 20:52:43 vi-colo-978 postfix/smtpd[6604]: > p3EE2F39A.dip.t-dialin.net[62.226.243.154]: 250 Ok
Dec 16 20:52:43 vi-colo-978 postfix/smtpd[6604]: watchdog_pat: 0x9c8c460
Dec 16 20:52:43 vi-colo-978 postfix/smtpd[6604]: < p3EE2F39A.dip.t-dialin.net[62.226.243.154]: RSET
Dec 16 20:52:43 vi-colo-978 postfix/smtpd[6604]: > p3EE2F39A.dip.t-dialin.net[62.226.243.154]: 250 Ok
Dec 16 20:52:43 vi-colo-978 postfix/smtpd[6604]: watchdog_pat: 0x9c8c460
Dec 16 20:52:43 vi-colo-978 postfix/smtpd[6604]: < p3EE2F39A.dip.t-dialin.net[62.226.243.154]: QUIT
Dec 16 20:52:43 vi-colo-978 postfix/smtpd[6604]: > p3EE2F39A.dip.t-dialin.net[62.226.243.154]: 221 Bye
Dec 16 20:52:43 vi-colo-978 postfix/smtpd[6604]: disconnect from p3EE2F39A.dip.t-dialin.net[62.226.243.154]
Dec 16 20:52:43 vi-colo-978 postfix/smtpd[6604]: master_notify: status 1
Dec 16 20:52:43 vi-colo-978 postfix/smtpd[6604]: connection closed

Also nimmt er nicht Mails zu externen Anbietern. Wieso?

kostya
Posts: 89
Joined: 2003-01-22 17:23

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by kostya » 2004-12-16 21:07

Weil der externe sich nicht mit sasl anmeldet (dafür muss das bei dem externen aktiviert sein und er muss auch die Zugangsdaten haben) und permit_auth_destination nach permit_sasl_authenticated steht.

User avatar
TDS
Posts: 71
Joined: 2004-03-25 07:53
Location: Hannover

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by TDS » 2004-12-16 21:20

Hmm, also wenn ich mich mit meinen Mailprogramm anmelde, dann ist bei SMTP mit Authentifizierung nen Häkchen. Zugangsdaten hab ich ja, keine Sorge. Oder wie soll ich das verstehen. Ach ja, die Meldung mit keine Authentifizierungsmethode gefunden meines Mailprogramms ist komisch genug...

User avatar
TDS
Posts: 71
Joined: 2004-03-25 07:53
Location: Hannover

Mail-Ausgabe

Post by TDS » 2005-01-13 12:07

So, jetzt bin ich ja mal gespannt. Gab ja lange keine Antwort hier. Wie gesagt POP3 funktioniert. SMTP mit Server-eigenen Adressen funktioniert auch. Nur mit externen Adressen funktioniert es nicht.

http://www.tds-net.de/experts/mail1.txt

Anonymous

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by Anonymous » 2005-02-10 12:29

Ich hab das Problem jetzt auch mit zwei Benutzern auf meinem Server. Mit SMTPAuth ist alles in Ordnung, von ca. 30 Benutzern haben dieses Problem auch bisher nur 2, das kann also nicht an einer fehlerhaften Konfiguration liegen, die Clients sind auch korrekt eingerichtet, sonst würde Outlook ja bereits beim Versenden auf die Nase fallen.

Was ich bisher festgestellt habe ist, dass das Problem nur mit Outlook XP auftaucht und das sowohl auf Win2000 als auch auf WinXP, kann das schonmal jemand bestätigen oder habt Ihr da andere Erfahrungen ?
Bei mir selbst (Win2000, Outlook 2000) gab's noch nie Probleme, ich kann den Fehler nicht reproduzieren, auch bei Benutzern mit Outlook Express unter XP scheint's keine Probleme zu geben.

Ein Bekannter hat die Mailverbindungen auf SSL gesetzt, da klappt alles ohne Probleme. Er ist der Meinung, bei der Authentifizierung würden sich viele Outlook-Versionen einfach nicht korrekt verhalten und mit SSL zwingt man Outlook quasi dazu, sich korrekt zu authentifizeiren.

Hat schon jemand eine andere Lösung für dieses so oft beschriebene Problem gefunden ?

User avatar
TDS
Posts: 71
Joined: 2004-03-25 07:53
Location: Hannover

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by TDS » 2005-02-10 22:24

Bin ja nun fast nen Postifx-Profi geworden. Mit SASL gibt es grundlegend immer Probleme. Wie hast du es konfiguriert. Ã?ber PAM oder so? Mit Berkeley DB? Hast du broken_sasl_auth_clients = yes gesetzt?

Anonymous

Re: Postfix + POP3 + SMTP + Relay Access Denied

Post by Anonymous » 2005-02-15 00:01

Postfix-Profi bin ich leider nicht, auch kein Newbie, aber mit Postfix musste ich mich bisher noch nie eingehender beschäftigen.

Wo sehe ich, ob ich PAM nutze ? Installiert hab ich's, eine Berkley DB allerdings nicht und broken_sasl_auth_clients taucht in meiner main.cf nicht auf, wird dann wohl auf default stehen.

Ich hab das Problem inzwischen aber gelöst (dank der Hilfe meines Linux-Gurus, der bei sowas immer herhalten muss):
Fest steht, dass das Problem nur mit Outlook XP aufgetaucht ist und zwar nur, wenn kein ServicePack installiert war. Dem einen Benutzer hab ich einfach mal den Tipp gegeben, das mal zu installieren und schon war das Problem behoben.
Nach besagter Unterstützung hab ich dann TLS eingerichtet und beiden Benutzern erklärt, wie man die Konten für SSL einstellt und dann ging's bei beiden, also sowohl mit als auch ohne SP.

Ich danke jedenfalls ein weiteres Mal M$ für viel vergeudete Zeit. Danke Bill :roll: