[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

more fetchmail questions



I've got a ... well, what basically amounts to a kludge to get around a
blocked SMTP port... I'm using a remote mailbox and fetchmail to serve
as a sort of virtual mailhosting, which has, until now, worked just
fine.

I say until now because I hadn't noticed my setup's behavior where
bounced mail is concerned -- basically, fetchmail grabs the mail, shunts
it to my local sendmail deamon, and tries to deliver it.  

The problem is that when sendmail cannot deliver it, it sends out a
bounce message, and the fetchmail client terminates the fetch, since it
is unable to deliver the mail.  Which is fine, and desireable behavior.
What isn't desireable is that fetchmail leaves the offending piece of
mail on the server, to be bounced *again* the next time fetchmail is
run.

So, basically ... how on earth do I get rid of a piece of mail from my
server when my local sendmail can't deliver it?

my (well, root's) .fetchmailrc :

poll sakima.octoraro.org
  localdomains meteu.octoraro.org
  user xxxxxxxxxxxxxxxx
  pass xxxxxxxxxxxxxxxx
  to flip *
  mda "/usr/sbin/sendmail   -oem  -f    %F    %T "

And, the output of a fetchmail run:

meteu:/root:26# fetchmail
3 messages for greywolf at sakima.octoraro.org.
reading message 1 of 3 (360 header octets)  (0 body octets)  flushed
reading message 2 of 3 (360 header octets)  (0 body octets) fetchmail:
MDA exited abnormally or returned nonzero status
 not flushed
reading message 3 of 3 (360 header octets)  (0 body octets)  flushed

The first and third messages are to vaild addresses, the second is not 
(I know that because I set it up that way :) ... I need a way to get
that second message *off* the server...preferably without my
intervention... :)

 - flip

----------------------------------- flip@csh.rit.edu/flip@octoraro.org ----
"One slip, and down the hole you fall
 It seems to take no time at all"
    -- Pink Floyd, One Slip


Reply to: