On Tue 17 May 2016 at 12:32:33 -0500, David Wright wrote:
> On Thu 12 May 2016 at 20:38:41 (+0100), Brian wrote:
>
> > For Exim and minimaldns the question is
> >
> > Does the hostname resolve to a fqdn (something with a dot in it)?
> >
> > 127.0.1.1 alum.anything_you_want
On Thu 12 May 2016 at 20:38:41 (+0100), Brian wrote:
> On Thu 12 May 2016 at 10:08:49 -0500, David Wright wrote:
> > On Thu 12 May 2016 at 11:33:10 (+0100), Brian wrote:
> > > On Wed 11 May 2016 at 14:51:31 -0500, David Wright wrote:
> > > > BTW when will dpkg-reconfigure exim4-config either st
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
- 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
On 13/05/2016 12:10, Haines Brown wrote:
I'm still having no luck increasing maximum attachment size.
I create file: /etc/exim4/exim4.conf.localmacros
I leave it default permissions: -rw-r--r-- 1 root root
It has a single line: MESSAGE_SIZE_LIMIT = 200M
followed by CR.
I am no expert on line e
On Fri 13 May 2016 at 07:10:02 -0400, Haines Brown wrote:
> I'm still having no luck increasing maximum attachment size.
>
> I create file: /etc/exim4/exim4.conf.localmacros
> I leave it default permissions: -rw-r--r-- 1 root root
> It has a single line: MESSAGE_SIZE_LIMIT = 200M
> followed by CR
On Fri 13 May 2016 at 12:01:02 -0400, Haines Brown wrote:
[...snip...]
> > WARNING WARNING WARNING^MESC[9d# This file was generated dynamically
> > from^MESC[10d# split config files in the /etc/exim4/conf.d/
[...snip...]
> I didn't understand the reference here to split configuration. I checke
- Forwarded message from Sven Hartge -
Date: Fri, 13 May 2016 15:41:53 +0200
From: Sven Hartge
To: debian-user@lists.debian.org
Subject: Re: mutt attachment error
User-Agent: tin/2.3.1-20141224 ("Tallant") (UNIX) (Linux/4.3.0-1-amd64
(x86_64)) tinews.pl/1.1.39
Haines Br
Haines Brown wrote:
> I'm still having no luck increasing maximum attachment size.
> I create file: /etc/exim4/exim4.conf.localmacros
> I leave it default permissions: -rw-r--r-- 1 root root
> It has a single line: MESSAGE_SIZE_LIMIT = 200M
> followed by CR.
> And I restart exim: # invoke-rc.d e
David Wright wrote:
> On Fri 13 May 2016 at 07:10:02 (-0400), Haines Brown wrote:
>> I'm still having no luck increasing maximum attachment size.
>>
>> I create file: /etc/exim4/exim4.conf.localmacros
>> I leave it default permissions: -rw-r--r-- 1 root root
>> It has a single line: MESSAGE_SIZE_
On Fri 13 May 2016 at 07:10:02 (-0400), Haines Brown wrote:
> I'm still having no luck increasing maximum attachment size.
>
> I create file: /etc/exim4/exim4.conf.localmacros
> I leave it default permissions: -rw-r--r-- 1 root root
> It has a single line: MESSAGE_SIZE_LIMIT = 200M
> followed by C
I'm still having no luck increasing maximum attachment size.
I create file: /etc/exim4/exim4.conf.localmacros
I leave it default permissions: -rw-r--r-- 1 root root
It has a single line: MESSAGE_SIZE_LIMIT = 200M
followed by CR.
And I restart exim: # invoke-rc.d exim4 reload
But:
# exim -bP | g
On Thu 12 May 2016 at 10:08:49 -0500, David Wright wrote:
> On Thu 12 May 2016 at 11:33:10 (+0100), Brian wrote:
> > On Wed 11 May 2016 at 14:51:31 -0500, David Wright wrote:
> > >
> > > BTW when will dpkg-reconfigure exim4-config either stop saying
> > > "hostname --fqdn did not return a ful
On Thu 12 May 2016 at 11:33:10 (+0100), Brian wrote:
> On Wed 11 May 2016 at 14:51:31 -0500, David Wright wrote:
> > On Tue 10 May 2016 at 17:43:03 (+0200), Sven Hartge wrote:
> > > David Wright wrote:
> > > > Isn't the Debian way to put
> > >
> > > > MESSAGE_SIZE_LIMIT=foo
> > >
> > > > into /e
On Wed 11 May 2016 at 14:51:31 -0500, David Wright wrote:
> On Tue 10 May 2016 at 17:43:03 (+0200), Sven Hartge wrote:
> > David Wright wrote:
> > > Isn't the Debian way to put
> >
> > > MESSAGE_SIZE_LIMIT=foo
> >
> > > into /etc/exim4/update-exim4.conf.conf and then run
> > > # dpkg-reconfigur
On Tue 10 May 2016 at 17:43:03 (+0200), Sven Hartge wrote:
> David Wright 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
>
On Wed 11 May 2016 at 18:28:59 +0200, to...@tuxteam.de wrote:
> just a little note: "exim -bP" dumps all configuration items Exim
> thinks it's seeing (after all Debian magic happened) So perhaps
> for debugging you might try:
>
> sudo exim -bP | grep size
>
> which, on my box gives:
>
> bo
On Wed, 11 May 2016 11:12:26 -0400
Haines Brown 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi
just a little note: "exim -bP" dumps all configuration items Exim
thinks it's seeing (after all Debian magic happened) So perhaps
for debugging you might try:
sudo exim -bP | grep size
which, on my box gives:
bounce_return_size_limit = 100K
Haines Brown 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/exi
On Tue, May 10, 2016 at 07:58:36PM +0200, Sven Hartge wrote:
> Brian wrote:
> > On Tue 10 May 2016 at 17:43:03 +0200, Sven Hartge wrote:
> >> David Wright 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
On Wed, 11 May 2016 at 04:43, Brian wrote:
> On Tue 10 May 2016 at 12:56:47 -0600, Charlie Kravetz wrote:
>
> > On Tue, 10 May 2016 17:03:47 +0100
> > Brian wrote:
> > >
> > >Didn't spot that; exim's .confs can be confusing. What file is used for
> > >non-split configuration?
> > >
> >
> > Not m
On Tue 10 May 2016 at 12:56:47 -0600, Charlie Kravetz wrote:
> On Tue, 10 May 2016 17:03:47 +0100
> Brian wrote:
> >
> >Didn't spot that; exim's .confs can be confusing. What file is used for
> >non-split configuration?
> >
>
> Not meaning to send this to you, Brian, but I lost the previous mess
On Tue, 10 May 2016 17:03:47 +0100
Brian wrote:
>On Tue 10 May 2016 at 17:43:03 +0200, Sven Hartge wrote:
>
>> David Wright 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 erro
On Tue 10 May 2016 at 19:58:36 +0200, Sven Hartge wrote:
> Brian wrote:
> > On Tue 10 May 2016 at 17:43:03 +0200, Sven Hartge wrote:
> >> David Wright wrote:
> >>> Isn't the Debian way to put
>
> >>> MESSAGE_SIZE_LIMIT=foo
>
> >>> into /etc/exim4/update-exim4.conf.conf and then run
> >>> # d
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
Brian wrote:
> On Tue 10 May 2016 at 17:43:03 +0200, Sven Hartge wrote:
>> David Wright 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 (). Co
On Tue 10 May 2016 at 17:43:03 +0200, Sven Hartge wrote:
> David Wright 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
>
David Wright 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
On Tue 10 May 2016 at 10:28:24 -0500, David Wright 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 assume
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/
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 d
32 matches
Mail list logo
