----- Original Message ----
> From: Patrick Horgan <phorg...@yahoo.com>
> To: postfix users list <postfix-users@postfix.org>
> Sent: Thu, January 14, 2010 11:10:52 PM
> Subject: Can't send from script and don't understand NOQUEUE error
>
> I'm setting up a python script to do some sysadmin stuff and if it detects a
> problem I want it to email. It does the email, but the server rejects it.
> Taking python out of the picture, I did this:
>
> telnet s2.ootbcomp.com 25
> Trying 66.201.42.40...
> Connected to s2.ootbcomp.com.
> Escape character is '^]'.
> 220 s2.ootbcomp.com ESMTP Postfix
> ehlo localhost
> 250-s2.ootbcomp.com
> 250-PIPELINING
> 250-SIZE 10240000
> 250-VRFY
> 250-ETRN
> 250-STARTTLS
> 250-AUTH PLAIN LOGIN
> 250-AUTH=PLAIN LOGIN
> 250-ENHANCEDSTATUSCODES
> 250-8BITMIME
> 250 DSN
> mail from: patr...@ootbcomp.com
> 250 2.1.0 Ok
> rcpt to: patr...@ootbcomp.com
> 451 4.3.5 Server configuration problem
> rcpt to: patrick
> 451 4.3.5 Server configuration problem
> rcpt to: patr...@ootbcomp.com.
> 451 4.3.5 Server configuration problem
> quit
> 221 2.0.0 Bye
> Connection closed by foreign host.
>
>
> I can email from my machine using firefox to the same address and it works.
>
> On the server, the log shows:
>
> Jan 14 15:03:44 s2 postfix/smtpd[10535]: connect from
> adsl-99-61-74-22.dsl.pltn13.sbcglobal.net[99.61.74.22]
> Jan 14 15:03:44 s2 postfix/smtpd[10535]: warning: connect to 127.0.0.1:60000:
> Connection refused
> Jan 14 15:03:44 s2 postfix/smtpd[10535]: warning: problem talking to server
> 127.0.0.1:60000: Connection refused
> Jan 14 15:03:45 s2 postfix/smtpd[10535]: warning: connect to 127.0.0.1:60000:
> Connection refused
> Jan 14 15:03:45 s2 postfix/smtpd[10535]: warning: problem talking to server
> 127.0.0.1:60000: Connection refused
> Jan 14 15:03:45 s2 postfix/smtpd[10535]: NOQUEUE: reject: RCPT from
> adsl-99-61-74-22.dsl.pltn13.sbcglobal.net[99.61.74.22]: 451 4.3.5 Server
> configuration problem; from=to=
> proto=ESMTP helo=
> Jan 14 15:03:45 s2 postfix/smtpd[10535]: disconnect from
> adsl-99-61-74-22.dsl.pltn13.sbcglobal.net[99.61.74.22]
>
> I would swear this worked yesterday! Where can I look?
>
> Patrick
Seems to me whatever service is running on port 60000 isn't running, and its
causing you these issues.
Thanks.
Daniel Reinhardt
Website: www.cryptodan.com
Email: crypto...@yahoo.com
Junior Network Security Engineer
