Unable to send mail through 587 since upgrade to 8.4.0

[Hal9000]

Hello!
Since I upgraded my Plesk to 8.4.0, users using the alternate 587 port have since been unable to send emails.

Server Response: 553 sorry, that domain isn't in my list of allowed rcpthosts (#5.7.1)

I didn't change my settings, the relay is set to smtp authentication.

/etc/xinetd.d/smtp_psa_alt looks like this

service smtp_alt
{
socket_type = stream
protocol = tcp
wait = no
disable = no
user = root
instances = UNLIMITED
server = /var/qmail/bin/tcp-env
server_args = -Rt0 /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true
}

What can i do? It's pretty urgend, since there are many providers blocking port 25 thus several users are unable to send email right now!

Hal

[wsani]

See here: http://forum.swsoft.com/showthread.php?p=205717#post205717

[Hal9000]

thanks, adding env = SMTPAUTH=1 to /etc/xinetd.d/smtp_psa_alt fixed the problem.

[DiLDoG]

I'm still having this problem (psa v8.4.0_build84080515.08 os_Debian 4.0), and I can't find any of these smtp config files. The only thing close is inetd.conf, wich has this line:

#:OTHER: Other services
ftp stream tcp nowait root /usr/sbin/tcpd in.proftpd
smtp stream tcp nowait.1000 root /var/qmail/bin/tcp-env tcp-env /usr/bin/env SMTPAUTH=1 POPAUTH=1 POPLOCK_TIME=20 END=1 /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true
smtps stream tcp nowait.1000 root /var/qmail/bin/tcp-env tcp-env /usr/bin/env SMTPAUTH=1 POPAUTH=1 POPLOCK_TIME=20 END=1 /var/qmail/bin/relaylock /var/qmail/bin/qmail-smtpd /var/qmail/bin/smtp_auth /var/qmail/bin/true /var/qmail/bin/cmd5checkpw /var/qmail/bin/true

poppassd stream tcp nowait/1000 root /usr/sbin/tcpd /opt/psa/admin/bin/poppassd

When I change Relay options in plesk this file gets modified. What should I do?

[bsandor]

I wrote my solution here: http://forum.swsoft.com/showthread.php?t=53561&highlight=inetd.conf

I hope it will help you. :)