Please whitelist cPanel in your adblocker so that you’re able to see our version release promotions, thanks!

The Community Forums

Interact with an entire community of cPanel & WHM users!

exim.conf error?

Discussion in 'E-mail Discussion' started by deadlock, Jun 16, 2007.

  1. deadlock

    deadlock Well-Known Member

    Joined:
    May 12, 2002
    Messages:
    58
    Likes Received:
    0
    Trophy Points:
    306
    A few days ago, line 615 of exim.conf was updated to 'address_pipe' instead of 'virtual_address_pipe' (see below), which caused my script to run twice for every delivery. At the time it was the only change to exim.conf on that particular day which tells me it was done deliberately for some reason. Whatever that reason was, the side effect is really irritating. Can it please be changed back to virtual_address_pipe so that I don't have to manually fix it every time there's an update?
    Code:
    mainacct_central_user_filter:
        driver = redirect
        allow_filter
        allow_fail
        check_local_user
        domains = ! lsearch;/etc/userdomains
        condition = "${perl{hasfilterfile}{$local_part}}"
        file = "${perl{getfilterfile}{$local_part}}"
        file_transport = address_file
        pipe_transport = address_pipe ###### HERE
        reply_transport = address_reply
        retry_use_local_part
        no_verify
    
     
  2. cPanelNick

    cPanelNick Administrator
    Staff Member

    Joined:
    Mar 9, 2015
    Messages:
    3,480
    Likes Received:
    30
    Trophy Points:
    158
    cPanel Access Level:
    DataCenter Provider
    address_pipe is the the correct transport. Can you pm me a test delivery with exim?


    # exim -d -t
    To: yourusername
    From: root
    Subject: subject that will match your filter

    body that will match your filter
    .
     
  3. deadlock

    deadlock Well-Known Member

    Joined:
    May 12, 2002
    Messages:
    58
    Likes Received:
    0
    Trophy Points:
    306
    Thanks Nick!

    For posterity, the solution was to move the filter from /etc/vfilters to a local user .forward file.

    Pipes now work in .forward files when they didn't before :)
     
Loading...

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.
    Dismiss Notice