Fabrice, I do not have Delphi available at this moment, so could you test
the code below to see if it is treated as spam by SpamAssassin?
Checking against SpamAssassin is required, but checking against most common
mail readers (either standalone mail client or webmail applications) is also
man
Maybe you could carefully read those documentation and review ICS code to
see if it needs some improvement. If improvment is needed, then propose some
changes. Don't forget the gold rule: change in ICS must not break any
existing code.
--
francois.pie...@overbyte.be
The author of the freeware
I think here is what we should do:
- the OpsnSSL DLLs must be loaded only from process folder of the
ICS-based-our-code-exe
- before loading the DLLs, we must check for their presence in RAM and fire
an exception in that case.
Regards,
SZ
On Sat, Sep 4, 2010 at 10:29 AM, Francois PIETTE
wrote:
Well, like I wrote, it effects all programs that use ICS. And it is a
bit harder to find a solution that fits all in this case due to nature
of the problem.
This is how ICS loads for example SSLLEAY32.DLL:
const GSSLEAY_DLL_Name : String = 'SSLEAY32.DLL';
...
GSSLEAY_DLL_Handle := LoadLibrary(PC
Forget about my remark about "\" or "/". The DllPath could be used as
is just DllPath + LibraryName. This avoids the need to process
needlessly slashes or backslashes. If this is used I would suggest a
bold remark in the docs on Wiki to encourage use of this property if
this is to be used.
Anyway,
const GSSLEAY_DLL_Name : String = 'SSLEAY32.DLL';
I think the solution is much simpler than what you think: Change "const" by
"var" so that the DLL name is provided thru a global variable (by the way a
global typed constant can be used as a global variable if J+ option is used
which is the c
Francois PIETTE wrote:
>> const GSSLEAY_DLL_Name : String = 'SSLEAY32.DLL';
>
> I think the solution is much simpler than what you think: Change
> "const" by "var" so that the DLL name is provided thru a global
This is not required since writable typed constants is enabled.
--
Arno Garrels
--
Hello DZ-Jay,
At least Firebird provides 5 priorities so why should we remove this
feature from ICS?
It's likely that X-MSMail-Priority can be removed, however my OE v6
still uses it, XP SP3.
Isn't it just the high priority itself, that scores?
--
Arno Garrels
> On 09/03/2010 15:09, Arno G
Arno Garrels wrote:
> Isn't it just the high priority itself, that scores?
Or most likely the existence of the word "Priority", may it be low or
high? But I cannot remember when I saw the last spam mail with a high
priority.
--
Arno Garrels
--
To unsubscribe or change your settings for TWSo
On Sep 04, 2010, at 11:40, Arno Garrels wrote:
> Hello DZ-Jay,
>
> At least Firebird provides 5 priorities so why should we remove this
> feature from ICS?
It's not standard, most clients assume there's only "low," "normal," and
"urgent". In any case, setting TSmtpCli to use only three values
DZ-Jay wrote:
> On Sep 04, 2010, at 11:40, Arno Garrels wrote:
>
>> Hello DZ-Jay,
>>
>> At least Firebird provides 5 priorities so why should we remove this
>> feature from ICS?
>
> It's not standard, most clients assume there's only "low," "normal,"
> and "urgent". In any case, setting TSmtpCl
On Sep 04, 2010, at 13:14, Arno Garrels wrote:
> DZ-Jay wrote:
>> On Sep 04, 2010, at 11:40, Arno Garrels wrote:
>>
>>> Hello DZ-Jay,
>>>
>>> At least Firebird provides 5 priorities so why should we remove this
>>> feature from ICS?
>>
>> It's not standard, most clients assume there's only "lo
12 matches
Mail list logo
