Re: [exim] IPV6 error in exim -> now "unrouteable"

Pàgina inicial
Delete this message
Reply to this message
Autor: Heiko Schlittermann
Data:  
A: exim-users
Assumpte: Re: [exim] IPV6 error in exim -> now "unrouteable"
Privacy <axelle.apvrille@???> (Mo 14 Apr 2014 22:46:29 CEST):
> Hi Heiko & list,
>
> Thanks for the tip.
>
> On 13/04/2014 15:07, Heiko Schlittermann wrote:
> > Privacy <axelle.apvrille@???> (Sa 12 Apr 2014 20:46:16 CEST):
> >> Hello,
> >>
> >> I am trying to set up exim4 to use my gmail account. But mail is queued
> >> and is never sent because the log says:
> > …
> >> In /etc/exim4/update-exim4.conf.conf, I have at the end:
> >>
> >> disable_ipv6='true'
> >> dns_ipv4_lookup='*'


I do not know the Debian way of Exim configuration. Are these settings
already there, or did you invent these options?

> >     exim -bP disable_ipv6
> This tells me:
> no_disable_ipv6
> which I guess is not good :(


> However, I did a few things:
> - I had both a /etc/exim4/conf.d directory (split config) and a
> exim4.conf.template (unique file). I removed the conf.d directory to be
> sure it'd read the unique config file.
>
> - The config file is named 'exim4.conf.template'. Is that really
> correct? In doubt, I duplicated it to exim4.conf.


Ooops. Under Debian Exim tries to read

    /etc/exim4/exim4.conf
    /var/lib/…/*autogenerated*  (I do not exactly remember that name)


in that order. The first match wins.
If you copied the exim4.conf.template to exim4.conf you may get
unexpected results. I think, the exim4.conf.template isn't a complete
and correct Exim configuration. But maybe it's a syntactically correct,
but incomplete configuration. (/dev/null is a correct but incomplete
(depending on the purpose) Exim configuration too.)

Using "exim4 -bV" tells you the configuration file used.

> + I have a update-exim4.conf.conf file.
> Now, restarting exim4 I have in the logs:
> 2014-04-14 22:43:43 exim 4.80 daemon started: pid=32736, -q30m,
> listening for SMTP on port 25 (IPv4)
> 2014-04-14 22:43:43 Start queue run: pid=32741
>
> 2014-04-14 22:44:45 Start queue run: pid=300 -qff
> 2014-04-14 22:44:45 1WZ4qE-0005vb-JJ Unfrozen by forced delivery
> 2014-04-14 22:44:45 1WZ4qE-0005vb-JJ ** MYEMAIL@???: Unrouteable
> address
> 2014-04-14 22:44:45 1WZ4qE-0005vb-JJ Frozen (delivery error message)
>
> So, this looks different, doesn'it it? Why is it "unrouteable" ?


Probabably because of …. see above, inapprobiate/incomplete
configuration.

    Best regards from Dresden/Germany
    Viele Grüße aus Dresden
    Heiko Schlittermann
-- 
 SCHLITTERMANN.de ---------------------------- internet & unix support -
 Heiko Schlittermann, Dipl.-Ing. (TU) - {fon,fax}: +49.351.802998{1,3} -
 gnupg encrypted messages are welcome --------------- key ID: 7CBF764A -
 gnupg fingerprint: 9288 F17D BBF9 9625 5ABC  285C 26A9 687E 7CBF 764A -
(gnupg fingerprint: 3061 CFBF 2D88 F034 E8D2  7E92 EE4E AC98 48D0 359B)-