procmail issue (not recipe help request) - Unix

This is a discussion on procmail issue (not recipe help request) - Unix ; I just got a shell with a new place, and I cant get procmail to process my mail at all. I'm wondering if it's maybe nothing Im doing wrong, but maybe it's not running possibly? I'm a little noobish so ...

+ Reply to Thread
Results 1 to 3 of 3

Thread: procmail issue (not recipe help request)

  1. procmail issue (not recipe help request)

    I just got a shell with a new place, and I cant get procmail to
    process my mail at all. I'm wondering if it's maybe nothing Im doing
    wrong, but maybe it's not running possibly? I'm a little noobish so
    please excuse that in advance.

    My .procmailrc file is:

    LOGFILE=/home/d77/.pm.log
    VERBOSE=no
    COMSAT=no
    MAILDIR=$HOME/Mail
    PATH=/usr/local/bin:/usr/bin

    :0:
    * ^Subject:.*go.*
    | /home/d77/goscript


    ....as you might be able to tell, my goal is to be able to send an
    email with "go" in the subject which will automatically make the
    script "goscript" run.

    So after a few tries of it not working, I notice the log file, .pm.log
    wasn't ever being created or written to. It's like procmail isn't even
    trying.

    If I do ps -aux
    I seem to have permission to view root's running processes, and
    procmail isn't listen among them. Does this mean my admin just doesn't
    have it running? It is installed, though, "which procmail" returns
    that it is indeed there. does it sound like I just need to ask them to
    run it?

    As far as I know, there's nothing special I have to do to make
    procmail start processing my rcfile right? If I read the man page
    right, it just automatically looks for $HOME/.procmailrc ..assuming
    it's running, right?

  2. Re: procmail issue (not recipe help request)

    yerk5 wrote:
    > I just got a shell with a new place, and I cant get procmail to
    > process my mail at all. I'm wondering if it's maybe nothing Im doing
    > wrong, but maybe it's not running possibly? I'm a little noobish so
    > please excuse that in advance.
    >
    > My .procmailrc file is:
    >
    > LOGFILE=/home/d77/.pm.log
    > VERBOSE=no
    > COMSAT=no
    > MAILDIR=$HOME/Mail
    > PATH=/usr/local/bin:/usr/bin
    >
    > :0:
    > * ^Subject:.*go.*
    > | /home/d77/goscript
    >
    >
    > ...as you might be able to tell, my goal is to be able to send an
    > email with "go" in the subject which will automatically make the
    > script "goscript" run.
    >
    > So after a few tries of it not working, I notice the log file, .pm.log
    > wasn't ever being created or written to. It's like procmail isn't even
    > trying.
    >
    > If I do ps -aux
    > I seem to have permission to view root's running processes, and
    > procmail isn't listen among them. Does this mean my admin just doesn't
    > have it running? It is installed, though, "which procmail" returns
    > that it is indeed there. does it sound like I just need to ask them to
    > run it?


    procmail runs on the mail server.
    If your system is not a mail server, you better ask your admin.

    man procmail
    sais:
    ....
    Procmail should be invoked automatically over the .forward
    file mechanism as soon as mail arrives. Alternatively, when
    installed by a system administrator, it can be invoked from
    within the mailer immediately
    ....

    Some mail servers process a $HOME/.forward file with
    "|IFS=' '&&exec procmail -f-||exit 75 #mylogin"

    This requires that the mail server has read access to $HOME.

    Some mail servers and/or procmails are picky about permissions;
    make sure that
    ls -ld $HOME
    has not write access for others.

    --
    echo imhcea\.lophc.tcs.hmo |
    sed 's2\(....\)\(.\{5\}\)2\2\122;s1\(.\)\(.\)1\2\11g;1 s;\.;::;2'

  3. Re: procmail issue (not recipe help request)

    Ah yes, I forgot about needing to use the .forward. It's been years
    since I worked with procmail.

    Just as an FYI in case this helps anyone in the future, when I tried
    using a .forward of:
    "|IFS=' ' && exec procmail -f || exit 75 #d77"
    (with quotes) and tried sending myself a test email from another
    account, the server bounced the email back saying:

    Command died with status 127: "IFS=' ' && exec
    procmail -f || exit 75 #d77". Command output: exec: procmail: not
    found

    Hmm, not found? I tried adding the full path to procmail, hoping that
    would help it find it. Tried this.forward:
    "|IFS=' ' && exec /usr/local/bin/procmail -f || exit 75 #d77"

    Worked. Thanks again!

+ Reply to Thread