Sendmail - issue within DMZ for some servers but not all
Hi All,
I have a strange issue and I am not sure where the problem lies.
I have about six Ubuntu servers on our DMZ two of which were built on 18.04 from scratch the others were upgraded to 18.04 from 16.04.
The servers built from scratch can send emails from the server via sendmail fine, so the Firewall rules for coming from DMZ to our internal network is fine.
The servers upgraded to 18.04 cannot send out emails, it is as if sendmail does not work.
This is what I get
Code:
root@DMZ-Server:~# echo "test" | sendmail -v me@domain
domain: Name server timeout
me@domain... Transient parse error -- message queued for future delivery
me@domain... queued
root@DMZ-Server:~#
I have uninstalled & purged sendmail from a server that does not work and re-installed.
I have updated the sendmail.cf to point to the mail server
Code:
define(`SMART_HOST',`MailServer.domain')dnl
the Hosts file has the relevant info...
It still does not work...
could someone help or point me in the right direction?
I am having the same issue on all systems in the DMZ that have updated from 16.04 - 18.04
Hi gurus!
I need help to make sendmail to accept unknown user mail. That is if the user does not exist sendmail keep on processing the mail and store it in a some mailbox ...
Thanks for any idea! (5 Replies)
Hi,
yesterday I had issues, sendmail was not responding quickly while sending email and users did not receive any email,
This happened with sendmail on solaris 10 and also with sendmail on a linux box.
Found it is something to do with DNS blacklists,
following lists did not work for me,... (2 Replies)
Hi Team,
I have a script written to sendmail along with attachment in html format.
The code is
export MAILFROM="abc@abc.com"
export MAILTO="abc@abc.com"
export CONTENT="./GRP_SPI_ERR.html"
export SUBJECT="TEST EMAIL: TESTING HTML"
{
print - "From: $MAILFROM"
print - "To: ${MAILTO}"... (3 Replies)
Hi, Guru
i had configure in my two server to send out the email.
One of the server able to send in the reasonable timing. but another not, it delay almost one day or two days but mostly not send at all.
below is the syslog when i try to send out the mail.
GOOD Server
Dec 28 11:29:39... (5 Replies)
Hi all,
we are using solaris 10. we need to increase every users mail boxes size as all users mail boxes got filled..Please help..its urgent..
Thanks in advance.. (1 Reply)
Hi Gurus,
I have been tampering around with sendmail for the past one week and seem to make little progress. Given below is an abstract of the issue.
I have a Fedora 12 server(A VM on vitual Box bridged with a Windows XP host) which has to act as a SMTP server and have accordingly put up the... (8 Replies)
Hi Every One,
one of our server configuration on sendmail config
we are using SMAR_HOST
###
define(`SMART_HOST', 'mail.xxx.com')
and /etc/sysconfig/sednmail DAEMON is setted to NO
so let me know why sendmail is not working for this server
any this else u need please do let me know (0 Replies)
Hi,
I'm using sendmail version 8.13.8-8.1.el5_7. I'm pretty new to it. The servera are running RHEL 5.8. My question basically is that I would want to know is there a way to change the from address. I would be able to change it using the return address in mailx command. However I would like to... (3 Replies)
Dear All ,
I have some problem in Sendmail , where it was sending mails perfectly fine with the Ip address of the client machine.
But suddenly there was an issue , the SMTP takes the IP of the bond1 interface.
So the IP could not get validated in the relay server.
So how should i send... (1 Reply)
Discussion started by: jegaraman
1 Replies
LEARN ABOUT DEBIAN
smtpdcheck
smtpdcheck(1) Mail Avenger 0.8.3 smtpdcheck(1)NAME
smtpdcheck - check SMTP servers
SYNOPSIS
smtpdcheck [--stop {ip-addr|name}] [--timeout seconds]
[prio:]server [[prio:]server]
DESCRIPTION
smtpdcheck checks to see if SMTP servers are available. The intent is for use on secondary mail servers, which have no reason to accept
mail when the primary server is available.
The argument consists of a list of server names, each of which may optionally be prefixed by a numeric MX priority and a colon. (This is
exactly the format for MX records returned by the avenger dns command.) smtpdcheck will attempt to connect to each server in succession.
If one of the servers specified on the command line is available, smtpdcheck will print its name to standard output and exit with status 1.
If smtpdcheck cannot connect to any of the servers, it will exit with status 0. If a system error occurs, smtpdcheck will exit with status
2.
OPTIONS
--stop {ip-addr|name}
Tells smtpdcheck to stop before checking a server with IP address ip-addr or hostname name. If such a host is encountered in the list
of servers and prio is specified, then smtpdcheck will consider it acceptable for other servers with the same priority to be available,
even if those servers were first in the list. In other words, given the following arguments:
smtpdcheck --stop s2.domain.com
10:s1.domain.com 10:s2.domain.com
20:s3.domain.com
This command will always succeed, regardless of whether "s1.domain.com" is up, because "s2.domain.com" has the same priority. On the
other hand, the following command will fail and output "s1.domain.com" if "s1.domain.com" is up:
smtpdcheck --stop s2.domain.com
10:s1.domain.com 20:s2.domain.com
30:s3.domain.com
If a gethostbyname lookup for the argument name fails, smtpdcheck will exit immediately with status 2.
--timeout {seconds]
By default, smtpdcheck spends 10 seconds probing each server. This includes the time to do a DNS lookup, to establish a TCP connection
to port 25 of the server, and to read the "220" SMTP code from the server's SMTP greeting message. To use a different value, specify
it with the --timeout option. The value 0 disables the timeout completely, which is dangerous since smtpdcheck might then end up
waiting forever to read the "220" string.
EXAMPLES
To refuse to relay mail at a secondary MX server when the primary server is not down, you might place the following in
/etc/avenger/secondary (assuming MxLocalRcpt is 1):
dns RECIP_MXES mx "$RECIPIENT_HOST"
setvars
server=`smtpdcheck --stop $MYIP $RECIP_MXES`
test -n "$server" && defer "Please use server $server"
SEE ALSO avenger(1)dbutil(1)asmtpd.conf(5),
The Mail Avenger home page: <http://www.mailavenger.org/>.
BUGS
smtpdcheck could achieve much lower latency by probing all the servers simultaneously. It should also include some kind of caching, to
avoid repeatedly trying to contact an unavailable server. Finally, hosts with multiple IP addresses could be handled more cleanly, though
what smtpdcheck does should probably work in most cases.
AUTHOR
David Mazieres
Mail Avenger 0.8.3 2012-04-05 smtpdcheck(1)