[Postfixbuch-users] trotz SMTPAUTH keine sichere Authentifikation

[Mark Riemann]

Patrick Ben Koetter schrieb:
> Ooops. Das sehen wir uns genauer an.
> Starte mal saslauthd so:
> # saslauthd -a rimap -O mail.meineDomain.de -d
> 
> und mail dann den output.

-- SCHNIPP --
root at meineDomain: (/var/log) >  saslauthd -a rimap -O mail.meineDomain.de -d
saslauthd[3590] :main            : num_procs  : 5
saslauthd[3590] :main            : mech_option: mail.meineDomain.de
saslauthd[3590] :main            : run_path   : /var/state/saslauthd
saslauthd[3590] :main            : auth_mech  : rimap
saslauthd[3590] :ipc_init        : using accept lock file: 
/var/state/saslauthd/mux.accept
saslauthd[3590] :detach_tty      : master pid is: 0
saslauthd[3590] :ipc_init        : listening on socket: 
/var/state/saslauthd/mux
saslauthd[3590] :main            : using process model
saslauthd[3590] :have_baby       : forked child: 3619
saslauthd[3619] :get_accept_lock : acquired accept lock
saslauthd[3590] :have_baby       : forked child: 3648
saslauthd[3590] :have_baby       : forked child: 3682
saslauthd[3590] :have_baby       : forked child: 3712
-- SCHNAPP --

Nach einem STRG+C folgt:

-- SCHNIPP --
saslauthd[3619] :server_exit     : child exited: 3619
saslauthd[3648] :server_exit     : child exited: 3648
saslauthd[3619] :server_exit     : child exited: 3619
saslauthd[3590] :server_exit     : pid file lock removed: 
/var/state/saslauthd/saslauthd.pid.lock
saslauthd[3590] :ipc_cleanup     : accept lock file removed: 
/var/state/saslauthd/mux.accept
saslauthd[3590] :ipc_cleanup     : socket removed: /var/state/saslauthd/mux
saslauthd[3590] :server_exit     : master exited: 0
saslauthd[3682] :server_exit     : child exited: 3682
saslauthd[3712] :server_exit     : child exited: 3712
root at meineDomain: (/var/log) >
-- SCHNAPP --


>>drwxr-xr-x    2 root     root         2048 Okt 14 19:33 saslauthd
> 
> gut. Postfix darf rein.

Wie kommst von meinem Posting darauf? Weil für others r-x ist?


>>>Darf Postfix da rein? Läuft Postfix mittlerweile vielleicht chrooted?
>>Wie stelle ich das fest?
> 
> Werf mal einen blick in die master.cf ;)

Der Inhalt meiner /etc/postfix/master.cf:
-- SCHNIPP --
==========================================================================
# service type  private unpriv  chroot  wakeup  maxproc command + args
#               (yes)   (yes)   (yes)   (never) (100)
# ==========================================================================
smtp      inet  n       -       n       -       -       smtpd
#submission inet n      -       n       -       -       smtpd
#       -o smtpd_etrn_restrictions=reject
#628      inet  n       -       n       -       -       qmqpd
pickup    fifo  n       -       n       60      1       pickup
cleanup   unix  n       -       n       -       0       cleanup
qmgr      fifo  n       -       n       300     1       qmgr
#qmgr     fifo  n       -       n       300     1       oqmgr
rewrite   unix  -       -       n       -       -       trivial-rewrite
bounce    unix  -       -       n       -       0       bounce
defer     unix  -       -       n       -       0       bounce
trace     unix  -       -       n       -       0       bounce
verify    unix  -       -       n       -       1       verify
flush     unix  n       -       n       1000?   0       flush
proxymap  unix  -       -       n       -       -       proxymap
smtp      unix  -       -       n       -       -       smtp
relay     unix  -       -       n       -       -       smtp
-- SCHNAPP --


MfG
Mark