Hallo!
Ich habe seit einigen Tagen ein Problem mit meinem MTA (Postfix).
Da ich das System vor ein paar Tagen neu aufgesetzt habe, kam ich dann zu dem Punkt mit der MTA Einrichtung. Habe dabei die Anleitung von Confixx befolgt, welche Installation darauf folgte.
Schließlich hatte ich aber am Ende zuerst das Problem, dass der SMTP Server nicht wollte. Er sagte mir, dass ein "SASL mechanism" fehlte. Daraufhin habe ich dann saslauthd nachinstalliert und nach einer Anleitung im Internet konfiguriert.
Nun stellt sich aber immer noch ein Problem mit dem POP Server.
Als Kunde in Confixx kann man zwar eine Verbindung zu ihm aufbauen, doch angeblich sind nie eMails auf dem Server vorhanden, also "Keine neuen Nachrichten".
Wenn ich aber in /var/mails reinschaue, sehe ich folgendes:
[Blockierte Grafik: http://img3.imageshack.us/img3/6919/mailsc.th.jpg]
Diese Dateien enthalten die eMails. Doch müssen diese Dateien nicht noch bearbeitet werden bzw. eine Indexdatei (courierpop3dsizelist) erstellt werden, denn die fehlt?
Selbst die Webmail Oberfläche von Confixx sagt, dass INBOX leer ist.
Hier der Inhalt meiner Postfix main.cf:
# See /usr/share/postfix/main.cf.dist for a commented, more complete version
# Debian specific: Specifying a file name will cause the first
# line of that file to be used as the name. The Debian default
# is /etc/mailname.
#myorigin = /etc/mailname
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
# TLS parameters
smtpd_tls_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
smtpd_tls_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
smtpd_use_tls=yes
smtpd_tls_session_cache_database = btree:${data_directory}/smtpd_scache
smtp_tls_session_cache_database = btree:${data_directory}/smtp_scache
# See /usr/share/doc/postfix/TLS_README.gz in the postfix-doc package for
# information on enabling SSL in the smtp client.
myhostname = v220091037361726.yourvserver.net
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = /etc/mailname
mydestination = v220091037361726.yourvserver.net, localhost.yourvserver.net, localhost, v220091037361726, localhost.localdomain
relayhost =
mynetworks = 127.0.0.0/8
#mailbox_command = procmail -a "$EXTENSION"
mailbox_command=/usr/bin/procmail
mailbox_size_limit = 0
recipient_delimiter = +
inet_interfaces = all
smtpd_sasl_auth_enable = yes
smtpd_sasl_security_options = noanonymous
smtpd_sasl_local_domain =
broken_sasl_auth_clients = yes
smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination
### PARALLELS CONFIXX POSTFIX ENTRY ###
virtual_maps = hash:/etc/postfix/confixx_virtualUsers, hash:/etc/postfix/confixx_localDomains
### /PARALLELS CONFIXX POSTFIX ENTRY ###Außerdem läuft die Sache auch noch mit Spamassassin. Dessen Konfigurationsdatei:
# /etc/default/spamassassin
# Duncan Findlay
# WARNING: please read README.spamd before using.
# There may be security risks.
# Change to one to enable spamd
ENABLED=1
# Options
# See man spamd for possible options. The -d option is automatically added.
# SpamAssassin uses a preforking model, so be careful! You need to
# make sure --max-children is not set to anything higher than 5,
# unless you know what you're doing.
#OPTIONS="--create-prefs --max-children 5 --helper-home-dir"
OPTIONS="--local --daemonize --max-children=5"
# Pid file
# Where should spamd write its PID to file? If you use the -u or
# --username option above, this needs to be writable by that user.
# Otherwise, the init script will not be able to shut spamd down.
PIDFILE="/var/run/spamd.pid"
# Set nice level of spamd
#NICE="--nicelevel 15"
# Cronjob
# Set to anything but 0 to enable the cron job to automatically update
# spamassassin's rules on a nightly basis
CRON=0Und hier noch die procmailrc Datei:
# SpamAssassin sample procmailrc
# ==============================
# The following line is only used if you use a system-wide /etc/procmailrc.
# See procmailrc(5) for infos on what it exactly does, the short version:
# * It ensures that the correct user is passed to spamd if spamc is used
# * The folders the mail is filed to later on is owned by the user, not
# root.
DROPPRIVS=yes
# Pipe the mail through spamassassin (replace 'spamassassin' with 'spamc'
# if you use the spamc/spamd combination)
#
# The condition line ensures that only messages smaller than 250 kB
# (250 * 1024 = 256000 bytes) are processed by SpamAssassin. Most spam
# isn't bigger than a few k and working with big messages can bring
# SpamAssassin to its knees.
#
# The lock file ensures that only 1 spamassassin invocation happens
# at 1 time, to keep the load down.
#
:0fw: spamassassin.lock
* < 256000
| /usr/bin/spamc
# Mails with a score of 15 or higher are almost certainly spam (with 0.05%
# false positives according to rules/STATISTICS.txt). Let's put them in a
# different mbox. (This one is optional.)
:0:
* ^X-Spam-Level: \*\*\*\*\*\*\*\*\*\*\*\*\*\*\*
almost-certainly-spam
# All mail tagged as spam (eg. with a score higher than the set threshold)
# is moved to "probably-spam".
:0:
* ^X-Spam-Status: Yes
probably-spam
# Work around procmail bug: any output on stderr will cause the "F" in "From"
# to be dropped. This will re-add it.
# NOTE: This is probably NOT needed in recent versions of procmail
:0
* ^^rom[ ]
{
LOG="*** Dropped F off From_ header! Fixing up. "
:0 fhw
| sed -e '1s/^/F/'
}
DEFAULT=$HOME/Maildir/Ich wäre für Hilfe sehr dankbar!
Christoph
