?

Log in

No account? Create an account

fetchmail quirk?

« previous entry | next entry »
Feb. 25th, 2006 | 10:14 pm
mood: busybusy
music: R. E. M. - Strange

So my mail arrives at my host server, and it's there in my inbox.
From another server, where I prefer to keep the mail, I use fetchmail to grab the mail via IMAP, and remove it from that other server if I've successfully retrieved it.
For the most part, this works excellently.

But lately, I've been encountering a situation where certain emails (usually ones with many lines of quoted messages; replies-to-replies-to-replies...) are rejected as "exceeding maximum size" (despite being only medium-sized) ... and deleted! from the server where I'd already received them and they were fine!

From the fetchmail manpage:

SMTP/ESMTP ERROR HANDLING
       Besides the spam-blocking described above, fetchmail takes special actions on the  following
       SMTP/ESMTP error responses

       452 (insufficient system storage)
            Leave the message in the server mailbox for later retrieval.

       552 (message exceeds fixed maximum message size)
            Delete the message from the server.  Send bounce-mail to the originator.


What? How is either of those things the right thing for fetchmail to do in this situation?

Link | Leave a comment | Share

Comments {3}

JP Sugarbroad

(no subject)

from: taral
date: Feb. 27th, 2006 12:24 am (UTC)
Link

Because fetchmail is designed to simulate a proper forwarding. If the mail had be *forwarded* to your local SMTP server instead of stored, it would have been rejected and a bounce sent to the sender.

Solution? Don't use SMTP for local delivery!

Reply | Thread

Triple Entendre

(no subject)

from: triple_entendre
date: Mar. 1st, 2006 02:15 am (UTC)
Link

ah! thank you!

you are my hero for today. (or rather, two days ago).

Reply | Parent | Thread

VIM

from: anonymous
date: Mar. 4th, 2006 04:35 pm (UTC)
Link

VIM!

Reply | Thread