About the EHLO command in Wt::Mail::Client::Client()
Added by Zhimin Song over 12 years ago
Hey all friends:
How to write the the EHLO command in Wt::Mail::Client::Client().
I have learned the maybe right command clause, but the log said unexpected response 553,
My command is Client("mail.muc.edu.cn\r\n AUTH PLAIN mybase64\r\n")
It is not right?
Thanks any help!
Regards
Zhimin
Replies (7)
RE: About the EHLO command in Wt::Mail::Client::Client() - Added by Zhimin Song over 12 years ago
oops. probably got it.
The mail server maybe did not install checkpasswd package:-(
maybe
Zhimin
RE: About the EHLO command in Wt::Mail::Client::Client() - Added by Koen Deforche over 12 years ago
Hey Zhimin,
Wt::Mail::Client does not yet support authentication.
But you are welcome to add it, plain authentication should not be too involved.
Regards,
koen
RE: About the EHLO command in Wt::Mail::Client::Client() - Added by Ehsan Mahdavi over 8 years ago
Doesn't it support authentication yet?
These days almost every email servers require authentication because of spam protection features.
Thanks
RE: About the EHLO command in Wt::Mail::Client::Client() - Added by Koen Deforche over 8 years ago
The original thought was to let the mail client connect to a relay SMTP server (on localhost), which then forwards the mail on the internet. That's how linux/macosx servers are typically installed out-of-the box to have email delivered from daemons (to root@localhost).
But perhaps that original assumption is less real than we assumed?
RE: About the EHLO command in Wt::Mail::Client::Client() - Added by Ehsan Mahdavi over 8 years ago
I think the assumption was made 4 or 5 years ago.
The security policies now are different.
I tried to have local postfix installed and when trying that for example with gmail recipients, google says the server with address x(my address) is not authorized to send email directly to our servers. We then need to submit a request for each single copy of our application to be authorized.
On the other hands there are some policies in spam databases to white-list specific IP addresses and black-list some others. Assume that I am going to sell my application to regular customers who don't have static IP addresses and their current address is used by some affected clients before. Now the IP address is marked black and my customers will be disabled to send emails day by day. Yesterday they could, now they can't. What about tomorrow? Can't say!
So there is now an obvious need for the email client to authenticate itself using a username/password to a known mail server.
What's ur idea?
RE: About the EHLO command in Wt::Mail::Client::Client() - Added by Koen Deforche over 8 years ago
In any case, this means that you have a relay host to which you're allowed to send email (and which has certain protection, which might include authentication), right?
So instead of having your application connect directly to this (relay) server, you can setup a local postfix that forwards to this (relay) server, while your application uses the local postfix?
The local postfix server will indeed not typically be an internet mail host.
RE: About the EHLO command in Wt::Mail::Client::Client() - Added by Ehsan Mahdavi over 8 years ago
Well Well Well...
I was using the local postfix, I just had to configure to do the authentication. I used this [[http://postfix.state-of-mind.de/patrick.koetter/smtpauth/smtp_auth_mailservers.html\]] and it seems to be working just great.
Thank you