Noel Jones wrote:
On 1/29/2010 4:46 PM, Wade Smart wrote:
Noel Jones wrote:
On 1/28/2010 4:57 PM, Wade Smart wrote:
I have been using postfix for about two + years but something that was
just out of my understanding at the time was setting up relaying.
Right now I just sent from my mail client (thunderbird) but I would
like to be able to send back through postfix to keep a record of all
sent mails.
Im getting this error:
postfix/smtp[18963]:
499E1B1B64: to=<wadesm...@gmail.com>,
relay=72.167.82.80[72.167.82.80]:465,
delay=7822,
delays=7522/0.06/300/0,
dsn=4.4.2,
status=deferred (lost connection with 72.167.82.80[72.167.82.80] while
receiving the initial server greeting)
sm...@smart-laptop:~$ postconf -n
...
relayhost = 72.167.82.80:465
(side note, the IP should be enclosed in brackets,
relayhost = [72.167.82.80]:port
but that's probably unrelated to this problem.)
Using port 465 implies that the client is expecting wrapper-mode TLS.
This mode is deprecated for email use and not directly supported by
postfix.
The vast majority of mail relays also support using the standard
"submission" interface at port 587, which is the strongly preferred
port.
If it's an antique mail relay that doesn't support the submission
port, a workaround for client side wrapper mode is described here:
http://www.postfix.org/TLS_README.html#client_smtps
-- Noel Jones
I contacted the company and, you were right, so I changed the port and I
added the brackets. Similar error message:
relay=non delay=35 delays=4.6/0.08/30/0 dns=4.41 status=deferred
(connect to 72.167.82.80[72.167.82.80]:587: Connection timed out)
Hmm, testing from here:
# telnet 72.167.82.80 587
Trying 72.167.82.80...
telnet: connect to address 72.167.82.80: Operation timed out
telnet: Unable to connect to remote host
So it looks like 587 isn't available. At least from here.
Let's try 465. This requires openssl rather than telnet...
# openssl s_client -connect 72.167.82.80:465
CONNECTED(00000003)
depth=3 /L=ValiCert Validation Network/O=ValiCert,
[big SSL handshake snipped]
...certificate chain)
---
220 p3plsmtpa01-09.prod.phx3.secureserver.net ESMTP
OK, 465 works for me.
Lets try port 25.
# telnet 72.167.82.80 25
Trying 72.167.82.80...
Connected to p3plsmtpa01-v01.prod.phx3.secureserver.net.
Escape character is '^]'.
220 p3plsmtpa01-04.prod.phx3.secureserver.net ESMTP
OK, port 25 works. So it looks as if they gave you bad information
about port 587. You'll either need to use port 25, or if your ISP
blocks that, you'll need to use the stunnel workaround to connect to 465.
Ok, Im just going to ask this because.. I dont know.
You "can" connect to a normal smtp port with postfix, right?
I mean, I get my email from Godaddy and Im using or wanted postfix to
send my mail back through my account.
Wade
Yes, of course. But something (firewall, ISP policy, or other end just
isn't listening) can block postfix's access to whatever port you're
trying to use.
-- Noel Jones
Someone posted me this link.
https://help.ubuntu.com/community/GmailPostfixFetchmail
After trying it with Gmail I tried it with Godaddy.
It is working because Im getting my test messages but Im getting all
sorts of errors the log:
to=<sm...@wadesmart.com>
relay=smtpout.where.secureserver.net[64.202.165.58]:3535,
delay=309
delays=309/0.03/0.32/0
dns=4.74
status=deferred (TLS is required, but was not offered by host....)
Im using port 3535 because I found a post online about someone had
success with that port (and I use that with my mail client to.)
Wade
--
Registered Linux User: #480675
Registered Linux Machine: #408606
Linux since June 2005
