Strona 1 z 1

Problem postfix

: 06 sierpnia 2014, 13:48
autor: uh4
Witam,
Znowu problem z postfixem
Przy wysyłaniu maila z programu outlock wyskakują mi takie błędy:
root@budma24:/var/log# tail -f mail.log
Aug 6 13:43:12 budma24 postfix/anvil[965]: statistics: max connection rate 1/60s for (smtp:94.158.225.22) at Aug 6 13:39:51
Aug 6 13:43:12 budma24 postfix/anvil[965]: statistics: max connection count 1 for (smtp:94.158.225.22) at Aug 6 13:39:51
Aug 6 13:43:12 budma24 postfix/anvil[965]: statistics: max cache size 1 at Aug 6 13:39:51
Aug 6 13:44:38 budma24 postfix/smtpd[997]: warning: hostname revdns-94-158-225-22.jjs.pl does not resolve to address 94.158.225.22: Name or service not known
Aug 6 13:44:38 budma24 postfix/smtpd[997]: connect from unknown[94.158.225.22]
Aug 6 13:44:38 budma24 postfix/smtpd[997]: NOQUEUE: reject: RCPT from unknown[94.158.225.22]: 554 5.7.1 <uh4@wp.pl>: Relay access denied; from=<uh@budma24.pl> to=<uh4@wp.pl> proto=SMTP helo=<userKomputer>
Aug 6 13:44:38 budma24 postfix/smtpd[997]: NOQUEUE: reject: RCPT from unknown[94.158.225.22]: 554 5.7.1 <uh4@wp.pl>: Relay access denied; from=<uh@budma24.pl> to=<uh4@wp.pl> proto=SMTP helo=<userKomputer>
Aug 6 13:44:38 budma24 postfix/smtpd[997]: disconnect from unknown[94.158.225.22]
Aug 6 13:44:38 budma24 dovecot: pop3-login: Login: user=<uh>, method=PLAIN, rip=94.158.225.22, lip=185.49.12.237, mpid=1005, session=<ogY5f/T/AwBenuEW>
Aug 6 13:44:38 budma24 dovecot: pop3(uh): Disconnected: Logged out top=0/0, retr=0/0, del=0/0, size=0
main.cf
root@budma24:/var/log# cat /etc/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


readme_directory = no


# 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=no (tu zmieniłem ale nic się nie dzieje)
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 = budma24.pl
alias_maps = hash:/etc/aliases
alias_database = hash:/etc/aliases
myorigin = /etc/mailname
mydestination = budma24.pl
relayhost =
mynetworks = 127.0.0.0/8 [::ffff:127.0.0.0]/104 [::1]/128
mailbox_command = procmail -a "$EXTENSION"
mailbox_size_limit = 0
recipient_delimiter = +
#inet_interfaces = all
smtpd_sasl_auth_enable = yes
smtpd_sasl_type = dovecot
smtpd_sasl_path = private/auth
#smtpd_recipient_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination (tu zmieniłem ale nic się nie dzieje)
smtpd_relay_restrictions = permit_mynetworks, permit_sasl_authenticated, reject_unauth_destination
Co ciekawe wszystko działało, aż przestało :)
PS przez program ALPINE na koncie shell poczta działa bez problemów.

Pozdrawiam

: 06 sierpnia 2014, 15:47
autor: LordRuthwen
Serwer wymaga uwierzytelnienia masz zaznaczone?
Jak wygląda konfiguracja SASL?

: 09 sierpnia 2014, 11:42
autor: uh4
sasl chyba dobrze jest skonfigurowany.
Server poczty działał i nagle przestaly byc wysylane maile przez outlocka
pwcheck_method: saslauthd
mech_list: plain login
#
# Settings for saslauthd daemon
# Please read /usr/share/doc/sasl2-bin/README.Debian for details.
#


# Should saslauthd run automatically on startup? (default: no)
START=yes


# Description of this saslauthd instance. Recommended.
# (suggestion: SASL Authentication Daemon)
DESC="SASL Authentication Daemon"


# Short name of this saslauthd instance. Strongly recommended.
# (suggestion: saslauthd)
NAME="saslauthd"


# Which authentication mechanisms should saslauthd use? (default: pam)
#
# Available options in this Debian package:
# getpwent -- use the getpwent() library function
# kerberos5 -- use Kerberos 5
# pam -- use PAM
# rimap -- use a remote IMAP server
# shadow -- use the local shadow password file
# sasldb -- use the local sasldb database file
# ldap -- use LDAP (configuration is in /etc/saslauthd.conf)
#
# Only one option may be used at a time. See the saslauthd man page
# for more information.
#
# Example: MECHANISMS="pam"
MECHANISMS="pam"


# Additional options for this mechanism. (default: none)
# See the saslauthd man page for information about mech-specific options.
MECH_OPTIONS=""


# How many saslauthd processes should we run? (default: 5)
# A value of 0 will fork a new process for each connection.
THREADS=2


# Other options (default: -c -m /var/run/saslauthd)
# Note: You MUST specify the -m option or saslauthd won't run!
#
# WARNING: DO NOT SPECIFY THE -d OPTION.
# The -d option will cause saslauthd to run in the foreground instead of as
# a daemon. This will PREVENT YOUR SYSTEM FROM BOOTING PROPERLY. If you wish
# to run saslauthd in debug mode, please run it by hand to be safe.
#
# See /usr/share/doc/sasl2-bin/README.Debian for Debian-specific information.
# See the saslauthd man page and the output of 'saslauthd -h' for general
# information about these options.
#
# Example for chroot Postfix users: "-c -m /var/spool/postfix/var/run/saslauthd"
# Example for non-chroot Postfix users: "-c -m /var/run/saslauthd"
#
# To know if your Postfix is running chroot, check /etc/postfix/master.cf.
# If it has the line "smtp inet n - y - - smtpd" or "smtp inet n - - - - smtpd"
# then your Postfix is running in a chroot.
# If it has the line "smtp inet n - n - - smtpd" then your Postfix is NOT
# running in a chroot.
OPTIONS="-c -m /var/run/saslauthd"
root@budma24:/var/run/saslauthd# testsaslauthd -u XXXXXXXX -p XXXXXXXXX -f /var/run/saslauthd/mux
0: OK "Success."

: 10 sierpnia 2014, 11:00
autor: uh4
Pomoże ktoś?

: 16 sierpnia 2014, 23:44
autor: uh4
Zna ktoś rozwiązanie?