Sponsored Content
Full Discussion: Sendmail Error
Operating Systems Solaris Sendmail Error Post 302933956 by nimika on Tuesday 3rd of February 2015 10:58:03 AM
Old 02-03-2015
Sendmail Error

Hello,

we have a mailserver named vision.mailhost.com 192.168.10.10 ( solaris 10)
We have an test server named visionway 192.168.10.5 ( solaris 10)

we want to run a cron job on test server and send an email if the cronjob fails

Question is how does the test server sendmail know the information of the mailserver.

The error we get when we check the log is message is Queued....

after we modified the /etc/hosts file it has an entry
192.168.10.10 vision.mailhost.com mailhost
The mail started working but how does it knew the information of the mailserver it has to be defined somewhere in sendmail correct ? or does the sendmail checks the entry in /etc/hosts and sends the mail to each of the server mentioned in /etc/host ?

we were checking the sendmail.cf
the DS parameter is empty
 

10 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

sendmail error :-(

Hi all, My problem is on : SunOS "MY_HOSTNAME" 5.7 Generic_106541-14 sun4u sparc SUNW,Ultra-60 I get the following message on the console login screen: sendmail: MAA 23665: SYSERR: putoutmsg (NO-HOST): error on output channel sending "550 none...User unknown": I/O error. Does anyone... (11 Replies)
Discussion started by: guest100
11 Replies

2. UNIX for Dummies Questions & Answers

extracting sendmail: error

I'm a newbie trying to update an old sendmail 8.6 to 8.12.3 ftp'ed sendmail.org and got sendmail.8.12.3.tar.gz file size matches but when i: tar xvf sendmail.8.12.3.tar.gz i get: tar: directory checksum error tried getting others... ie. 8.12.2... ftp'ed using binary and saved in... (1 Reply)
Discussion started by: sphiengollie
1 Replies

3. UNIX for Dummies Questions & Answers

Sendmail error

I have faced the following error : Feb 8 11:56:10 test sendmail: unable to qualify my own domain name (test) -- using short name I searched the forum and tested the required in the posts , but it doesn't work ... I have changed the IP and local host in /etc/hosts to be as follows : ... (1 Reply)
Discussion started by: atiato
1 Replies

4. UNIX for Advanced & Expert Users

Whe trying to start sendmail i getting following error

Hi expert , When i trying to start sendmail i getting the following error : pls help me # ./sendmail start # 451 4.0.0 /etc/mail/sendmail.cf: line 77: fileclass: cannot open /etc/mail/local-host-names: World writable directory 451 4.0.0 /etc/mail/sendmail.cf: line 472: fileclass: cannot... (6 Replies)
Discussion started by: saisivakumar
6 Replies

5. UNIX for Advanced & Expert Users

Too many hops error in sendmail

I am running SCO openserver 6 with sendmail as my mta I have a customer that sends me mail and occasionally some of them get bounced by my machine with a too many hops error. the header shows that it hops around their servers several times before getting to me and I know this is something that they... (3 Replies)
Discussion started by: garycrow
3 Replies

6. UNIX for Dummies Questions & Answers

getting some error periodically - sendmail

Hi all, When ever i open unix, periodically after every 3 minutes(approximately) i get the below error. "Dec 29 23:56:01 "domain name" sendmail: unable to qualify my own domain name ("domain name") -- using short name". This is interrupting me while writing a program. Please... (2 Replies)
Discussion started by: rakeshbharadwaj
2 Replies

7. Solaris

Sendmail error delaying relay

When I try to send mail, sendmail delays a lot. After monitoring syslog, I noticed that sendmail starts with this first message... waits a minute and gives the second message... waits another minute and then sends off the email. How do I correct this in sendmail or completly disable it. I'm sending... (0 Replies)
Discussion started by: adelsin
0 Replies

8. AIX

sendmail error aix 5.2

Hi, i'm having this error in my aix development server... i dont know what to do, anyone can helpme out with this??? I'll be so gratefull. ---- start of message Message from syslogd@aixdes1 at Mon Aug 9 08:36:03 2010 ... aixdes1 mail:crit sendmail: My unqualified host name (aixdes1)... (4 Replies)
Discussion started by: fdeivis
4 Replies

9. Red Hat

sendmail error

Hi, Need help here in sendmail error encountered # tail /var/log/maillog Aug 18 16:36:01 dot-123-my-server sendmail: q7IKa1GJ001123: to=<munin@dot-123-my-server>, ctladdr=<munin@dot-123-my-server> (101/102), delay=00:00:00, xdelay=00:00:00, mailer=local, pri=30898, dsn=2.0.0, stat=Sent Aug... (2 Replies)
Discussion started by: edwin rosales
2 Replies

10. UNIX for Dummies Questions & Answers

Sendmail error message

Hi i am having a probleme with my sendmail server. using it as a mta to send out email. keem on getting this error message back. ----- The following addresses had permanent fatal errors ----- <XXX@XXXX.co.za> (reason: 554 Denied (Mode: normal)) ----- Transcript of session... (1 Reply)
Discussion started by: sakie
1 Replies
mxallowd(1)							   User Manuals 						       mxallowd(1)

NAME
mxallowd - dynamically whitelist your Mail eXchanger SYNOPSIS
mxallowd [-d] [-c configfile] [-t whitelist-time] [-p pflog-interface] [-l pcap-filter] [-F] [-s] [-q] [-p] -f fake-mailserver -r real- mailserver -n queue-num DESCRIPTION
mxallowd is a daemon which uses libnetfilter_queue (on Linux) or pf and pflog (on BSD) to allow (or deny) connections to a mailserver (or similar application) if the remote host hasn't connected to a fake daemon before. This is an improved version of the so-called nolisting (see http://www.nolisting.org/). The assumption is that spammers are not using RFC 2821-compatible SMTP-clients and are sending fire-and-forget spam (directly to the first or second MX-entry without retrying on error). This direct access is blocked with mxallowd, you'll only get a connection if you retry. NOTE: It is highly recommended to install nscd (nameserver caching daemon) or a similar software in order to speed-up DNS lookups. Since version 1.3, DNS lookups are done in a thread (so they don't block the main process), however, on very-high-traffic-sites, mxallowd may show significantly better overall performance in combination with nscd. OPTIONS
-b, --no-rdns-whitelist Disable whitelisting all IP-addresses that have the same RDNS as the connecting one (necessary for google mail) -c, --config Specifies an alternative configuration file (instead of /etc/mxallowd.conf) -t, --whitelist-time Specify the amount of time (in seconds) until an IP-address will be removed from the whitelist -s, --stdout Log to stdout, not to syslog -q, --quiet Don't log anything but errors. -f, --fake-mailserver Specify which IP-address the fake mailserver has (connecting to it will whitelist you for the real mailserver) -r, --real-mailserver Specify which IP-address the real mailserver has -F, --foreground Do not fork into background, stay on console -n, --queue-num (only available when compiled for netfilter_queue) Specify the queue number which will be used for the netfilter_queue-link. This has to be the same which is specified in the ipta- bles-rule and it has to be specified, there is no default. -p, --pflog-interface (only available when compiled for pf) Specify the pflog(4) interface which you configured in pf(4). The default is pflog0. Also see the pcap-filter-option if you use an interface which does not only get smtp-traffic. -l, --pcap-filter (only available when compiled for pf) Specify the filter for pcap. The default is "port 25". See tcpdump(8) for more information on the filters. FILES
/etc/mxallowd.conf System-wide configuration file. Use the long options without the beginning two dashes. For example: stdout fake-mailserver 192.168.1.3 fake-mailserver 192.168.1.4 real-mailserver 192.168.1.5 queue-num 23 EXAMPLES FOR NETFILTER
The machine has two IP-addresses. The mailserver only listens on 192.168.1.4, the nameserver returns the mx-records mx1.domain.com (192.168.1.3) with priority 5 and mx2.domain.com (192.168.1.4) with priority 10. # modprobe nfnetlink_queue # iptables -A INPUT -p tcp --dport 25 -m state --state NEW -j NFQUEUE --queue-num 23 # mxallowd -s -F -f 192.168.1.3 -r 192.168.1.4 -n 23 Then open a separate terminal and connect via telnet on your real mailserver. You'll see the connection attempt being dropped. Now connect to the fake mailserver and watch mxallowd's output. Afterwards, connect to the real mailserver to verify your mailserver is still working. EXAMPLES FOR PF
The machine has two IP-addresses. The mailserver only listens on 192.168.1.4, the nameserver returns the mx-records mx1.domain.com (192.168.1.3) with priority 5 and mx2.domain.com (192.168.1.4) with priority 10. Create a pf.conf like this: table <mx-white> persist real_mailserver="192.168.1.4" fake_mailserver="192.168.1.3" real_mailserver6="2001:dead:beef::1" fake_mailserver6="2001:dead:beef::2" pass in quick log on fxp0 proto tcp from <mx-white> to $real_mailserver port smtp pass in quick log on fxp0 inet6 proto tcp from <mx-white> to $real_mailserver6 port smtp block in log on fxp0 proto tcp to { $fake_mailserver $real_mailserver } port smtp block in log on fxp0 inet6 proto tcp to { $fake_mailserver6 $real_mailserver6 } port smtp Afterwards, load it and start mxallowd using the following commands: # pfctl -f /etc/pf.conf # mxallowd -s -F -f 192.168.1.3 -r 192.168.1.4 Then open a separate terminal and connect via telnet on your real mailserver. You'll see the connection attempt being dropped. Now connect to the fake mailserver and watch mxallowd's output. Afterwards, connect to the real mailserver to verify your mailserver is still working. The ruleset for pf is actually longer because pf does more than netfilter on linux -- netfilter passes the packets and lets mxallowd decide whether to drop/accept whilst pf blocks/passes before even "passing" to mxallowd. SEE ALSO
iptables(8), pf(4), pflog(4), tcpdump(8) AUTHOR
Michael Stapelberg <michael+mxallowd at stapelberg dot de> Linux MARCH 2012 mxallowd(1)
All times are GMT -4. The time now is 03:06 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy