Exim Advanced Config editor to fix piping problem

bladerunner316

• August 03, 2022 21:41

Hi All- Using cPanel & WHM v104.0.7 I need to make changes outlined here:

• 

  cPRex Jurassic Moderator

  • August 04, 2022 14:11

  Hey there! It sounds like you already had a ticket opened with our team - is that correct? If so, could you post the number here so I can review that?

  0
• 

  bladerunner316

  • August 04, 2022 16:13

  Hey there! It sounds like you already had a ticket opened with our team - is that correct? If so, could you post the number here so I can review that?

  
  yes, i do have a ticket. 94471791 was hoping the very smart group here would have an idea on how this could be accomplished. The reason i need this modification is because piped emails, while being successfully processed, are giving the sender a bounce back with the following errors (so they believe their message was not processed): PHP Warning: ini_set(): Session ini settings cannot be changed after headers have already been sent in /pathtoOSticket/bootstrap.php on line 19 PHP Warning: session_cache_limiter(): Session cache limiter cannot be changed after headers have already been sent in /pathtoOSTicket/bootstrap.php on line 21

  0
• 

  cPRex Jurassic Moderator

  • August 04, 2022 17:37

  Thanks for posting the ticket number - I'm following along with that on my end as well. I do see Devon is looking into that again now so you'll be getting a reply there soon.

  0
• 

  cPRex Jurassic Moderator

  • August 05, 2022 14:02

  Well, it looks like there really is no good way to do this. One of our Level 3 technicians was able to create some one-off customizations for you, but they were pretty extreme and not something we would support.

  0
• 

  jandafields

  • February 03, 2023 00:38

  I have also been wanting to do this. I'm piping to a curl command, and no matter what I try, sending output to dev null, or sending output to a tmp file so that there is no return value, curl still returns something (a blank line perhaps) so I still end up with delivery failure emails. Which, of course, are not delivery failures at all. they are just the return from the pipe. So now I'm having to do email filters to catch these, but not catch legitimate delivery failures.

  0

Please sign in to leave a comment.