Email Server High Availability


 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users Email Server High Availability
# 1  
Old 03-09-2016
Email Server High Availability

Hello,

We are planning to setup a Email server with High Availability for email services so that if SMTP/POP/IMAP goes down on one server, the services switch to second server.
We are planning to use a Linux machines from a hosting provider and will do it using DNS with multiple MX records with round robin.

Now i have couple of queries regarding this setup :-
  • Is this possible to have a same domain name to bind with 2 IPs i.e xyz.com point to 1.1.1.1 on one server and xyz.com point to 2.2.2.2 on second server.
  • How can we setup MX records for each server on DNS for email failover.
  • As we have a separate servers for this setup that means data related to email would be reside on separate server (because they have separate HDD), so in case 1st server goes down and it switch to second server, will i skipped my email which was received on 1st server before it goes down as my email client will receive them on certain period of time.

Please let me know if above is a valid query.
Login or Register to Ask a Question

Previous Thread | Next Thread

7 More Discussions You Might Find Interesting

1. Red Hat

Redhat: High Availability

Hi, I want to create gfs storage. But getting error as below: --> Finished Dependency Resolution Error: Package: pacemaker-1.1.12-22.el7_1.2.x86_64 (rhel-ha-for-rhel-7-server-eus-rpms) Requires: sbd You could try using --skip-broken to work around the problem You could try... (1 Reply)
Discussion started by: mzainal
1 Replies

2. Solaris

High availability

hi guys I posted problem last time I didn't find answer to my issue. my problem is as below: I have two servers which work as an actif/standby in high availability system. but when i use command HASTAT -a i have the following message: couldn' find actif node. the servers are sun... (1 Reply)
Discussion started by: zineb06
1 Replies

3. Red Hat

Redhat 5 High Availability Add-on

Hello Experts, I have a question about Redhat HA Add-On, how can i setup an Active/Active Cluster using Redhat 5.7 64Bit, with Round-Robin technique. Each server will run an application and oracle database without RAC. Thanks (0 Replies)
Discussion started by: karmellove
0 Replies

4. AIX

AIX high availability 1-3/69

Hi, Can someone help and give the answer for the following questions: 1. When PowerHA SystemMirror 7.1 is installed on AIX 7.1, what RSCT component does Cluster Aware AIX (CAA) replace? A. Group Services B. Resource Manager C. Topology Services D. Resource Monitoring and Control... (2 Replies)
Discussion started by: walterchang100
2 Replies

5. UNIX for Dummies Questions & Answers

iscsi high availability

Hi, I want to set up a iscsi high availability with sheepdog distributed storage. Here is my system set up. Four nodes with sheepdog distributed storage and i am sharing this storage through iscsi using two nodes as well as using a virtual ip set up using ucarp.Two nodes using same iqn. And... (0 Replies)
Discussion started by: jobycxa
0 Replies

6. UNIX for Advanced & Expert Users

High availability/Load balancing

Hi folks, (Sorry I don't know what its technology is termed exactly. High Availability OR load balancing) What I'm going to explore is as follows:- For example, on Physical Servers; Server-1 - LAMP, a working server Server-2 - LAMP, for redundancy While Server-1 is working all... (3 Replies)
Discussion started by: satimis
3 Replies

7. AIX

AIX and port trunking / high availability

Hi all I was just wondering what modes AIX supports for port trunking ( bonding, etherchannel, link aggregation or whatever you want to call it ) I'm in particular looking for a high availability mode ( other than 802.3ad ) (2 Replies)
Discussion started by: art
2 Replies
Login or Register to Ask a Question
Log::Handler::Output::Email(3pm)			User Contributed Perl Documentation			  Log::Handler::Output::Email(3pm)

NAME
Log::Handler::Output::Email - Log messages as email (via Net::SMTP). SYNOPSIS
use Log::Handler::Output::Email; my $email = Log::Handler::Output::Email->new( host => "mx.bar.example", hello => "EHLO my.domain.example", timeout => 120, debug => 0, from => 'bar@foo.example', to => 'foo@bar.example', subject => "your subject", buffer => 0 ); $email->log(message => $message); DESCRIPTION
With this output module it's possible to log messages via email and it used Net::SMTP to do it. The date for the email is generated with "Email::Date::format_date". Net::SMTP is from Graham Barr and it does it's job very well. METHODS
new() Call "new()" to create a new Log::Handler::Output::Email object. The following opts are possible: host With this option you has to define the SMTP host to connect to. host => "mx.host.com" # or host => [ "mx.host.example", "mx.host-backup.example" ] hello Identify yourself with a HELO. The default is set to "EHLO BELO". timeout With this option you can set the maximum time in seconds to wait for a response from the SMTP server. The default is set to 120 seconds. from The sender address (MAIL FROM). to The receipient address (RCPT TO). Additional options are cc and bcc. subject The subject of the mail. The default subject is "Log message from $progname". buffer This opts exists only for security. The thing is that it would be very bad if something wents wrong in your program and hundreds of mails would be send. For this reason you can set a buffer to take care. With the buffer you can set the maximum size of the buffer in lines. If you set buffer => 10 then 10 messages would be buffered. Set "buffer" to 0 if you want to disable the buffer. The default buffer size is set to 20. debug With this option it's possible to enable debugging. The information can be intercepted with $SIG{__WARN__}. log() Call "log()" if you want to log a message as email. If you set a buffer size then the message will be pushed into the buffer first. Example: $email->log(message => "this message will be mailed"); If you pass the level then its placed into the subject: $email->log(message => "foo", level => "INFO"); $email->log(message => "bar", level => "ERROR"); $email->log(message => "baz", level => "DEBUG"); The lowest level is used: Subject: ERROR: ... You can pass the level with "Log::Handler" by setting message_pattern => '%L' flush() Call "flush()" if you want to flush the buffered lines. sendmail() Call "sendmail()" if you want to send an email. The difference to "log()" is that the message won't be buffered. validate() Validate a configuration. reload() Reload with a new configuration. errstr() This function returns the last error message. DESTROY
"DESTROY" is defined and called "flush()". PREREQUISITES
Carp Email::Date Net::SMTP Params::Validate EXPORTS
No exports. REPORT BUGS
Please report all bugs to <jschulz.cpan(at)bloonix.de>. If you send me a mail then add Log::Handler into the subject. AUTHOR
Jonny Schulz <jschulz.cpan(at)bloonix.de>. COPYRIGHT
Copyright (C) 2007-2009 by Jonny Schulz. All rights reserved. This program is free software; you can redistribute it and/or modify it under the same terms as Perl itself. perl v5.14.2 2012-11-21 Log::Handler::Output::Email(3pm)