Mails versenden mittels postfix

Hello,

I#m running SuSE 8.2 pro. Up to now relaying mail unsing postfix worked
without any problem. Since some days mails stay in the mailq with the
message: (transport unavailable).

In /var/log/mail.warn I found several lines similiar to the following:

Dec 2 14:01:28 ragged postfix/qmgr[10030]: warning: connect to transport
smtp: Connection refused

postconf -n says:

ragged:/home/vha # postconf -n
alias_maps = hash:/etc/aliases
canonical_maps = hash:/etc/postfix/canonical
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = vscan:
daemon_directory = /usr/lib/postfix
debug_peer_level = 2
defer_transports =
disable_dns_lookups = no
inet_interfaces = 127.0.0.1
mail_owner = postfix
mail_spool_directory = /var/mail
mailbox_command =
mailbox_size_limit = 51200000
mailbox_transport =
mailq_path = /usr/bin/mailq
manpage_directory = /usr/share/man
masquerade_classes = envelope_sender, header_sender, header_recipient
masquerade_domains = virtuatron.de
masquerade_exceptions = root
message_size_limit = 10240000
mydestination = $myhostname, localhost.$mydomain
myhostname = ragged.ID-132536.user.dfncis.de
newaliases_path = /usr/bin/newaliases
program_directory = /usr/lib/postfix
queue_directory = /var/spool/postfix
readme_directory = /usr/share/doc/packages/postfix/README_FILES
relayhost = mail.bytecamp.net
relocated_maps = hash:/etc/postfix/relocated
sample_directory = /usr/share/doc/packages/postfix/samples
sender_canonical_maps = hash:/etc/postfix/sender_canonical
sendmail_path = /usr/sbin/sendmail
setgid_group = maildrop
smtp_sasl_auth_enable = yes
smtp_sasl_password_maps = hash:/etc/postfix/sasl_passwd
smtp_sasl_security_options =
smtp_use_tls = no
smtpd_client_restrictions =
smtpd_helo_required = no
smtpd_helo_restrictions =
smtpd_recipient_restrictions = permit_mynetworks,reject_unauth_destination
smtpd_sasl_auth_enable = no
smtpd_sender_restrictions = hash:/etc/postfix/access
smtpd_use_tls = no
strict_rfc821_envelopes = no
transport_maps = hash:/etc/postfix/transport
unknown_local_recipient_reject_code = 450

My master.cf:

# service type private unpriv chroot wakeup maxproc command + args
# (yes) (yes) (yes) (never) (100)
# ================================================== ========================
smtp inet n - n - - smtpd
#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
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 nqmgr
#tlsmgr fifo - - n 300 1 tlsmgr
rewrite unix - - n - - trivial-rewrite
bounce unix - - n - 0 bounce
defer unix - - n - 0 bounce
flush unix n - n 1000? 0 flush
proxymap unix - - n - - proxymap
smtp inet n - y - - smtpd
relay unix - - n - - smtp
# -o smtp_helo_timeout=5 -o smtp_connect_timeout=5
showq unix n - n - - showq
error unix - - n - - error
local unix - n n - - local
virtual unix - n n - - virtual
lmtp unix - - n - - lmtp
localhost:10025 inet n - n - - smtpd -o
content_filter=
#
# 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}
cyrus unix - n n - - pipe
user=cyrus argv=/usr/lib/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}
procmail unix - n n - - pipe
flags=R user=nobody argv=/usr/bin/procmail -t -m /etc/procmailrc ${sender}
${recipient}


I doublechecked the mailserver and the password. There are no errors. I hope
anyone has an idea why this does not work anymore.

CU Volker

--
# This is by-design behavior, not a security vulnerability.
# Scott Culp, Microsoft Security Response Center
# SPAM-Count since 09/2003: 363 UCEs.

Volker Hartmann wrote:

> In /var/log/mail.warn I found several lines similiar to the following:
>
> Dec 2 14:01:28 ragged postfix/qmgr[10030]: warning: connect to transport
> smtp: Connection refused

[..]

> relayhost = mail.bytecamp.net

So ganz spontan würd ich sagen, dass entweder dein Passwort oder dein
Benutzername nicht stimmen kann, oder dass beim Anmelden an den Relayhost
irgendein anderer Fehler auftritt. Am einfachsten wäre es wahrscheinlich,
du frägst beim Betreiber des Relayhosts nach, wieso dir die Verbindung
verweigert wird. Der kann dir normalweise sagen, wo das Problem liegt.

--
Michael Dürgner
Informatik-Student
Wise men don't need advice. Fools don't take it.
- Benjamin Franklin -

Michael Duergner wrote:

> Volker Hartmann wrote:
>
>> In /var/log/mail.warn I found several lines similiar to the following:
>>
>> Dec 2 14:01:28 ragged postfix/qmgr[10030]: warning: connect to transport
>> smtp: Connection refused
>
> [..]
>
>> relayhost = mail.bytecamp.net
>
> So ganz spontan würd ich sagen, dass entweder dein Passwort oder dein
> Benutzername nicht stimmen kann, oder dass beim Anmelden an den Relayhost
> irgendein anderer Fehler auftritt. Am einfachsten wäre es wahrscheinlich,
> du frägst beim Betreiber des Relayhosts nach, wieso dir die Verbindung
> verweigert wird. Der kann dir normalweise sagen, wo das Problem liegt.
>
Hello Michael,

the admin at bytecamp says, no conections from my ip to the mailserver when
I am trying to send mail via postfix. No outgoing packets blocked by my
firewall. POP3 using kmail works.

CU Volker
--
# This is by-design behavior, not a security vulnerability.
# Scott Culp, Microsoft Security Response Center
# SPAM-Count since 09/2003: 365 UCEs.

Volker Hartmann wrote:

> Hello,
>
> I#m running SuSE 8.2 pro. Up to now relaying mail unsing postfix worked
> without any problem. Since some days mails stay in the mailq with the
> message: (transport unavailable).
>
Works again. Renamed main.cf and master.cf and reinstalled poxtfix rpms.
Must
have been some configuration issue.

--
# This is by-design behavior, not a security vulnerability.
# Scott Culp, Microsoft Security Response Center
# SPAM-Count since 09/2003: 366 UCEs.