Brian <a...@cityscape.co.uk> wrote: > On Tue 10 May 2016 at 17:43:03 +0200, Sven Hartge wrote: >> David Wright <deb...@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. > Didn't spot that; exim's .confs can be confusing. The file /etc/exim4/update-exim4.conf.conf is the configuration file for the configuration generator, not Exim4 itself. > What file is used for non-split configuration? Have a look at /usr/share/doc/exim4/README.Debian.gz, Section 2.1.3 "Using Exim Macros to control the configuration" Everything is documented there and the following sections, on how to expand or override the configuration system provided by the Exim4 maintainers. Grüße, Sven. -- Sigmentation fault. Core dumped.
