Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
As the message states: protocol error: 571 Delivery not authorized, message refused. You are not authorized to send mail using that server. If you administer the destination server you'll have to add your server/ip to the allowed ones or provide correct authentication. If you don't administer the destination server, you'll have to take it up with the admin that does.
And please don't use words like asap. What's urgent to you is not to us, we're all volunteers.
Since you have to authenticate then the problem is either on your side if you're not providing the correct credentials or on the other side if the other server doesn't accept your connection. Both ways can cause the error. If you have to authenticate providing a user name you could try the connection with a telnet session. If you don't have to provide credentials are you allowed to relay to that host?
Yes i am on a static WAN IP...
i was once listed in URIBL,but was delisted too,again today i was listed on the same.
m not sure that RBL is causing a problem as previously when i was listed for 2-3 days the mails were delivered.
Strange, I don't know much more to try. If you can access the server using telnet and send a mail from the console in that same telnet session, then you can exclude the credentials.
OK, you'll have to go through your smtp logs to find out what commands you're sending and what responses you're receiving and debug from there on to find the error.
You also might want to set your loglevel a bit higher in order to get more info. Once you set your loglevel, restart your sendmail, try sending a mail from a telnet session (all the steps) and after that the normal way you do. Then check your logfile for errors/communication.