253 reputation
19
bio website htbaa.com
location Netherlands
age 26
visits member for 4 years, 7 months
seen Jan 16 at 9:37

I'm a programmer. Simple as that.


May
29
awarded  Self-Learner
Dec
19
awarded  Popular Question
Oct
8
awarded  Yearling
Sep
28
awarded  Student
Jun
16
accepted Postfix MX lookup for delivery instead of local delivery for specific domains
Jun
16
comment Postfix MX lookup for delivery instead of local delivery for specific domains
Thanks, this is a very clarifying answer. Which is basically what @Flimzy said, only more descriptive.
Jun
16
comment Postfix MX lookup for delivery instead of local delivery for specific domains
Thanks for your answer. The setup makes sense although it does indeed complicate stuff quite a lot. We're running Postfix 2.5.4 and it seems postmulti only exists since 2.6. I had already expected that the thing I want is tricky and it seems like all this is a bit much to avoid a 15-minute delay to wait for mail (POP-Locator can only check as early as every 15 minutes). I'll wait a bit more for other people to give a potential answer, otherwise I'll accept this one.
Jun
16
awarded  Editor
Jun
16
comment Postfix MX lookup for delivery instead of local delivery for specific domains
Edited my post. Must add to it that I also tried specifying IP-addresses, as well trying relay. If the Postfix server receives a message it's fine to deliver it locally (= situation where Exchange server is down). If a mail is being sent from the Postfix server (sendmail, php's mail()) then I want it to perform a MX lookup. Optionally it's fine if it tried local delivery afterwards if it can't deliver the e-mail.
Jun
16
revised Postfix MX lookup for delivery instead of local delivery for specific domains
added 73 characters in body; added 93 characters in body; added 4 characters in body
Jun
16
asked Postfix MX lookup for delivery instead of local delivery for specific domains
Mar
8
awarded  Autobiographer
Feb
18
comment Recommended way to restrict Apache users
The BASH script would be executed as the user that's executing the PHP script, so if the user/group rights are correct then yes. But not with safe_mode and open_basedir I believe. You could also just simply disallow using system() by editing php.ini.
Feb
17
comment Recommended way to restrict Apache users
If you don't restrict the actual user and group that owns and execute the file then yes, that is to be expected. If you're executing all files as the httpd user (usually www-data) then it's understandable it can. If you're specifically want to restrict PHP scripts you still can use safe_mode and open_basedir to restrict the user. They'll be around for a while, but eventually get removed as they're deprecated.
Feb
17
comment Beginners security question
Yes that much is obvious, I never said or implied it was the OP's domain. The possible attacker is trying to include his own content in the victim's website, whatever that content may be.
Feb
17
answered Beginners security question
Feb
14
comment lighttpd fails while enabling mod_proxy
Or rather, after "mod_compress". Not that it matters, but readability does :-)
Feb
14
answered Recommended way to restrict Apache users
Feb
14
awarded  Supporter
Jul
5
awarded  Scholar