Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #167831
| From | Ron Leach <ronleach@tesco.net> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: mutt attachment error |
| Date | 2016-05-13 19:10 +0200 |
| Message-ID | <ryoL8-7Vp-15@gated-at.bofh.it> (permalink) |
| References | <rxhsm-4N0-15@gated-at.bofh.it> <rxkgx-80L-1@gated-at.bofh.it> <ryjiq-2bj-17@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
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 endings, but I had thought, and this wikipedia site https://en.wikipedia.org/wiki/Newline suggests, that the line ending that *should* be used in Linux is x 0A (LF line feed), not x 0D (CR) If your autogenerated file shows the MESSAGE_SIZE_LIMIT = 200M followed immediately by <##################> then the exim system (possibly) doesn't like the CR line ending. [That was the advice given me on the debian-exim list earlier this month, where I had posted a similar question. Brian has already mentioned that thread in an earlier message.] Perhaps someone who knows for sure what the line-endings ought to be could chime in. regards, Ron
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll 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