Problem gcc'ing with an attachment

Problem gcc'ing with an attachment

[David S Goldberg]

[-- Attachment #1: Type: text/plain, Size: 673 bytes --]

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?

Thanks,
-- 
Dave Goldberg
david.goldberg6@verizon.net

[-- Attachment #2: Type: text/plain, Size: 3205 bytes --]

4596 SELECT "INBOX.in-box"
* FLAGS (\Answered \Flagged \Draft \Deleted \Seen gnus-save gnus-forward gnus-dormant $Forwarded $MDNSent gnus-expire $Label1 $Label2 $Label3 $Label4 $Label5)
* OK [PERMANENTFLAGS (\Answered \Flagged \Draft \Deleted \Seen gnus-save gnus-forward gnus-dormant $Forwarded $MDNSent gnus-expire $Label1 $Label2 $Label3 $Label4 $Label5 \*)] 
* 194 EXISTS
* 1 RECENT
* OK [UNSEEN 192] 
* OK [UIDVALIDITY 974143455] 
* OK [UIDNEXT 13320] 
4596 OK [READ-WRITE] Completed
4597 UID SEARCH UNSEEN UNDELETED
* SEARCH 13317 13318 13319
4597 OK Completed
4598 UID SEARCH SEEN
* SEARCH 12158 12171 12172 12174 12182 12185 12187 12188 12190 12340 12351 12356 12369 12404 12414 12421 12549 12601 12650 12924 12983 12986 12995 12996 12997 12999 13002 13004 13012 13069 13072 13074 13077 13115 13127 13129 13133 13145 13146 13147 13148 13149 13150 13151 13152 13153 13154 13164 13165 13166 13167 13168 13169 13170 13171 13172 13173 13174 13175 13180 13181 13182 13183 13184 13186 13187 13188 13189 13190 13191 13192 13193 13194 13195 13196 13197 13198 13199 13200 13201 13202 13203 13204 13205 13206 13207 13208 13209 13210 13211 13212 13213 13214 13215 13216 13217 13218 13219 13220 13221 13222 13223 13224 13225 13226 13227 13228 13229 13230 13231 13232 13233 13234 13235 13236 13237 13238 13239 13240 13243 13244 13245 13246 13247 13248 13249 13250 13251 13252 13253 13254 13255 13256 13257 13258 13259 13260 13261 13262 13263 13264 13265 13266 13268 13269 13270 13271 13272 13273 13274 13275 13276 13277 13278 13279 13280 13281 13282 13283 13284 13285 13286 13287 13288 13289 13290 13291 13292 13293 13294 13295 13296 13297 13298 13299 13300 13301 13302 13303 13304 13305 13306 13307 13308 13309 13310 13312 13313 13314 13315 13316
4598 OK Completed
4599 UID SEARCH FLAGGED
* SEARCH 12158 12171 12172 12174 12182 12185 12187 12188 12190 12340 12351 12356 12369 12404 12414 12421 12549 12601 12650 12924 12983 12986 12995 12996 12997 12999 13002 13004 13012 13069 13072 13074 13077 13115 13127 13129 13133 13148 13168 13172 13175 13180 13181 13184 13188 13189 13190 13191 13192 13197 13198 13199 13200 13201 13202 13204 13205 13207 13208 13209 13210 13213 13215 13226 13227 13228 13229 13230 13231 13232 13234 13235 13236 13237 13238 13239 13240 13245 13247 13249 13255 13259 13260 13261 13262 13263 13264 13265 13269 13271 13278 13279 13280 13281 13285 13287 13292 13297 13298 13302 13305 13306 13310 13313 13314 13315
4599 OK Completed
4600 UID SEARCH ANSWERED
* SEARCH 12986 12995 12997 13002
4600 OK Completed
4601 UID SEARCH KEYWORD gnus-expire
* SEARCH
4601 OK Completed
4602 UID SEARCH KEYWORD gnus-dormant
* SEARCH
4602 OK Completed
4603 UID SEARCH KEYWORD gnus-save
* SEARCH
4603 OK Completed
4604 UID SEARCH KEYWORD gnus-forward
* SEARCH 12650 12986 12995 12999 13165 13192 13207 13260 13269 13271 13278 13284 13286 13288 13302
4604 OK Completed
4605 UID SEARCH RECENT
* SEARCH 13319
4605 OK Completed
4606 FETCH 1,* UID
* 1 FETCH (UID 12158)
* 194 FETCH (UID 13319)
4606 OK Completed
4607 UNSELECT
4607 OK Completed
4608 APPEND "INBOX.in-box" {598763}
4608 BAD Literal in Append command too long

Re: Problem gcc'ing with an attachment

[Simon Josefsson]

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'.

Re: Problem gcc'ing with an attachment

[David S Goldberg]

>>>>> On Wed, 15 Jan 2003 09:00:27 +0100, Simon Josefsson
>>>>> <jas@extundo.com> said:

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

Unfortunately no.  I'm no where near the quota on my account and
mailing it to myself (via BCC) works.

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

But I had forgotten about that.  And yes I do want to use it. Thanks!
It doesn't fix the bug if it is one, but there's no need for me to
have large files sitting on my mail server.

-- 
Dave Goldberg
david.goldberg6@verizon.net

Re: Problem gcc'ing with an attachment

[Simon Josefsson]

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

>>>>>> On Wed, 15 Jan 2003 09:00:27 +0100, Simon Josefsson
>>>>>> <jas@extundo.com> said:
>
>> Assuming the message really was ~598763 bytes long, I think the server
>> started to limit the size of messages somehow.  Does this sounds
>> plausible?
>
> Unfortunately no.  I'm no where near the quota on my account and
> mailing it to myself (via BCC) works.

Maybe it has a limit just for APPEND...  Does moving an article
between groups work?  Does copying between groups work?  Does posting
to a nnimap group work?  (The first two probably works, while the
latter uses APPEND if I recall correctly, and, assuming my hypothesis
is correct, shouldn't work.)  The article probably need to be ~600kb
or larger to trigger it.