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.
There is less than 12 hours left to vote in the 2015 LinuxQuestions.org Members Choice Awards. Click here to go to the polls. Vote now and make sure your voice is heard!
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.
It should say "Queuing for node 192.168.1.1", given the information you gave above. But let's assume it was a typo.
So, at this point the secondary server will try to make an SMTP connection to your primary. If something went wrong, it would be in the logs. Also, make sure you can "telnet 192.168.1.1 25" from the secondary.
It's not complaining about the syntax (listing an ip address after ETRN). But, according to RFC 1985,
The specified node name must be a fully qualified domain name for the
node, which may refer to a CNAME or MX pointer in the DNS. If an
alias is used for the node, multiple ETRN commands may be needed to
start the processing for the node as it may be listed at the remote
site under multiple names. This can also be addressed using the
options discussed in section 5.3.
Instead of scattering your mail in various computers, you can arrange for all mail to be delivered to a central IMAP server. Then, users can use an IMAP client, such as mutt or thunderbird, to read their mail by connecting to the server. It's clean, because all mail remains on the server.