Re: mutt attachment error
On Tue 10 May 2016 at 17:43:03 (+0200), Sven Hartge wrote:
> David Wright <deblis@lionunicorn.co.uk> wrote:
> > On Tue 10 May 2016 at 11:07:47 (-0400), Haines Brown wrote:
>
> >> I tried to use mutt to send someone a zip file of about 50 Mb and got
> >> the error: "Error sending message, child exited 1 (). Could not send
> >> message."
> >>
> >> I assumed the attachment was too large and so went to
> >> /etc/exim4/conf.d/main/02*/ and altered the configuration to be:
> >>
> >> # Message size limit. The default (used when MESSAGE_SIZE_LIMIT
> >> # is unset) is 50 MB
> >> .ifdef MESSAGE_SIZE_LIMIT
> >> # message_size_limit = MESSAGE_SIZE_LIMIT # I commented this line
> >> message_size_limit = 200 MB # I added this line
> >> .endif
> >>
> >> I restarted exim, but it had no effect.
>
> > Isn't the Debian way to put
>
> > MESSAGE_SIZE_LIMIT=foo
>
> > into /etc/exim4/update-exim4.conf.conf and then run
> > # dpkg-reconfigure exim4-config
>
> No, that won't work. You cannot just put stuff into
> /etc/exim4/update-exim4.conf.conf and hope it will make it into the
> configuration.
Yes, I chose the wrong file. Hope doesn't come into it:
dpkg-reconfigure exim4-config sees to that.
I think it's quite unusual for there not to be any stub file provided
by Debian. In fact, it'd be quite useful in this case as
/etc/exim4/exim4.conf.localmacros could reiterate the fact that it's
only for unsplit configuration, and
/etc/exim4/conf.d/main000_localmacros could ditto for split.
BTW when will dpkg-reconfigure exim4-config either stop saying
"hostname --fqdn did not return a fully qualified name, dc_minimaldns will not
work. Please fix your /etc/hosts setup." or suggest a reasonable fix?
Or IOW, why has bug #504427 never even received acknowledgment?
Cheers,
David.
Reply to: