Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.user > #167740

Re: mutt attachment error

Show all headers | View raw

On Wed, 11 May 2016 11:12:26 -0400
Haines Brown <haines@histomat.net> wrote:


> 
> I took a look at /usr/share/doc/exim4/README.Debian.gz and found that
> to use a macro to change a default configuration value I need to
> define the new value in a local configuration file. I have a non-split
> configuration, and so it seems I must create a
> /etc/exim4/exim4.conf.localmacros file.
> 
> The document says that if present this file is read before the
> exim4.conf.template file. I don't understand. Wouldn't reading the
> template file subsequently to it just overwrite my custom value with
> the default value?
> 
> In this localmacros file it seems that I simply need the line
> MESSAGE_SIZE_LIMIT=200MB to redefine maximum message size from the
> default 50 MB to 200MB. I'm unsure of the syntax here. Is "MB"
> acceptable? Need it be separated from the number by a space? The
> document seems to say that for answers to such questions I should read
> the Exim Specification 6.4. It does not tell me where this
> specification is to be found.
> 
> Another point of confusion is that MESSAGE_SIZE_LIMIT is referred to
> as a macro, but in context it seems more just a variable. To set a
> custom value, do I have to write an entire macro from scratch, which
> seems implied by the text, or merely set the value of a variable,
> which is implied by the example?
> 

The reason that macros are used is the answer to your first question:
the macros are referred to and expanded at various points in the
exim.conf.template file. They are generally not macros in the
programming sense, in terms of being entire functions, they are simply
labels which are replaced by values, normally fairly simple values.
Often they are switches to enable an optional feature.

Here's my mail server local macros:

CHECK_RCPT_LOCAL_ACL_CODE = "/etc/exim4/banned_countries"
CHECK_MAIL_HELO_ISSUED = yes
SMTP_ACCEPT_MAX_PER_HOST = 3
CHECK_RCPT_VERIFY_SENDER = yes
CHECK_RCPT_REVERSE_DNS = yes
MAIN_LOG_SELECTOR = +ident_timeout +smtp_confirmation +smtp_connection

If you search exim.conf.template, you will find all these labels. They
will be contained in .ifdef...endif statements to check whether they
exist already, and will usually be assigned default values if not found.

The template file is also pretty much a man page, with a lot of
comments. You can go through it, look at the macro labels and mostly see
what you need to put in your local macro to override the default. One
exception is, as it happens, MESSAGE_SIZE_LIMIT which is referenced but
does not set a default, so you can't see the syntax you need, but Sven
has answered that one.

-- 
Joe

Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

mutt attachment error Haines Brown <haines@histomat.net> - 2016-05-10 17:10 +0200
  Re: mutt attachment error David Wright <deblis@lionunicorn.co.uk> - 2016-05-10 17:30 +0200
    Re: mutt attachment error Brian <ad44@cityscape.co.uk> - 2016-05-10 17:50 +0200
    Re: mutt attachment error Sven Hartge <sven@svenhartge.de> - 2016-05-10 17:50 +0200
      Re: mutt attachment error Brian <ad44@cityscape.co.uk> - 2016-05-10 18:10 +0200
        Re: mutt attachment error Sven Hartge <sven@svenhartge.de> - 2016-05-10 20:00 +0200
          Re: mutt attachment error Brian <ad44@cityscape.co.uk> - 2016-05-10 20:50 +0200
          Re: mutt attachment error Haines Brown <haines@histomat.net> - 2016-05-11 17:20 +0200
            Re: mutt attachment error Sven Hartge <sven@svenhartge.de> - 2016-05-11 18:20 +0200
              Re: mutt attachment error <tomas@tuxteam.de> - 2016-05-11 18:30 +0200
                Re: mutt attachment error Brian <ad44@cityscape.co.uk> - 2016-05-11 19:40 +0200
            Re: mutt attachment error Joe <joe@jretrading.com> - 2016-05-11 19:00 +0200
        Re: mutt attachment error Charlie Kravetz <cjk@teamcharliesangels.com> - 2016-05-10 21:30 +0200
          Re: mutt attachment error Brian <ad44@cityscape.co.uk> - 2016-05-10 21:50 +0200
            Re: mutt attachment error Mark Fletcher <mark27q1@gmail.com> - 2016-05-10 23:50 +0200
      Re: mutt attachment error David Wright <deblis@lionunicorn.co.uk> - 2016-05-11 22:00 +0200
        Re: mutt attachment error Brian <ad44@cityscape.co.uk> - 2016-05-12 12:40 +0200
          Exim and hostname --fqdn, was Re: mutt attachment error David Wright <deblis@lionunicorn.co.uk> - 2016-05-12 17:20 +0200
            Re: Exim and hostname --fqdn, was Re: mutt attachment error Brian <ad44@cityscape.co.uk> - 2016-05-12 21:40 +0200
              Re: Exim and hostname --fqdn, was Re: mutt attachment error David Wright <deblis@lionunicorn.co.uk> - 2016-05-17 19:40 +0200
                Re: Exim and hostname --fqdn, was Re: mutt attachment error Brian <ad44@cityscape.co.uk> - 2016-05-18 01:10 +0200
  Re: mutt attachment error Sven Hartge <sven@svenhartge.de> - 2016-05-10 20:10 +0200
    Re: mutt attachment error Haines Brown <haines@histomat.net> - 2016-05-13 13:20 +0200
      Re: mutt attachment error David Wright <deblis@lionunicorn.co.uk> - 2016-05-13 15:40 +0200
        Re: mutt attachment error Sven Hartge <sven@svenhartge.de> - 2016-05-13 15:50 +0200
      Re: mutt attachment error Sven Hartge <sven@svenhartge.de> - 2016-05-13 15:50 +0200
      Re: mutt attachment error Ron Leach <ronleach@tesco.net> - 2016-05-13 19:10 +0200
      Re: mutt attachment error Brian <ad44@cityscape.co.uk> - 2016-05-13 19:10 +0200

csiph-web