>I think 1.3.9.x has been long tested and has no known bugs, plus it
>has many
>new features above 1.3.3.10
It has known bugs. Some minor and one severe for some installations. I
was not able to fix it in 1.3.9.1 because the code was frozen. That is
the reason I proposed 1.4.1.
ASSP is published
>>Will do, but will 1.3.9.1 be ever published on sf ? When ?
>>
>>Or it's been aborted like 1.3.5 and next published version will be
>>1.4.1.x ?
>
>Aborted?
1.3.5 has never been released to the public, so I call it aborted. Is
'skipped' a better name ? The fact is that now the last sf version is
1
>
>Will do, but will 1.3.9.1 be ever published on sf ? When ?
>
>Or it's been aborted like 1.3.5 and next published version will be
>1.4.1.x ?
Aborted?
Do you propose to publish 1.3.5 or 1.3.9 on SF, even when 1.4.1 is
already ready for primetime?
--
> ASSP 1.4.1 is now closed - code is freezed.
>
> Please help to publish a solid version by replacing 1.3.3,1.3.5 and
> 1.3.9 in your installation.
Will do, but will 1.3.9.1 be ever published on sf ? When ?
Or it's been aborted like 1.3.5 and next published version will be 1.4.1.x ?
Userbase
ASSP 1.4.1 is now closed - code is freezed.
Please help to publish a solid version by replacing 1.3.3,1.3.5 and
1.3.9 in your installation.
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Bu
ASSP development mailing list
schreibt:
>But the sender does not get a non-delivery report.
ASSP never sends a NDR. It replies with the message you set in
AttachmentError.
To see what is going on set the logging option: SMTP Status Code Reply
Logging (replyLogging).
---
Hello @all!
Unfortunately maybe I found a misbehaviour handling blocked attachments:
Blocked or not allowed attachments are found and CC as wanted to my Spambox.
But the sender does not get a non-delivery report.
The postfix log on my ASSP machine says that the connection is lost:
"postfix/smt
>> [Attachment][scoring]
> is logged when you check "suspicious attachments". Do you?
on a second thougth... I see an entry for "suspicious attachments"
containing "gif|pdf" but no flag to disable such a check; will it
suffice
to remove the contents of "SuspiciousAttach" to avoid that error (for
GrayHat <[EMAIL PROTECTED]> schreibt:
>uh, no, sorry Fritz, I meant ASSP logs that error but doesn't crash
>one more strange thing; I've the attachment filtering set to "block"
>yet ASSP logs an "[Attachment][scoring]" followed by one of the
>errors I reported; the error line is usually 9401 althou
>> error: unable to parse message for attachments - Can't locate object
>> method "new" via package "Email::MIME" at c:\assp\assp.pl line 9380.
> it bombs, you mean it crashes?
uh, no, sorry Fritz, I meant ASSP logs that error but doesn't crash
one more strange thing; I've the attachment filterin
It would be nice if you just do it and send me the proposal.
fritz
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
>Please help in improving the GUI:
>
>http://www.magicvillage.de/~Fritz_Borgstedt/assp/0001CD85-801C/
I'd suggest using and html lists in your code, where possible.
For example, redRe shows up as a jumble of lines because it only uses
line breaks:
It could use BOTH paragraph AND numbered
GrayHat <[EMAIL PROTECTED]> schreibt:
>now... ASSP (1.4.1.0.32) still bombs with errors when it
>comes to parsing attachments; the error(s) are:
>
>error: unable to parse message for attachments - Can't locate object
>method "new" via package "Email::MIME" at c:\assp\assp.pl line 9380.
it bombs,
> ASSP 1.4.1 seems to be ready for prime time ))).
Fritz... about Email::MIME::Modifier... I tried a search..
ppm search Email::MIME
and the search returned this
1: Email-MIME
Easy MIME message parsing.
Version: 1.8
Author: Simon Cozens ([EMAIL PROTECTED])
Provide: Email::MIME versi
>With this last fix ASSP 1.4.1 will become the current stable and
>closed version (if successfull).
>
>Email::MIME::Modifier required for attachment detection!
>- new - all (not only the first) attachments within
>MaxBytes/ClamAVBytes will be detected and processed!
>
>Please everybody who does
> I tried 1.4.1.0.28 now with Email::MIME::Modifier installed
> and sent some test messages.
Just to add a little bit of infos, I installed the latest 1.4.1.0.29
and while looking at the maillog tail here's what I found:
Aug-4-08 18:08:22 msg-66094-09742 [Attachment][scoring] 212.19.106.178
<[EMA
Good morning Fritz!
Many thanks for your support!
I tried 1.4.1.0.28 now with Email::MIME::Modifier installed and sent some
test messages.
Attachment blocking is still on Level 4 for all, but e.g. a file "test.mgg"
went through. The extension is definitely not on the list of allowed file
extensi
Is it me, or is there an old version put back in 1.4.1 ? (0.12)
Op 2 aug 2008, om 21:34 heeft Fritz Borgstedt het volgende geschreven:
>
>> Can we forward multiple messages to the email
>> interface now instead of one at a time?
>
> You can do that in ASSP 2.0 and 1.4.1
>
>
>
>Can we forward multiple messages to the email
>interface now instead of one at a time?
You can do that in ASSP 2.0 and 1.4.1
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest
>Can we forward multiple messages to the email
>interface now instead of one at a time?
You can in ASSP 2.0
fritz
-
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux bas
Is this only for attachment blocking or is this going to affect the
email interface as well? Can we forward multiple messages to the email
interface now instead of one at a time?
Fritz Borgstedt wrote:
> With this last fix ASSP 1.4.1 will become the current stable and
> closed version (if succes
Fritz Borgstedt wrote:
> With this last fix ASSP 1.4.1 will become the current stable and
> closed version (if successfull).
>
> Email::MIME::Modifier required for attachment detection!
> - new - all (not only the first) attachments within
> MaxBytes/ClamAVBytes will be detected and processed!
>
With this last fix ASSP 1.4.1 will become the current stable and
closed version (if successfull).
Email::MIME::Modifier required for attachment detection!
- new - all (not only the first) attachments within
MaxBytes/ClamAVBytes will be detected and processed!
Please everybody who does attachmen
23 matches
Mail list logo
