Thank you very much for the update :)
Max
On 06/28/2011 11:43 AM, Thomas Eckardt wrote:
> Hi all,
>
> fixed in 2.0.2_3.1.10:
>
> - A code change in 3.1.04 for adding our header lines has caused in some
> cases that the mail header was destroyed. So the MIME content was no
> longer valid.
>
> Tho
t; ASSP contains no code that changes the Content-Type - we change the
> Transfer-Encoding to 'base64' if we create an DKIM signature for a HTML
> message
>
>> Did I miss an upgrade of some module
> No - nothing has changed.
>
> Thomas
>
>
>
>
Hi Thomas,
were running 3.1.06 for a while and noticed that character conversion
for umlauts was wrong when sending mails using utf-8. (displaying only
in hex)
And at least when using iso-8859 for the outgoing mail, any text/html
mail got scrambled.
The Mailheader was:
content-Type: text/plai
On 04/05/2011 07:21 PM, Fritz Borgstedt wrote:
> ASSP development mailing list
> schreibt:
>> Couldn't all the regex files in the asspv1 directory generally be
>> used
>> with asspv2 too?
>
> No. This will be decided by Thomas. The regex code in V2 is much more
> advanced.
>
Thanks!
On 04/01/2011 12:15 PM, Fritz Borgstedt wrote:
> There is new file bombsubjectre.txt ->
> http://assp.cvs.sourceforge.net/viewvc/assp/assp/files/
> The content can be used in ASSP V1 and V2, please try it.
>
Hi Fritz,
thanks very much for the update!
Couldn't all the regex files in the asspv1 dir
Thanks Fritz,
what would be a good value for MaxErrors? You suggested '3'. Was this
suggestion based on my example or was it a more general recommendation?
BTW: I set it to '2' for a trial, but 1 hour later a similar mail
slipped through.. maybe I should have restarted ASSP, will watch out if
Thanks Fritz, didn't think that invalid recipients count as smtp session
errors.
Any reason to not set this value to 2 instead of 3? What do you think?
On 03/10/2011 03:26 PM, Fritz Borgstedt wrote:
> ASSP development mailing list
> schreibt:
>> I found MaxVRFYErrors, but considering the help t
Hi,
Lately more spam passed and I noticed that many of those mails were sent
to invalid local recipients besides one or two valid ones.
i.e. To: validu...@example.com, Cc: invalidus...@example.com,
invalidus...@example.com, invalidus...@example.com
I found MaxVRFYErrors, but considering the hel
Thank you very much for your quick answer and the workaround! ;)
On 02/24/2011 08:15 PM, Thomas Eckardt wrote:
> I'm sorry - used a wrong verification string - meanwhile define the
> servers as x.x.x.x:53
>
> Thomas
>
>
>
> Von:"m...@mailspot.at"
Hi Thomas, thanks for the Update.
I got the following problem though:
After the upgrade from .19 assp doesn't validate any configured dns
servers anymore sucessfully and always reverts back to some opendns
servers..
I downgraded and everything's working again.
Greets,
Max
On 02/24/2011 12:
Ok, everything's clarified ;)
Thanks, have a nice evening.
On 11/10/2010 05:59 PM, Fritz Borgstedt wrote:
> ASSP development mailing list
> schreibt:
>> I downloaded the Razor Plugin from there, but it complains about the
>> version.
>
> # This is a ASSP-Plugin for Razor2 detection.
> # Designed
Thanks Fritz,
On 11/10/2010 03:18 PM, Fritz Borgstedt wrote:
>
> # This is a ASSP-Plugin for Razor2 detection.
> # Designed for ASSP v 2.0.2(1.2.15) and above
>
> 2.0.1 (odd) is the stable version
> and can be found at ASSP V2:
> http://sourceforge.net/projects/assp/files/ASSP%20V2%20multithread
Hi,
Thomas: any news about this email causing assp to hang?
It's been a while. I haven't changed anything in the config, but since
adding this sender to noprocessing, no worker has ever been stuck
again.. there must be something about that mail.
And sorry for asking again, but is the razor pl
istake I had done
in the uribl config (socket timeout was set to an insanely high value.)
BTW: about the razor plugin: I wanted to try that out, when I look at
the release notes for version 2.0.1 it's mentioned, but it doesn't load
because it says version 2.02 is needed.. is this a m
Thanks for your answer,
I didn't send it to Fritz or Thomas yet since I'm not sure if they'd
love to get mails from anyone without any demand/notice.
If they don't mind I'd happily provide it to Fritz or Thomas.
Thanks,
Max
On 10/29/2010 06:45 PM, Charles Marcus wrote:
>
> Did you provide
Since I added this sender address to no processing, no worker has been
stuck.
It would still be nice to know what about this mail could have caused
assp to hang..
On 10/27/2010 05:35 PM, m...@mailspot.at wrote:
>
>Ok, got the Mail..
>
> X-Mailer: Microsoft Office Outlook
It appears that it's only one specific mail causing this.
It's definately ham and periodically comes in through the backupmx,
since it failed.
I temporarily added the ip to noprocessing ips to get the mail.
Could it be some strange attachment/encoding? I already disabled the OCR
plugin just
Hi,
it would be great if someone could help me out with this.
I'm currently running 2.0.1(1.2.21). BTW: does this version belong to
assp-user or assp-test?
Unfortunately since installing that version I get stuck workers at least
once per hour:
These are the corresponding log lines:
27-10-
Sorry very, VERY sleepy and tired didn't realize what Thomas posted,
I'll report back
On 09/17/2010 11:02 PM, m...@mailspot.at wrote:
>
>Ok, so here it is ;)
>
> BTW: as I already mentioned, a downgrade to 2.02 (1.2.10) works.
> If I shall post everything, just te
Ok, so here it is ;)
BTW: as I already mentioned, a downgrade to 2.02 (1.2.10) works.
If I shall post everything, just tell me.
ASSP 2.0.2(1.2.11) is starting in directory /usr/share/assp[ OK ]
on host mail.mailspot.at
using Perl /usr/local/bin/perl5.10.1 version 5.010001 (5.10.1)
r...@ma
Hi,
thanks for the update.
However ASSP doesn't startup for me since it updated. Couldn't create
listen socket et.c.
Sounds like the problem long time ago where ASSP changed to its
unprivileged uid/gid before starting to listen.
After downgrade to .10 it does work again.
Thanks,
Max
On 09
thanks a lot for the enlightenment Fritz and Charles,
well you see I'm all new to this.. sorry
On 05/24/2010 01:17 PM, Fritz Borgstedt wrote:
> ASSP development mailing list
> schreibt:
>
>> I noticed that when I use catch all for mails addressed to non
>> existent
>> recipients (not in LDA
I noticed that when I use catch all for mails addressed to non existent
recipients (not in LDAP et.c.), the sender wouldn't get any mail returned.
This might be intended, maybe I missed an option or I have a problem
with my setup.
However this could be a problem since sometimes it happens that
Hi,
thanks again for those many new features and fixes!
Is the pers whitelist optional, i.e. will mail sent to the outside by
any user still be added automatically to the global whitelist? Do pers.
black/white -lists only come to effect by using the mail interface?
Do addresses on user's A pe
Thanks for the Update!
I got a problem though I never had with any version before..
After upgrading to 04, I noticed that assp won't listen on 25 and 465
anymore.
In the logs:
Couldn't create server socket on port ':25' -- maybe another
service is running or I'm not root (uid=500)?
another proce
Thanks to everyone for helping me out!
Now I know what was wrong.. stupid me had set a very high limit to
URIBLMaxTime.
I can't remember how that happened or why I did that as I have only 3
uribl providers in use anyway.
After changing the value to default settings of 10 seconds, "worker
stuck
Hi,
sorry for the extra mail, but thought it's best to share some more info:
After getting rid of ldap lookups and trying smtp vrfy the issue still
remained, so I did the following:
I emptied the textbox for db entry in file paths/DB for LDAP, disabled
smtp vrfy, put @mydomain in addressesflat
27 matches
Mail list logo