Re: Fetchmail stuck on bad messages

From: Michael D Schleif (mds_at_helices.org)
Date: 08/18/03

  • Next message: David Fokkema: "Re: print manager - cups - mostly SOLVED" 
    Date: Mon, 18 Aug 2003 00:12:28 -0500
To: debian-user@lists.debian.org

    Derrick 'dman' Hudson <dman@dman13.dyndns.org> [2003:08:18:00:57:59-0400] scribed:
    > On Fri, Aug 15, 2003 at 08:22:52PM -0500, Michael D Schleif wrote:
    > [...]
    >
    > | There must be something that exim can/does do that procmail cannot?
    >
    > exim is an MTA (Mail Transfer Agent) that also includes an LDA (Local
    > Delivery Agent).
    >
    > procmail is an LDA.
    >
    > exim does a lot that procmail can't do, and procmail isn't intended to
    > do. procmail can do things that exim can't (for example, changing a
    > message via a filter, such as spamassassin, and then making delivery
    > decisions based on the external program's output).

    OK

    > | What do you think?
    >
    > Use the mail handling chain that works best for you. If you aren't
    > using any of exim's mail processing capabilities for mail you receive,
    > then eliminate it from the equation and have fetchmail hand the
    > messages directly to procmail. (you'll still want (need) exim
    > installed for handling mail that originates locally (ie from cron jobs
    > and the like) and potentially for sending mail (depends on your MUA
    > and whether or not you use programs like reportbug))

    I was wondering more in line of bouncing messages for malformed headers,
    and that ilk. Of course, I need something to act as MTA; but, what I am
    unclear about is that which exim contributes as LDA that cannot --
    readily -- be accomplished via procmail. What are reasons to continue
    to use exim -- or equivalent -- between fetchmail and procmail?

    What do you think? 

    -- 
Best Regards,
mds
mds resource
877.596.8237
-
Dare to fix things before they break . . .
-
Our capacity for understanding is inversely proportional to how much
we think we know.  The more I know, the more I know I don't know . . .
--



    -- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: David Fokkema: "Re: print manager - cups - mostly SOLVED"

    Relevant Pages

    • Re: fetchmail problem
      ... > Connection closed by foreign host. ... Than somewhere I read that Exim, ... > seems that procmail is most likely the easiest to set up. ... configuration file can't be read for some reason. ...
      (Debian-User)
    • Re: Fetchmail stuck on bad messages
      ... exim is an MTA that also includes an LDA (Local ... Delivery Agent). ... procmail is an LDA. ...
      (Debian-User)
    • Re: Fetchmail stuck on bad messages
      ... Exim can do things procmail can't do. ... with mail from fetchmail, I think using procmail directly is better. ... And one of these days I'm going to add SMTP to mutt ...
      (Debian-User)
    • Exim vs Procmail (was: Sendmail vs Exim vs Others)
      ... The FAQ says to use procmail. ... Another point is that exim isn't the only MTA. ... possible with exim filters. ...
      (Debian-User)
    • Re: MUA Filters vs Procmail filters[was] RE: Mailing list procmailrecipe
      ... den 10.04.2004 schrieb Jay Daniels um 17:34: ... "The procmail call in the .forward file is only necessary if the MTA ... sendmail it is totally unnecessary to call procmail a second time ... delivery agent / mail delivery agent). ...
      (Fedora)