Common error for system administrator

Case 1:

getng sch error
Dec 30 05:10:02 server124 postfix/cleanup[10299]: E7D76F62F3C: milter-reject: END-OF-MESSAGE from mail.zovemenitt.net[173.205.183.59]: 5.7.1 sender domain does not exist; from=<contact@mail.zovemenitt.net> to=<palmarka999@comcast.net> proto=SMTP helo=<17260|ely01>
M part of comcast team



solution:

step 1: IN server 124

cat /etc/dkim-filter.conf


step 2: if any domain is there remove that one

Domain #add all your domains here and seperate them with comma



step 3:

service dkim-milter stop

--------------------------------------------------------------------------------------------------------------- next mailler issue 2


case 2;


PHP Warning: fsockopen(): unable to connect to 173.205.182.249:2525 (Connection refused) in /var/www/cgi-bin/test11.php on line 72
!! Error, can't connect to the server 173.205.182.249 on the port 2525groups.cratchankinal.com
|173.205.182.249



ans

pmta is 2525
postfix 2505



change port no in the script 2525 to 2505

case 3

abuse@domain not receiving mails

ans :

netstat –nlp | grep 0.0.0.0:25

check whether sendmail is running on port 25 or not

Check also domain  and user entry is their in the following files

1.make entry in /etc/hosts

2.make entry in /etc/mail/local-hostnames

3.make entry in /etc/mail/virtusertable

4.service sendmail restart

case 4

error:

connect to mx2.hotmail.com[65.55.92.152]: Connection timed out (port 25)

ans : set is down

Case 5

Error:

warning: connect to Milter service inet:localhost:20209: Connection refused

ans:

service dkim-milter restart

service dk-milter restart

case 6 :

Mail not coming for user admin

ans:

1.make entry in /etc/hosts

2.make entry in /etc/mail/local-hostnames

3.make entry in /etc/mail/virtusertable

4.service sendmail restart

Case 7:

Redirection Issue

Check in httpd.conf for redirection

Domain resolving or not

Rdns is working or not

Replace domain name of sl3 in httpd.conf with server ip address

Service httpd restart

Case 8:

Issue: Error, can't connect to the server on the port

Solution: cd /etc;ls -d postfix-[0-9]* | cat | while read line; do /usr/sbin/postfix -c /etc/$line start; done

Case 9:

Issue :

Error 554 while sending mail.

Soln.: IP is permanently blocked for sending mails

Case 10:

Issue: while sending mail through this we get this error connect to relay.verizon.net[206.46.232.11]:25: Connection timed out

Solution: IPset not configured on that server or wait for some time to check since isp is not receiving mails from that domain

Case 11:

Issue: status=deferred (delivery temporarily suspended: Host or domain name not found. Name service error for name=verizon.net type=MX: Host not found, try again)

Solution: check /etc/hosts

            Service named restart

            Dig the domain name

            Wait for sometime

Case 12 :

Issue: Service pmta restart and after everything is ok but when u run this command Service pmta statusà output is service is stopped .

Solution:  Look for space on the disk , run df –h

And try to delete unwanted files and than restart pmta service .

Case 13 :

Issue : Mar 31 07:07:21 server4563 postfix-209.16.147.252/master[4434]: warning: service "2505" (2505) has reached its process limit "130": new clients may experience noticeable delays

Solution : check this variable in main.cf

            The smtpd_recipient_limit parameter (default: 1000) controls how many recipients the Postfix smtpd(8) server will take per delivery. The default limit is more than any reasonable SMTP client would send. The limit exists to protect the local mail system against a run-away client.

Case 14:

Issue: Timed out connecting from groups.boardmaintenance.net (64.16.202.97) to alt2.gmail-smtp-in.l.google.com (74.125.79.27))

Solution:

Check PMTA config for the respected Domain.

Case 15 :

 Issue : During mail sending using postfix and if you get this error dsn=4.4.3 and status=deffered

Solution: problem from ISP side wait for some time. As MX records are working .

           Check /etc/resolv.conf

Please check that the dns servers in /etc/resolv.conf are working. Be aware that mydns is not able to reslolve external domains, so you will have to enter there a dns server that is capable of resolving external domains too.

Case 16 : Timed out while connecting from sales.decisiveo.com (173.45.13.57) to h.mx.mail.yahoo.com (66.94.236.34)

Solution:

How to fix the problem (sortof)

Yahoo gives some basic "do these to fix the problem ":

• Remove email addresses that bounce
• Examine your retry policies
• Pay attention to the responses from our SMTP servers
• Don't send unsolicited email (duh!)
• Provide a method of unsubscribing
• Ensure your mail servers are not open relays.

Also install DomainKeys to help fix the problem

Dig a little deeper and you will find that you should install DomainKeys (you should have already installed SPF records so that you can send to AOL accounts) to sign your emails from a specific domain. However, even once this is done, you will still get some 451 errors.
The long and short of it is that you get what you pay for...

• Yahoo is not communicating with administrators even after they submit multiple request forms.
• Yahoo is not delivering messages even though they send the response back that the "message was temporarily deferred" (Which sounds like it is just waiting to send the message, but will get to it eventually).
• In an attempt to block spammers, Yahoo is blocking an extremely high number of "good" emails.

Service dkim-milter restart

Check also whether set is alive or not

Case 17 : warning: master_wakeup_timer_event: service pickup(public/pickup): No such file or directory

                fatal: open lock file pid/inet.2505: cannot create file exclusively: No such file or directory

Solution:          chmod 777 /var/mail/

Postfix reload command

Case 18 : /etc/init.d/httpd restart
Stopping httpd: [FAILED]
Starting httpd: (98)Address already in use: make_sock: could not bind to address [::]:80
(98)Address already in use: make_sock: could not bind to address 0.0.0.0:80
no listening sockets available, shutting down

IF the above error occurs then kill all the httpd processes and then restart the service. As Some other process is already running at port number 80. Use netstat -ltnp | grep ':80' to get the process name and pid.

Solution:

netstat -lnp | grep :80
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 1336/httpd

killall -9 httpd
killall -9 wget
kill -9 1336

service httpd restart.