Gnus development mailing list
 help / color / mirror / Atom feed
From: Simon Josefsson <jas@extundo.com>
Cc: The Gnus Mailing List <ding@gnus.org>
Subject: Re: Problem gcc'ing with an attachment
Date: Wed, 15 Jan 2003 09:00:27 +0100	[thread overview]
Message-ID: <ilu7kd67sh0.fsf@latte.josefsson.org> (raw)
In-Reply-To: <u8zr8bg7mwy.fsf@blackbird-2k.MITRE.ORG> (David S Goldberg's message of "Mon, 13 Jan 2003 16:35:57 -0500")

David S Goldberg <david.goldberg6@verizon.net> writes:

> This is a new one.  It's happened a few times today and last week.  I
> admit I'm not fully up to date on gnus, though.  I haven't updated
> since last Friday morning.  But since that update, and possibly the
> one before it.  I cannot gcc messages with attachments into my cyrus
> IMAP server.  gcc will work to the netscape server, an nnml folder and
> the cyrus server can handle the message if I bcc myself and deliver
> handles it.  It finally occurred to me to set imap-log and show what
> happens.  Here's what it said.  Is this a server problem (I'm not
> aware of any changes there and my group runs it) or a client problem?
...
> 4608 APPEND "INBOX.in-box" {598763}
> 4608 BAD Literal in Append command too long

Assuming the message really was ~598763 bytes long, I think the server
started to limit the size of messages somehow.  Does this sounds
plausible?

Maybe you want `gnus-gcc-externalize-attachments'.




  reply	other threads:[~2003-01-15  8:00 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-13 21:35 David S Goldberg
2003-01-15  8:00 ` Simon Josefsson [this message]
2003-01-15 14:22   ` David S Goldberg
2003-01-15 14:56     ` Simon Josefsson

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=ilu7kd67sh0.fsf@latte.josefsson.org \
    --to=jas@extundo.com \
    --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).