Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
Notices
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I want to make a backup mail server, and i am testing the posibilities to do the transfer between the second mail server and the main. These 2 servers are in the same network.
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,
Quote:
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.