Re: [a...@cityscape.co.uk: Re: mutt attachment error]

2016-05-13 Thread Sven Hartge 
Haines Brown  wrote:

> Yes, I discovered that to be the case. So I am now able to configure the
> attachment file as I want:

>   message_size_limit = 200M

But you do know, that just because your MTA does allow mails bigger than
200MiB (which will be ~130MB before base64 encoding), other MTA will
accept those mails.

>From my daily experience as mail server operator for a German University
I can tell you, that most ISPs or mail services have a limit somewhere
between 30MiB and 50MiB (after encoding).

So increasing your local message_size_limit does nothing for you, if you
want to send those big mails elsewhere.

Grüße,
Sven.

-- 
Sigmentation fault. Core dumped.

[a...@cityscape.co.uk: Re: mutt attachment error]

2016-05-13 Thread Haines Brown 
- Forwarded message from Brian  -

Date: Fri, 13 May 2016 18:08:49 +0100
From: Brian 
To: debian-user@lists.debian.org
Subject: Re: mutt attachment error
User-Agent: Mutt/1.5.23 (2014-03-12)

It appears from another mail

  https://lists.debian.org/debian-user/2016/05/msg00565.html

that you are *not* using Exim's non-split configuration. 

Yes, I discovered that to be the case. So I am now able to configure the
attachment file as I want:

  # exim -bP | grep size
  bounce_return_size_limit = 100K
  header_line_maxsize = 0
  header_maxsize = 1048576
  message_size_limit = 200M

Thanks for your patience.