Gnus development mailing list
 help / color / mirror / Atom feed
From: Steinar Bang <sb@dod.no>
To: ding@gnus.org
Subject: Re: Message size too large (where to adjust)
Date: Tue, 31 Aug 2010 19:15:46 +0200	[thread overview]
Message-ID: <871v9ezosd.fsf@dod.no> (raw)
In-Reply-To: <m3y6boclu5.fsf@quimbies.gnus.org>

>>>>> Lars Magne Ingebrigtsen <larsi@gnus.org>:

> Right.  But you'll get a bounce message (or it'll just refuse the
> message and you get an error message immediately).  I think that's
> better than guessing at a limit, and then sending out split messages
> that most (I think) recipients can't read.

True.  Split messages is really bad.






  reply	other threads:[~2010-08-31 17:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-09  0:02 Harry Putnam
2009-04-09  0:10 ` Russ Allbery
2009-04-09  0:24   ` Greg Troxel
2009-04-09  0:29     ` Harry Putnam
2009-04-09  0:24   ` Harry Putnam
2010-08-29 22:15   ` Lars Magne Ingebrigtsen
2010-08-30  5:49     ` Steinar Bang
2010-08-30 11:37       ` Lars Magne Ingebrigtsen
2010-08-30 12:13         ` Steinar Bang
2010-08-30 12:43           ` Lars Magne Ingebrigtsen
2010-08-31 17:15             ` Steinar Bang [this message]
2010-08-31 17:31               ` Steinar Bang
2010-08-30 15:00         ` Rupert Swarbrick

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=871v9ezosd.fsf@dod.no \
    --to=sb@dod.no \
    --cc=ding@gnus.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).