Hi,

Alvaro Lacerda <[email protected]> (Mo 03 Apr 2017 16:02:31 CEST):
> Hi All,
> 
> When I try to see if an email can be reached through the command 'exim -bt
> "[email protected]" ' I keep getting an error saying: "[email protected] cannot
> be resolved at this time: Temporary internal error"

Looks like mis-configuration.

> Whenever I try to send emails through "exim -v [email protected]" my messages
> just keep stuck in /var/spool/exim.in/input and it never goes anywhere as
> well.

Yes, if there is an mis-configuration, but not wrong enough to prevent
Exim from accepting the message, this is the expected behaviour.

    exipick

will show you your messages (the spool directory doesn't matter)

> When I check my logs in /var/spool/exim/log/ this is what I get for each
> log:
> 
>  Suggested action: use keep_environment.
(Unrelated here, but for completness: you should set keep_environment =
in your configuration.)

> 2017-04-03 09:44:10 exim 4.88 daemon started: pid=32236, no queue runs,
> listening for SMTP on port 465 (IPv6 and IPv4)

> 2017-04-03 09:44:14 exim 4.88 daemon started: pid=32249, -q1h, listening for
> SMTP on port 25 (IPv6 and IPv4)
> 2017-04-03 09:44:14 exim user lost privilege for using -C option

Do you start several instances of the Daemon? That's not the usual
setup. The last instance you start using -C …? For security reasons this
instance will run under some restrictions.

Normally you'd start one instance, listening on all ports (25, 465 in
your case)

> rejectlog:
> 
> 2017-03-30 03:19:02 H=localhost (postman1.cantell.com) [127.0.0.1] sender
> verify defer for <[email protected]>: Temporary internal error
> 2017-03-30 03:19:02 H=localhost (postman1.cantell.com) [127.0.0.1]
> X=TLSv1.2:ECDHE-RSA-AES256-SHA:256 CV=no F=<[email protected]>
> temporarily rejected RCPT <[email protected]>: unknown lookup type
> "mysql"

Search for "mysql" in your configuration. I think, you'll find something
like ${lookup mysql{….}}. To make this work, your Exim needs to be built
with mysql support.
    
    exim -bV

tells you what lookup types are supported. Some distros package
two different versions, a light and a heavy one. Did you build the Exim
from the sources? If so, you, you need to find MYSQL in the
Local/Makefile and enable it. If you have a distro package, check if
there is a package, supporting mysql.

Or, but probably not very likely, a simple configuration issue, syntax
error in defining a lookup. Try posting the output

    exim -bP config

*but check for passwords or similiar stuff*.


[deleted 28 lines disclaimer]

    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: F69376CE -
 ! key id 7CBF764A and 972EAC9F are revoked since 2015-01 ------------ -

Attachment: signature.asc
Description: PGP signature

-- 
## List details at https://lists.exim.org/mailman/listinfo/exim-users
## Exim details at http://www.exim.org/
## Please use the Wiki with this list - http://wiki.exim.org/

Reply via email to