Topic: cron using incorrect root email address

[ked]

Hello all,

I'm seeing a strange email address being used by cron for its automated mailing. It is attempting to send emails to root@mydomain.mydomain rather than root@mydomain. Of course the email bounces several times until the qmail-send program sends it to postmaster@mydomain, which is finally forwarded onto my external email address.

Other email seems fine. Have I made a configuration error?

A typical email trail looks like:

To: postmaster@mydomain

Hi. This is the qmail-send program at mydomain.
I tried to deliver a bounce message to this address, but the bounce bounced!

<anonymous@mydomain.mydomain>:
Sorry, I couldn't find any host named mydomain.mydomain. (#5.1.2)

--- Below this line is the original bounce.

Return-Path: <>
Received: (qmail 4081 invoked for bounce); 3 Mar 2008 17:06:32 -0000
Date: 3 Mar 2008 17:06:32 -0000
From: MAILER-DAEMON@mydomain
To: anonymous@mydomain.mydomain
Subject: failure notice

Hi. This is the qmail-send program at mydomain.
I'm afraid I wasn't able to deliver your message to the following addresses.
This is a permanent error; I've given up. Sorry it didn't work out.

<root@mydomain.mydomain>:
Sorry, I couldn't find any host named mydomain.mydomain. (#5.1.2)

--- Below this line is a copy of the message.

Return-Path: <anonymous@mydomain.mydomain>
Received: (qmail 4079 invoked by uid 0); 3 Mar 2008 17:06:32 -0000
Date: 3 Mar 2008 17:02:59 -0000
Message-ID: <20080303170259.3281.qmail@mydomain>
From: root@mydomain.mydomain (Cron Daemon)
To: root@mydomain.mydomain
Subject: Cron <root@myserver> run-parts /etc/cron.daily
X-Cron-Env: <SHELL=/bin/bash>
X-Cron-Env: <PATH=/sbin:/bin:/usr/sbin:/usr/bin>
X-Cron-Env: <MAILTO=root>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>
...

[cactus]

Report issues to the bugtracker please.

[raem]

ked

Better still, search the bugtracker (and forums) as I think that may have been answered previously.
I seem to think it may be related to having an unusual style of domain name.
Just rename it in a standard fashion ie mydomain.com and see if it then works OK.

[ked]

Thanks for your replies.

Cactus, I hesitated to post it as a bug as I assumed it was a configuration issue caused by my incompetence rather than being a bug in SME. Is the bug tracker appropriate for such issues?

Ray, I did do a search on a variety of terms before posting, but your comment helped me refine it further and come up with the issue previously posted on the forums.

Cheers.

[raem]

ked

....your comment helped me ..... come up with the issue previously posted on the forums.

Please provide a link for future reference.
Was that your issue, and did the answer resolve your issue ?

[ked]

It appears almost tangential to my problem, but seeing the double period in the error message in this post (http://forums.contribs.org/index.php?topic=31158.0) in conjunction with your suggested action to change the domain name made me realise that primary domain name I had set was poorly formed.

It was styled as mydomain and changing it to mydomain.com.au has fixed the issue. Further testing showed that using any domain name that contains a period fixes the issue.

Cheers,

Ken