The real fix is not to process the above commands with the shell.
Thanks for these tips too.
I decided to popen() directly to sendmail without saving a message to tmp
file.
Unfortunately I don't see any php function allowing to popen without
executing a command with the shell.
What do you
On 12/11/2013 8:37 AM, Marcin Szymonik wrote:
The real fix is not to process the above commands with the shell.
Thanks for these tips too.
I decided to popen() directly to sendmail without saving a message to
tmp file.
Unfortunately I don't see any php function allowing to popen without
Am 11.12.2013 14:37, schrieb Marcin Szymonik:
The real fix is not to process the above commands with the shell.
Thanks for these tips too.
I decided to popen() directly to sendmail without saving a message to tmp
file.
Unfortunately I don't see any php function allowing to popen without
On 11-12-2013 15:37, Marcin Szymonik wrote:
Unfortunately I don't see any php function allowing to popen without
executing a command with the shell.
There are some functions in php to executing shell or another program.
exec, system or piping like popen (popen, fopen). But I think you want
to
Am 11.12.2013 14:49, schrieb M.Atıf CEYLAN:
On 11-12-2013 15:37, Marcin Szymonik wrote:
Unfortunately I don't see any php function allowing to popen without
executing a command with the shell.
There are some functions in php to executing shell or another program. exec,
system or piping
OK, I think I will pass messages to localhost 25 or use advanced content
filter.
Many thanks
--
Marcin Szymonik
szymoni...@gmail.com
Marcin Szymonik:
The real fix is not to process the above commands with the shell.
Thanks for these tips too.
I decided to popen() directly to sendmail without saving a message to tmp
file.
Unfortunately I don't see any php function allowing to popen without
executing a command with
In our previous episode (Monday, 09-Dec-2013), li...@rhsoft.net said:
* the local part must not contain special chars
Is that your policy or are you claiming that is a standard? RFC 6530 covers
UTF-8 email addresses and how they should be handled my MTAs.
--
People who would not believe a
Am 10.12.2013 15:18, schrieb LuKreme:
In our previous episode (Monday, 09-Dec-2013), li...@rhsoft.net said:
* the local part must not contain special chars
Is that your policy or are you claiming that is a standard?
it is fact
RFC 6530 covers UTF-8 email addresses and how they should be
In our previous episode (Monday, 09-Dec-2013), li...@rhsoft.net said:
* the local part must not contain special chars
LuKreme:
Is that your policy or are you claiming that is a standard? RFC
6530 covers UTF-8 email addresses and how they should be handled
my MTAs.
Postfix does not currently
Hello Everyone,
I experience a strange problem with our mail system.
Sometimes an user gets a message which should be delivered to another user.
As most messages are delivered properly I can't reproduce that but I have
some logs connected with this problem.
Dec 8 20:36:26 serwery
Marcin Szymonik:
[ Charset ISO-8859-2 unsupported, converting... ]
Hello Everyone,
I experience a strange problem with our mail system.
Sometimes an user gets a message which should be delivered to another user.
As most messages are delivered properly I can't reproduce that but I have
some
Thanks for your reply.
Some lines are missing here. They would show how the message is
delivered to a content filter.
I'm sending more logs below.
You appear to have a broken content filter script.
Why do you think so?
I'm sending content filter configuration and script below - please
I see several problems with the content filter.
First the content filter appears to be using the same temporary
file when different messages arrive at almost the same time.
Before your content filter, these messages have different message
IDs:
Marcin Szymonik:
if($user)
{
exec($sendmail -f $sender -- $recipient $file,$out,$status);
}
else
{
(check if spam)
if($spam) exec(/usr/bin/formail -I 'X-Spam-Flag: YES'
$file|$sendmail -f $sender -- $recipient,$out,$status);
else exec($sendmail -f $sender --
On Mon, Dec 09, 2013 at 12:56:04PM -0500, Wietse Venema wrote:
The real fix is not to process the above commands with the shell.
I would say the one and only fix which is not optional. You can
build argument arrays for execve(2) with externally supplied data
elements, but you must never build
In our previous episode (Monday, 09-Dec-2013), Wietse Venema said:
Instead, you need to eliminate all characters except those that are
known to be safe: a-zA-Z0-9_@:=+, the '-', and maybe a few more.
what about é and ø? Or aren't we utf-8 clean on email addresses yet?
--
What if your DOPE was
Am 09.12.2013 20:03, schrieb LuKreme:
In our previous episode (Monday, 09-Dec-2013), Wietse Venema said:
Instead, you need to eliminate all characters except those that are
known to be safe: a-zA-Z0-9_@:=+, the '-', and maybe a few more.
what about é and ø? Or aren't we utf-8 clean on
Thank you so much!
You really helped me a lot.
All the best :-)
--
Marcin Szymonik
szymoni...@gmail.com
19 matches
Mail list logo
