no more mail

Place to discuss Fedora and/or Red Hat
User avatar
Basher52
guru
guru
Posts: 918
Joined: Wed Oct 22, 2003 5:57 am
Location: .SE

no more mail

Post by Basher52 » Thu Aug 14, 2008 12:13 am

For a couple of days now I don't get those mail that usually comes every night. All cron jobs are still running OK though.
I use 2.6.24.5-85.fc8 and I even restarted sendmail but no luck.
where can I find out what's going on? I can't come up with anything :(

User avatar
Void Main
Site Admin
Site Admin
Posts: 5716
Joined: Wed Jan 08, 2003 5:24 am
Location: Tuxville, USA
Contact:

Post by Void Main » Thu Aug 14, 2008 7:59 am

Look through your /var/log/maillog which should tell you exactly what is happening. Also see if you have outgoing mail queued up (# mailq).

User avatar
Basher52
guru
guru
Posts: 918
Joined: Wed Oct 22, 2003 5:57 am
Location: .SE

Post by Basher52 » Sat Aug 16, 2008 3:54 pm

just this day it started to work again... sooo wierd

the log is here:

Code: Select all

Aug 16 22:57:08 ftp sendmail[4722]: m7E24E2B029811: to=<root@ftp.basher52.net>, delay=2+18:52:54, xdelay=00:00:00, mailer=esmtp, pri=6255285, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
Aug 16 22:57:08 ftp sendmail[4722]: m7G6v7U9002679: to=<root@ftp.basher52.net>, delay=13:59:53, xdelay=00:00:00, mailer=esmtp, pri=7534390, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
Aug 16 22:57:08 ftp sendmail[4722]: m7D6w5tJ026447: to=<root@ftp.basher52.net>, delay=3+13:59:02, xdelay=00:00:00, mailer=esmtp, pri=7873903, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
Aug 16 22:57:08 ftp sendmail[4722]: m7G2v7U9002229: to=<root@ftp.basher52.net>, delay=17:59:58, xdelay=00:00:00, mailer=esmtp, pri=7892446, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
Aug 16 22:57:08 ftp sendmail[4722]: m7G2UcU7002180: to=<root@ftp.basher52.net>, delay=18:26:30, xdelay=00:00:00, mailer=esmtp, pri=8073167, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
Aug 16 22:57:08 ftp sendmail[4722]: m7D24FF4016644: to=<root@ftp.basher52.net>, delay=3+18:52:53, xdelay=00:00:00, mailer=esmtp, pri=8412675, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
Aug 16 22:57:08 ftp sendmail[4722]: m7F6v7C7022942: to=<root@ftp.basher52.net>, delay=1+13:59:58, xdelay=00:00:00, mailer=esmtp, pri=9691693, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
Aug 16 22:57:08 ftp sendmail[4722]: m7C6w5LQ012110: to=<root@ftp.basher52.net>, delay=4+13:59:02, xdelay=00:00:00, mailer=esmtp, pri=10037887, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
Aug 16 22:57:08 ftp sendmail[4722]: m7F2v7C7022295: to=<root@ftp.basher52.net>, delay=1+18:00:00, xdelay=00:00:00, mailer=esmtp, pri=10061971, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
Aug 16 22:57:08 ftp sendmail[4722]: m7F2Y1C5022254: to=<root@ftp.basher52.net>, delay=1+18:23:07, xdelay=00:00:00, mailer=esmtp, pri=10230470, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
Aug 16 22:57:08 ftp sendmail[4722]: m7C24EAR002676: to=<root@ftp.basher52.net>, delay=4+18:52:54, xdelay=00:00:00, mailer=esmtp, pri=10666659, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
Aug 16 22:57:08 ftp sendmail[4722]: m7E6w5tl009077: to=<root@ftp.basher52.net>, delay=2+13:59:02, xdelay=00:00:00, mailer=esmtp, pri=11976836, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
Aug 16 22:57:08 ftp sendmail[4722]: m7E2a1tj008420: to=<root@ftp.basher52.net>, delay=2+18:21:07, xdelay=00:00:00, mailer=esmtp, pri=12515613, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
Aug 16 22:57:08 ftp sendmail[4722]: m7D6w5tK026447: to=<root@ftp.basher52.net>, delay=3+13:59:02, xdelay=00:00:00, mailer=esmtp, pri=14110331, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
Aug 16 22:57:08 ftp sendmail[4722]: m7D2VCtI025190: to=<root@ftp.basher52.net>, delay=3+18:25:56, xdelay=00:00:00, mailer=esmtp, pri=14649108, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
Aug 16 22:57:08 ftp sendmail[4722]: m7C6w5LR012110: to=<root@ftp.basher52.net>, delay=4+13:59:02, xdelay=00:00:00, mailer=esmtp, pri=16274590, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
Aug 16 22:57:08 ftp sendmail[4722]: m7C2UfZC011229: to=<root@ftp.basher52.net>, delay=4+18:26:27, xdelay=00:00:00, mailer=esmtp, pri=16813367, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
and in all this i can't see anything wrong

another thing, why all these logs when the "thing" are set to send the bkup-mail at 4 AM... but I guess I don't know what usually happens on a server... still :(

User avatar
Void Main
Site Admin
Site Admin
Posts: 5716
Joined: Wed Jan 08, 2003 5:24 am
Location: Tuxville, USA
Contact:

Post by Void Main » Sat Aug 16, 2008 10:25 pm

You don't see those "no route to host" messages? For whatever reason port 25 on the mail server was not reachable and it queued the messages.

User avatar
Basher52
guru
guru
Posts: 918
Joined: Wed Oct 22, 2003 5:57 am
Location: .SE

Post by Basher52 » Mon Aug 18, 2008 2:34 am

well that I see but I just figured that's because the domain name is not registered anywhere.
I now saw that it's working again, but haven't done that the last 6 days.
wierd.. I haven't done anything other than rebooting after new patches
ah well... seems it's working now so.

thx man

User avatar
Void Main
Site Admin
Site Admin
Posts: 5716
Joined: Wed Jan 08, 2003 5:24 am
Location: Tuxville, USA
Contact:

Post by Void Main » Mon Aug 18, 2008 8:14 am

My guess is that you are no longer seeing those "no route to host" messages. That definitely indicates a problem.

User avatar
Basher52
guru
guru
Posts: 918
Joined: Wed Oct 22, 2003 5:57 am
Location: .SE

Post by Basher52 » Mon Aug 18, 2008 11:37 pm

They just poped up again
I gotta ask, to WHAT is there no route?
I'm mailing my own account as a bkup of files I got here, is it that one that I have no route to?
it can't be my "internal" mail server or?
this name: basher52.servehttp.com is just something I set a long time ago
when doing a web server test, but the name really has no baring in "real" life, if you know what I mean.

UPDATE: I forgot to tell that sending the bkup files do work as they get through to the account I'm sending it to.

User avatar
Void Main
Site Admin
Site Admin
Posts: 5716
Joined: Wed Jan 08, 2003 5:24 am
Location: Tuxville, USA
Contact:

Post by Void Main » Tue Aug 19, 2008 9:19 am

It means it can't reach the destination MX server's port 25. I have seen similar things when I lose network connectivity (cable/dsl down or my lone mail server is down/inaccessible) for a while and mail gets backed up in the queue. Sometimes when connectivity is returned I have to restart sendmail to get it going again. It was always on not so important machines in the past so I never looked into how to solve it. I'll bet there is an easy fix. Does that sound like the issue you are experiencing?

User avatar
Basher52
guru
guru
Posts: 918
Joined: Wed Oct 22, 2003 5:57 am
Location: .SE

Post by Basher52 » Tue Aug 19, 2008 11:36 pm

yeah kinda, but you say that it's the destination machine I can't connect to,
but the bkup files get there every day at 4:08 AM so in this case it doesn't feel like the exact same problem, although the server is just more like a test site.

I also looked in the maillog files before this ever happened(back in January) and even those have this kind of problem, timeout, no route etc.

I just tried to open 'basher52.servehttp.com' and some page came up, but it's not mine that's for sure. It's a searchportal thing.
I wonder... how can I remove that name 'basher52.servehttp.com' from my server, back to localhost or something so it won't do these checks as I think all timeouts and routing problem is to this name, just look at it:

From January

Code: Select all

Jan 20 15:27:51 ftp sendmail[3183]: m0I34BbG016650: to=<root@ftp.basher52.net>, delay=2+11:23:40, xdelay=00:00:00, mailer=esmtp, pri=5540057, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: Connection timed out with basher52.servehttp.com.
Jan 20 15:27:51 ftp sendmail[3183]: m0J7PnAX005108: to=<root@ftp.basher52.net>, delay=1+07:00:01, xdelay=00:00:00, mailer=esmtp, pri=5992423, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: Connection timed out with basher52.servehttp.com.
Jan 20 15:27:51 ftp sendmail[3183]: m0J3PnAY004641: to=<root@ftp.basher52.net>, delay=1+11:00:01, xdelay=00:00:00, mailer=esmtp, pri=6398184, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: Connection timed out with basher52.servehttp.com.
Jan 20 15:27:51 ftp sendmail[3183]: m0J3DkAV004620: to=<root@ftp.basher52.net>, delay=1+11:14:05, xdelay=00:00:00, mailer=esmtp, pri=6531223, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: Connection timed out with basher52.servehttp.com.
Jan 20 15:27:51 ftp sendmail[3183]: m0H7PndH012091: to=<root@ftp.basher52.net>, delay=3+06:57:59, xdelay=00:00:00, mailer=esmtp, pri=7158362, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: Connection timed out with basher52.servehttp.com.
Jan 20 15:27:51 ftp sendmail[3183]: m0H3PndI011603: to=<root@ftp.basher52.net>, delay=3+11:00:01, xdelay=00:00:00, mailer=esmtp, pri=7519918, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: Connection timed out with basher52.servehttp.com.
Now

Code: Select all

Aug 20 06:28:52 ftp sendmail[1219]: m7H2XLII027212: to=<root@ftp.basher52.net>, delay=3+01:55:31, xdelay=00:00:00, mailer=esmtp, pri=13117909, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
Aug 20 06:28:52 ftp sendmail[1219]: m7G6v7U9002679: to=<root@ftp.basher52.net>, delay=3+21:31:37, xdelay=00:00:00, mailer=esmtp, pri=14734390, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
Aug 20 06:28:52 ftp sendmail[1219]: m7G2v7U9002229: to=<root@ftp.basher52.net>, delay=4+01:31:42, xdelay=00:00:00, mailer=esmtp, pri=15092446, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
Aug 20 06:28:52 ftp sendmail[1219]: m7G2UcU7002180: to=<root@ftp.basher52.net>, delay=4+01:58:14, xdelay=00:00:00, mailer=esmtp, pri=15273167, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
Aug 20 06:28:52 ftp sendmail[1219]: m7F6v7C7022942: to=<root@ftp.basher52.net>, delay=4+21:31:42, xdelay=00:00:00, mailer=esmtp, pri=16891693, relay=basher52.servehttp.com., dsn=4.0.0, stat=Deferred: basher52.servehttp.com.: No route to host
I'm also thinking of that the route problem started some time when the web page(searchportal) showed up on this name.

Copperhead
scripter
scripter
Posts: 83
Joined: Wed May 14, 2003 1:12 am
Location: Los Angeles, CA, USA

Post by Copperhead » Wed Aug 20, 2008 7:03 am

Just edit /etc/hostname to change your hostname to whatever you want.

I believe you cane so it as root from the command line as well

$ hostname <new-hostname>

User avatar
Basher52
guru
guru
Posts: 918
Joined: Wed Oct 22, 2003 5:57 am
Location: .SE

Post by Basher52 » Wed Aug 20, 2008 8:31 am

There is no etc/hostname file.
I do have an etc/hosts if that's what you mean
and it looks like this:

Code: Select all

# Do not remove the following line, or various programs
# that require network functionality will fail.
::1     basher52.servehttp.com  ftp     localhost.localdomain   localhost
and after I did the 'hostname localhost.localdomain' nothing happened in this file though.

Copperhead
scripter
scripter
Posts: 83
Joined: Wed May 14, 2003 1:12 am
Location: Los Angeles, CA, USA

Post by Copperhead » Fri Aug 22, 2008 4:22 am

Ooops! Sorry basher. /etc/hostname is a Debian specific file. Wrong forum :D

You need to edit /etc/hosts and /etc/sysconfig/network, and then restart network services.

Alternatively, you can do this (as root), and not bother restarting:

$ echo "localhost" > /proc/system/kernel/hostname

You can then logout and log back in and your prompt should change to your new hostname.

Of course, you can check it with :

$ echo $HOSTNAME

User avatar
Basher52
guru
guru
Posts: 918
Joined: Wed Oct 22, 2003 5:57 am
Location: .SE

Post by Basher52 » Fri Aug 22, 2008 7:36 pm

thx.. but i dont think its the ftp.basher52.net thing its hang-ing on
it gotta be the other one as i said above
(but who am i to argue with you dudes lol)

User avatar
Void Main
Site Admin
Site Admin
Posts: 5716
Joined: Wed Jan 08, 2003 5:24 am
Location: Tuxville, USA
Contact:

Post by Void Main » Sat Aug 23, 2008 7:28 am

Basher52 wrote:thx.. but i dont think its the ftp.basher52.net thing its hang-ing on
it gotta be the other one as i said above
(but who am i to argue with you dudes lol)
Actually I agree with you. It's the "destination" server that is the problem and somewhere you have that defined as "basher52.servehttp.com". At some point that server is not reachable (at least to port 25) which is causing the backup of mail.

User avatar
Basher52
guru
guru
Posts: 918
Joined: Wed Oct 22, 2003 5:57 am
Location: .SE

Post by Basher52 » Sat Aug 23, 2008 2:16 pm

Void Main wrote:
Basher52 wrote:...somewhere you have that defined as "basher52.servehttp.com". At some point that server is not reachable (at least to port 25) which is causing the backup of mail.
hmm...
the only thing I did back then was to name my server to try the DNS to work, but how can this one: diino.com be mistaken with this basher52.serverhttp.com?
ah well... how can i remove this then?

Post Reply