Thanks for the comprehensive report. What do your logs say with regard to 1Wcool-0001JR-Kw?
Are you positive that your DNS was OK at the time of this incident and that your exim was thus able to determine that devilserver.deviltechnologies.com is the local host? Greetings Marc On Wed, Apr 23, 2014 at 10:38:30AM +0200, Diego Guella wrote: > From: Diego Guella <[email protected]> > Subject: Bug#697612: exim4-daemon-light: "MAIN_LOCAL_DOMAINS=@:localhost" > seems not to respect "@" > To: [email protected] > Cc: Diego Guella <[email protected]>, [email protected] > Reply-To: Diego Guella <[email protected]>, > [email protected] > Date: Wed, 23 Apr 2014 10:38:30 +0200 > X-Debian-PR-Package: exim4-daemon-light > X-Mailer: Microsoft Outlook Express 6.00.2900.5931 > List-Id: Reach the exim4 maintainers > <pkg-exim4-maintainers.lists.alioth.debian.org> > X-Spam-Score: (--) -2.6 > X-Spam-Report: torres.zugschlus.de Content analysis details: (-2.6 > points, 5.0 required) pts rule name description ---- > ---------------------- ------------------------------------------- -0.7 > RP_MATCHES_RCVD Envelope sender domain matches handover relay > domain -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% > [score: 0.0000] > > Package: exim4-daemon-light > Version: 4.72-6+squeeze3 > > Same problem here. > The bad news is, this happened from today, with no configuration > changes (that I know of) on the server. > The server is in production. > > Local mails to root@localhost and user@localhost are delivered > locally without problems, but local mails to > [email protected] does get sent to the > smarthost. > The server configuration is some years old, and it worked perfectly > until yesterday! (I get a daily mail from mdadm at 06:25 local time) > Today, I found that the mail was bounced and bounced again from my > server and the smarthost, and then my server stopped trying, sending > this error email message: > ----- > Message 1Wcool-0001JR-Kw has been frozen (delivery error message). > The sender is <>. > > The following address(es) have yet to be delivered: > [email protected]: Too many "Received" > headers - suspected mail loop > ----- > > update-exim4.conf.conf: > ----- > dc_eximconfig_configtype='smarthost' > dc_other_hostnames='' > dc_local_interfaces='' > dc_readhost='' > dc_relay_domains='' > dc_minimaldns='false' > dc_relay_nets='' > dc_smarthost='vps26197.ovh.net' > CFILEMODE='644' > dc_use_split_config='false' > dc_hide_mailname='false' > dc_mailname_in_oh='true' > dc_localdelivery='maildir_home' > ----- > > Some other information: > ----- > root@devilserver:/etc/exim4# uname -n > devilserver > root@devilserver:/etc/exim4# hostname > devilserver > root@devilserver:/etc/exim4# hostname -f > devilserver.deviltechnologies.com > root@devilserver:/etc/exim4# grep -v ^# /etc/hosts > 127.0.0.1 localhost > 192.168.200.249 devilserver.deviltechnologies.com devilserver > > ::1 ip6-localhost ip6-loopback > fe00::0 ip6-localnet > ff00::0 ip6-mcastprefix > ff02::1 ip6-allnodes > ff02::2 ip6-allrouters > ----- > > I have BIND installed, version 1:9.7.3.dfsg-1~squeeze11 > > I tried Osamu Aoki's workaround > (dc_other_hostnames='devilserver.deviltechnologies.com') and it > fixes the problem for me, too. > > I assume there is some deeply hidden misconfiguration of something > other than exim on my server, or in my network. > Again, this setup has worked fine for some years. > I have a backup of the server configuration of some months ago, and > I can double-check for changes in the configuration files. > Do somebody know where can I look at? > > > Thanks, > Diego > > -- > Pkg-exim4-maintainers mailing list > [email protected] > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-exim4-maintainers -- ----------------------------------------------------------------------------- Marc Haber | "I don't trust Computers. They | Mailadresse im Header Mannheim, Germany | lose things." Winona Ryder | Fon: *49 621 31958061 Nordisch by Nature | How to make an American Quilt | Fax: *49 621 31958062 -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
