Yea, that's the main issue.. But as it turned out, I actually was receiving bounce messages turned on - they apparently go to Admin Moderation, but, in 1.1.6, the code Emailpost.subs.php to view the bounced email gets hung up looking for "Html_2_BBC" at line 75, or so says the Error message and the log files when Admin tries to see what the email is. So there's no way to know what the bad message is - it's not a message that will post if approved, so all admin can do with it is delete "whatever it was" (someone not a member sending email to the forum? Could be anything, or anything else, and probably is.. my own mail server was way down on the likely possibilities list..).
I sent you a PM on that, Spuds, since I can't find "Html_2_BBC" either (I'm no smarter than the code apparently, I too occasionally get wrapped about the axle looking for things that evidently don't exist ), and I'm not 100% positive that code call is in the original 1.1.6 Emailpost.subs.php file (I think it is, but I did some fiddling with that file awhile back and while my backup files show the same code call, I still don't rule out the possibility this is yet another self-inflicted head-wound). . I was thinking of commenting the "Html_2_BBC" call out just to see what happens but decided to wait for your feedback before I break something else or call it a "bug".
Last post by Steeley -
I'm posting this up because I got bit by an "update" to my hosts email server. This isn't an EA BUG (unless you consider EA has the option of using php's native Mail() function a bug!
Background - I have a simple email script on my server that sends an email to people who activate it. Suddenly, people stopped getting it. I assumed there was something on their end because it worked for me just fine. I discovered recently it wasn't their mail server, it was MY mail server..
I isolated the problem to be a change either in the formatting of the email presented by php mail() to my hosts' mail server, or in my case now, more likely my host's mail server itself .. the result being that the email going out that used to start off with:
I didn't notice because the return addy for that script is "no_reply@mydomain.com", so the bounces go to bit-heaven.
And yes, EA using php mail() WAS also affected.
I found a bunch of EA bounce messages on the server (I guess I didn't have EA set for gathering bounce mails), that said: "Mail sent by user nobody being discarded due to sender restrictions in WHM->Tweak Settings.
cPanel's WHM->Tweak Settings checklist includes: Prevent “nobody” from sending mail — Enable this setting to block email that the nobody user sent to the remote address.
Note the key phrase "remote address". If the recipient address is on the host, it goes out fine. That would include you, most likely, so nothing appears amiss when you use or test it.
No wonder my forum traffic dropped off noticeably recently..
The simplest fix is for the host to "uncheck" that setting, and voilla!
Otherwise, switch EA to sending mail via SMTP instead of "PHP Mail", or if there's more affected than just EA, install a mail handling program that allows for more customization than php's mail() function does.
Neither I, nor my host, have discovered what changed the "hosted_user" to "nobody". (The server owners probably did an "upgrade" to the mail server and didn't tell anyone).
Last post by Steeley -
The old expression "Incompatibility is just an upgrade away" is becoming more and more evident every day. An upgrade on the internet or server and suddenly some ElkArt forum operation breaks. A forum error is reported as a bug or on the support board, and after being "trouble-shot" is isolated to something indeed in the environment that is no longer compatible with the EA version running. It's not a bug in the code, but may drive a code patch or version update to address.
There's a lot of that kind of info scattered all over the forum that requires an upgrade to a later (or for a new potential EA admin with an older server set up, an earlier) EA version to work right.
(For example, 2.0 may not work well for someone stuck with a server running PHP 5.6, where v1.1.7 and earlier does? How does (s)he find that out besides posting up somewhere asking if anyone knows ... ? )
PHP version, DB type and its version are significant environmental dependencies, but also changes in the internet Email security/Spam functions and servers can suddenly render an EA version "non-functional" in a significant way.
When we do discover an issue is indeed an environmental incompatibility, having a separate board (perhaps with sub boards of specific versions) to capture and list those discoveries would be a valuable resource and reference. It wouldn't be for reporting and resolving issues, but for capturing the identified incompatibility and maybe linking to patches or workarounds (if any) for that version's reported incompatibility.
If that sounds like a nifty idea, I'd be remiss if I were to suggest something for other people to do, so I'm willing to participate in discussing architecture and procedure for that kind of board, and since I'm retired and have nothing to do but make dinner and screw-around with stuff (including my own forum and websites), I'm willing to even assist in its operation if desired.
Another interesting little thing just now... since I had 3 PM's in my "inbox" two from Burke Knight and one from Spuds, and I replied to Spuds first (that cleared the "New" flag on that one), and read the first one from Burke Knight (that , or perhaps clicking to read the third, cleared the new flag on the second, ), but after I read the third (and last new PM), the New flag and the New Message icon count {1] remained displayed and wouldn't go away after I left the PM function. No matter how many times I went back and clicked the link in the display to "read it" it wouldn't clear. I had to go back, and start a reply, and THEN the New Message notifications cleared. Didn't bother to send the reply after it cleared (I was going to ask Burke Knight if he dropped it in something sticky before sending it), I just exited the function without sending.
Don't recall seeing that before, I'll keep an eye out in case it's repeatable.
I suspect that you have to do something else in the function after reading a message, but unless you're going to delete or reply to it there's nothing else to do except leave the function and that doesn't clear the NEW flag.., just clicking the link to read it doesn't do it, nor does clicking on something else outside the message function after you read it .. maybe we need a "I Read It Already, Dammit!" button or something
Last post by Steeley -
That's a start Spuds.... Over time, hopefully we get input as sysops report things like "We upgraded to php X.y and now my EA v {whatever} looses {some significant functionality}. There's a lot of that kind of info all over the forum here in "bug reports", etc. that really aren't "bugs" in the code, but compatibility issues with the environment they're running in, which requires an upgrade to a later (or for a new potential EA admin with an older server set up, an earlier) EA version to work right.
(2.0 may not work well for someone stuck with a server running PHP 5.6, where v1.1.7 and earlier does? How does (s)he find that out besides posting up somewhere asking if anyone knows ... ? )
PHP isn't the only factor of course, DB type and its version are significant factors too (any EA versions compatible with HIVE? Or NOT compatible with Azure SQL?)
When we do discover an issue is indeed an environmental incompatibility, maybe recording that in this thread when we figured that out will build a quick reference as we go along. Perhaps this topic should be changed to "Environmental (In?)compatibilities by EA Version" or something like that. At the risk of mission creep -maybe a Board with topics or sub-boards by version number where this compatibility stuff is captured for reference (after issues reported elsewhere - bug reports, support, etc. - are isolated in those boards , not for suspected issues to be reported and worked on in this reference board), would build a valuable resource . That discussion is above my paygrade however, although I wouldn't mind being part of that discussion - or the solution to make it work.. I'll post this idea up on the Site Feedback board .
Modern, Free, Powerful
), and I'm not 100% positive that code call is in the original 1.1.6 Emailpost.subs.php file (I think it is, but I did some fiddling with that file awhile back and while my backup files show the same code call, I still don't rule out the possibility this is yet another self-inflicted head-wound). . I was thinking of commenting the "Html_2_BBC" call out just to see what happens but decided to wait for your feedback before I break something else or call it a "bug".
)