06-10-2016
Mail server issue reoccurred
The mail server issue has reoccurred, however this time, all the mailbox servers are affected. There are about 10 - 12 mailbox servers which are not sending emails out.
The email relay server is also included here.
The email relay server is not pingable from the affected servers, but they are pingable from the jumpbox which is used to access these mailbox servers.
From the logs (mail.log) that I have checked from one of the servers, it shows "Connection timed out" error to the email relay server.
7 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi Unix Gurus,
Please help me out here.
Please tell me the steps to conigure sendmail to receive emails (same way we configure outlook client in windows)?
Thanks in advance.
-Dejavu (1 Reply)
Discussion started by: DejaVu
1 Replies
2. AIX
Hi, can any one help as i am unable to receive mail to outlook mail box from aix box.
Kindly help. (2 Replies)
Discussion started by: richajoy
2 Replies
3. Shell Programming and Scripting
Hi All,
I am writing one script to automate one long process. In this process we need to upload some input files and download some output files. So , I want to automate this upload and download by using mail functionality.
I want to trigger this script when I am sending mail to server. I know... (0 Replies)
Discussion started by: NirajThakar
0 Replies
4. UNIX for Advanced & Expert Users
Hello there,
First of all I tell you that this is my first postfix installation so please be patient...
I have following scenario:
fetchmail --> postfix --> amavis-new --> postfix --> exchange 2010.
Everything -except exchange ;-)- runs on an opensuse 12.1 box.
Now, I have a list of... (0 Replies)
Discussion started by: lpacor
0 Replies
5. UNIX and Linux Applications
Hello there,
First of all I tell you that this is my first postfix installation so please be patient...
I have following scenario:
fetchmail --> postfix --> amavis-new --> postfix --> exchange 2010.
Everything -except exchange ;-)- runs on an opensuse 12.1 box.
Now, I have a list of... (0 Replies)
Discussion started by: lpacor
0 Replies
6. UNIX for Dummies Questions & Answers
Hello there,
First of all I tell you that this is my first postfix installation so please be patient...
I have following scenario:
fetchmail --> postfix --> amavis-new --> postfix --> exchange 2010.
Everything -except exchange ;-)- runs on an opensuse 12.1 box.
Now, I have a list of... (2 Replies)
Discussion started by: lpacor
2 Replies
7. UNIX for Dummies Questions & Answers
HI experts,
By using mailx command i can send mails to any email id. and my DNS is like
oper@xyz.com ..... but if someone replied to the mail sent earlier using mailx command. then how to recieve or view that mail ...
Is dre any command to do the same ... Im working on some project and got... (7 Replies)
Discussion started by: ankitknit
7 Replies
LEARN ABOUT DEBIAN
dhcp-helper
DHCP-HELPER(8) System Manager's Manual DHCP-HELPER(8)
NAME
dhcp-helper - A DHCP/BOOTP relay agent.
SYNOPSIS
dhcp-helper [OPTION]...
DESCRIPTION
dhcp-helper is a DHCP and BOOTP relay agent. It listens for DHCP and BOOTP broadcasts on directly connected subnets and relays them to DHCP
or BOOTP servers elsewhere. It also relays replies from the remote servers back to partially configured hosts. Once hosts are fully config-
ured they can communicate directly with their servers and no longer need the services of a relay.
OPTIONS
The only required option is at least one DHCP server to relay to. The simplest way to configure dhcp-helper on a router is just to give the
interface to the network containing the DHCP server with a -b option. All the other interfaces present on the machine will then accept DHCP
requests. On a machine which does not have an interface on the network containing the DHCP server, use a -s option instead.
-s <server>
Specify a DHCP or BOOTP server to relay to. The server may be given as a machine name or dotted-quad IP address. More than one
server may be specified.
-b <interface>
Relay to a DHCP or BOOTP server using broadcast via <interface>. This eliminates the need to give a server address. <interface> is
automatically added to the list of interfaces which will not receive DHCP requests.
-i <interface>
Specify which local interfaces to listen on for DHCP/BOOTP broadcasts. If no -i flags are given all interfaces are used except those
specified by -e flags and those specified by -b flags.
-e <interface>
Specify which local interfaces to exclude.
-p Use alternative ports (1067/1068) for the DHCP client and server.
-v Report the software release version and copyright information.
-d Debug mode, do not change UID, write a pid-file or go into the background.
-r <file>
Specify an alternate path for dhcp-helper to record its process-id in. Normally /var/run/dhcp-helper.pid.
-u <username>
Specify the userid to which dhcp-helper will change after startup. The daemon must normally be started as root, but it will drop
root priviledges after startup by changing id to another user. Normally this user is "nobody" but that can be over-ridden with this
switch.
NOTES
Dhcp-helper requires a 2.2 or later Linux kernel. The "Linux packet filter" and "packet socket" facilities are not required, which is the
chief advantage of this software over the ISC DHCP relay daemon.
AUTHOR
This manual page was written by Simon Kelley <simon@thekelleys.org.uk>.
DHCP-HELPER(8)