On Mon, Oct 19, 2015 at 10:19:00AM -0600, Mike Brown wrote:
> I'm trying to get started with OpenSMTPD 5.7.3p1 from the FreeBSD ports
> collection on my BeagleBone Black, but I encountered a two issues right
> off the bat with configuration checking ('smtpd -n'):
>
>
> 1. If gethostname(3) / hostname(1) returns a non-FQDN (e.g. 'myhost') which
> is
> not resolvable, 'smtpd -n' fails with this message:
>
> invalid hostname: getaddrinfo() failed: hostname nor servname provided, or
> not known
>
> It seems to work OK if the hostname is a FQDN (even if unresolvable), or if
> the unqualified hostname is resolvable (e.g. it is in /etc/hosts as a
> localhost alias).
>
> I don't know what the desired behavior is in this situation, but it seems
> that
> smtpd should be able to start up with no less difficulty than sendmail. Or,
> if
> smtpd is not designed to work with a non-FQDN hostname, the error message
> should be clearer about what the user should do, since it's not a problem
> with
> the smtpd config, per se. The message could say "smtpd requires that the
> local
> machine's hostname '<hostname>' be resolvable", maybe also direct the user to
> check /etc/hosts.
>
I'll have a look at this when I'm done with bringing filters to OpenBSD.
> 2. Assuming the local hostname is a FQDN or is otherwise resolvable, 'smtpd
> -n' works OK with a minimal smtpd.conf:
>
> listen on 127.0.0.1 secure
> listen on ::1 secure
> accept for any relay
>
> However, it consumes all available memory for over 20 minutes if I add this:
> table aliases file:/usr/local/etc/mail/aliases
> accept for local alias <aliases> deliver to mbox
>
> It doesn't matter if the 'accept' line is present, nor does the content of
> the
> aliases file seem to matter; it can even be empty. Eventually smtpd starts up
> and the system becomes usable again, but not until after various essential
> services have been interrupted by the memory churn.
>
> I assume no one else has had this problem, so it must be something peculiar
> to
> my system. What can I do to help diagnose it?
>
Turns out someone else running on ARM is experiencing a similar issue.
A ticket has been opened on our tracker at github, can you:
- open a ticket for the first issue
- check if your second issue is appropriately described by ticket #642
and either add a comment to it with as much details as you can, or
open a different ticket if it's a different issue ?
thanks
--
Gilles Chehade
https://www.poolp.org @poolpOrg
--
You received this mail because you are subscribed to [email protected]
To unsubscribe, send a mail to: [email protected]
