> Hi all,
>
> fixed in assp 2.1.2 build 11352:
Thanks Thomas,
Facts: ASSP gets better on every release!
1) Performance is faster (my benchmarks on ASSP go back to 3 years past).
2) Less Spam at the end user 'pipe-line' drop point.
3) Better database and [bad email crash] processing.
4) Good use
> Hi all,
>
> fixed in assp 2.1.2 build 11345:
>
> - If assp is used as a generic transparent TCP-proxy, and an allow-IP-list
> is defined and an IP-group
> is used in the allow-IP-list - the config watch code has done wrong
> scheduling or caused an exception in the
> worker.
>
> - the module v
> Hi all,
>
> fixed in assp 2.1.2 build 11337:
>
> - build 11336 fails to start on NIX systems
Many thanks Thomas,
Latest ASSP 2.1.2 build 11337 is operative on Linux!
[+1]
Peter
--
All the data continuously genera
> Hi all,
>
> fixed in 2.1.2 build 11336:
Hi Thomas,
ASSP 2.1.2 build 11336 has 'broke' Linux support:
error = 'fails to start'
Linux Log shows this:
--
: assp.service: control process exited, code=exited status=1
: Unit assp.service entered failed state.
: PID 3
> Hi all,
>
> fixed in assp 2.1.2 build 11320:
>
> - improved OIP detection
> - wrong collection folder 'notspam' was used after a mail was stored in
> 'discarded' folder
> - a malformed header end sequence caused an destroyed mail header after
> our own header was added
>
> Thomas
Noticed this i
> Hi all,
>
> fixed in assp 2.1.2 build 11319:
Many thanks!
Looks good so far Thomas!
Testing it heavily now under my fully updated Fedora 15 Linux!
"ASSP-professional version 2.1.2(11319) (Perl 5.012004) (on linux)
initializing"
Peter
-
> Hi Peter,
>
> Yes, I have all these set...the only one I'm not sure of is:-
> 3) database driver name (DBdriver)...Do I type "InnoDB" in there or
> "mysql[,PORT=3306]"...?
>
> Many thanks
> Steve
---
Hi Steve,
Just to be sure you
> Hi Peter,
>
> Yes, I have all these set...the only one I'm not sure of is:-
> 3) database driver name (DBdriver)...Do I type "InnoDB" in there or
> "mysql[,PORT=3306]"...?
>
> Many thanks
> Steve
Hi Steve,
The ASSP 'database driver name (DBdriver)'
is set to: mysql
('true' in my case; and lik
> Getting furtherbut still errors
>
> Oct-30-11 06:56:33 [Worker_1] Whitelist database error: Can't connect to
> data source 'dbi:InnoDB :database=assp;host=172.16.16.20' because I can't
> work out what driver to use (it doesn't seem to contain a 'dbi:driver:'
> prefix and the DBI_DRIVE
>Peter, let's do an example:
>
>I assume : for MaxFiles = 13000 -> 13000 files in each, spam and notspam
>and ~3000 files in each of both error locations - >2GB is not enough!
>
>Currently the HMM uses 4 BDB's with in sum ~ 100MB for ~3000 files (in sum)
>on my test system - looks OK.?
>
>The lo
> Holding the HMM in memory requires up to 2GB RAM
Thanks Thomas,
HMM seems great; I am quoting here:
"In all those cases (100%) HMM was right and Bayes was wrong"
But why the 2Gb of memory? Is the DB that large?
Quoting again:
"Currently the HMM uses a very flat logic -
to hold the
> >(as happens when Thunderbird prompts the user to accept a
>>self-signed cert) is not best practice.
>
> This is done by Net::SSLeay (OpenSSL) - not by assp and it works perfect
> with other clients. ASSP simply detects that an unrecoverable (one more
> retry attempt for each connection) error o
> Wasn't suggesting it should be disabled, I was suggesting that maybe
> refusing to continue to offer STARTTLS/SSL because of one, temporary
> 'failure' (as happens when Thunderbird prompts the user to accept a
> self-signed cert) is not best practice.
>
> Postfix, Exchange Server, web server
>>There is absolutely nothing wrong with a smaller company using
>>self-signed certs, so ASSP should allow for this to work... period...
>Using SSL in a bigger company is more than doing some clicks.
>- create CA and keys
>- cert server
>- key and or certificate deployment
>- centralized ce
Good idea: K Post!
I will glady award you 20 cents! (what 2 cents)
Most of us IT 'support' guys and gals have so much
'extra' support code to mange and chase that it makes
ones's head spin to keep up with 100's of code updates -
simply for offering web related services: Linux, Windows,
Mac OS X,
Great work Thomas!
I notice that http://assp.cvs.sourceforge.net/viewvc/assp/assp2/
now shows this;
1) changelog.txt 1.177; @ 43 minutes;
version 2.1.2 build (11277) requires Perl 5.10 at least recommended is Perl
5.1.
-and -
2) changelog_2.0.X.txt 1.1 @ 59 minutes;
version='2.0.2'; $modversi
Hi Paul,
ASSP 2.0.2_3.3.01
Not so hard to find, it is in the ASSP GUI,
under 'infostats' then choose 'beta' [link].
To save your time, this is the link to the Devel ASSP
site: (and I actually used this method yesterday' to
update my ASSP to the latest) modversion = 3.3.01
http://assp.cvs.sourc
Many thanks Thomas,
"A very fast resolve on your part"...
Results / reports looks good so far!
As always, ASSP 'rocks' with mail protection needs!
"You win another gold star and a sweet choc. cookie"...
Peter
- Original Message -
From: "Thomas Eckardt"
To: "ASSP development mailing
Thomas,
Here are two ASSP 'maillog.txt' entries capturing
sections around 2 error logs for this:
[1]
>>
[Worker_1] Info: Name Server 210.23.129.34: ResponseTime = 43 ms
[Worker_10001] Info: notification message queued to sent to
supp...@pbco
Hi Thomas,
Using Assp 2.0.2_3.2.28, I received the
following entries in ASSP's emailed logs
This 'event' occurred 5 times today..
Message is:
>>--
log event on host ASSP.nospam:
error: untie attempted in orderedtie while 1 inner references still
Hi Thomas,
Log Report: using "assp 2.0.2_3.2.27"
>>-
log event on host ASSP.nospam:
error: untie attempted in orderedtie while 1 inner references still exist
-<<
Pete
Many thanks GreyHat,
That is some very useful information!
Kind of email 'Honey Pot' for the 'bears'
Peter
- Original Message -
From: "GrayHat"
To:
Sent: Monday, August 22, 2011 10:02 PM
Subject: [Assp-test] Simple yet effective (imHo) idea
> Hello all; I've been running ASSP for q
> No. It did not show that. Would you please be so kind to read the logs
> which are in the first posting of this thread and to read the
> introduction of enhancedOrigin feature from Thomas:
>
> The log entry in the starting mail was:
>>
>>Aug-03-11 08:32:04 [Worker_1] [TLS-in] [DenyStrict] 216.3
> I have seen it... I SCORE on certain BLs, but only block on the very
> reliable ones that quickly delist (WITHOUT charging extortion) once an
> offender fixes their problem.
Many thanks Charles,
On my dedicated Linux Server www + mail, I run
a clean ship and have NEVER caused or
personally rai
> No it is not your report, but you commented and explained it. And your
> explanation for this case was questionable and will not help the
> reporting user.
>
> ASSP uses ALSO DNSBL lookups for IPs on the mail route, but it uses
> also manually maintained blocklists (in V2 only) like
> denySMTPC
> Like I said, anyone who blocks on a BL that requires payment for removal
> gets what they deserve.
Charles,
Sorry, but that is a non-realistic statement!
Thanks to ASSP, I no longer need be *penalized*
by my client's broken and sick computers!
Are you in IT support?
I would suspect not?
Othe
Hi Fritz,
This is a bit tiresome, but it is NOT my report
about ASPP *logs*.
I am just one of 'many' that noticed the recent ASSP
change and accept it based on good facts!
Logs or not, I think the fact that ASSP uses Balcklists
origins as it does is GOOD. Amen!
Thanks Thomas, I like this prot
>> However, the 'removal' from a officail black list IP
>> is SLOW (days), unless you pay a up-front fee to
>> the Blacklist site.
>
> Not true except for a few ones that I would never block on...
>
> Most have a delisting process that you must follow, but do NOT charge
> for it...
>
> --
>
> Bes
Sent: Wednesday, August 03, 2011 11:16 PM
Subject: Re: [Assp-test] This is now becoming a joke
> The problem her was NOT a blacklist. It happened because entries were
> put manually into denySMTPConnectionsFromAlways lin the form of
> 14.0.0.0/8.
Fritz, 'thanks' but the given mail site [giv
>Thanks, I worked that out myself...:)
>I'm surprised that MS still gets blacklistedmust happen hourly...
Hi Steve,
A new mail host blacklisting usually kick's in hourly!
It depends on the DNS TTL.
However, the 'removal' from a officail black list IP
is SLOW (days), unless you pay a up-fr
> Thanks
> Steve Moffat
> Operations Director
> Optimum IT Solutions
Sorry Steve,
the syntax of my last mail was a little wrong!
..I have been typing too fast, with too much
to do (grin)!..
The correct url path for checking email IP's
is like this: (next line)
http://www.robtex.com/ip/216.32.1
> Thanks Peter
>
> Any idea why it just seems to have kicked in a lot recently? By recently
> I mean in the last week.
>
> Thanks
> Steve Moffat
> Operations Director
> Optimum IT Solutions
Hi Steve,
Well, simply because the latest ASSP devel version
has 'improved' it's mail protection methods
>I have turned off denystrict for the moment
>
> Steve
Hi Steve,
To clarify, on your previous email!
Quote: " [DenyStrict] 216.32.180.12 to:
ksm...@bldc.com blocked by denySMTPConnections or droplist strict:
14.0.0.0/8"
That email has an entry on a blacklist!
Here is the report:
Test
> Hi
>
> I sent a mail yesterday regarding these log entries and no reply yet. It's
> getting beyond a joke now. I am seeing these lines in the log more & more
> often
> What is the issue here?
>
> ASSP version 2.0.2(3.2.10)
>
> Aug-03-11 08:31:27 [Worker_1] Info: Name Server 192.168.175
> The problem is solved - thank you.
>
> Thomas
>
>
>
> Von:Thomas Eckardt
> An: ASSP development mailing list
> Datum: 31.07.2011 12:04
> Betreff:[Assp-test] help wanted for word stemming
>
>
>
> Hi all,
>
> I'm currently working on a word stemming engine for the assp - Bayesia
>>-
>> 1) What type of IP's will be ignored by this new filter?
>>-
>
> A) In general (for now):
>
> IPprivate
> ispip
> acceptAllMail
> whiteListedIPs
>
> Hi all,
>
> fixed in 2.0.2_3.2.06:
>
> - the enhanced mail routing IP-address-detection now cares about
> blacklisted dynamic IP-ranges (like pbl.spamhaus.org) and skips this IP's
> on the DNSBL check
> - strange output on orginating HELO detection in 2.0.2_3.2.05
>
> Thomas
Hi Thomas,
I am ve
> Perl 5.10 is now over 4 years "old" and Perl 5.12 over 2 years.
> As I wrote: 5.10.0 is required - at least 5.10.1 is recommended - 5.12.x
> and 5.14.x are supported.
Thank Thomas,
Centos and RH traditionally lag behind on the policy of using Nix 'new
releases'.
They both prefer to patch old
> Hi all,
>
> with the next release, there is no longer any garantie that assp.pl will
> run under Perl 5.8.8 on darwin.
> I'll do my best to keep assp.pl working on 5.8.8 to the end of this year -
> but who knows?
> Anyone who is using Perl 5.8.8 should switch off the autoupdate feature -
> do ma
> Nothing better than this, Peter. The best would be, if the CA is not
> needed. I think most of the assp users will not see a crash - but this
> highly depends on the setup(used features), own regexes (mostly)...
>
> There are some rules, which will lead it to a high spam detection rate and
> les
> >Why the given 'variance / gap' between
>
> - testing/detecting on the part that is most times 'OK' is more safe - the
> CA should NEVER! crash assp.
>
>>Is this a 'limit' in the current CA process / detection? >>body<<
>
> Call it a 'limit' - there are more than one 'limit'.
>
> - the current
> And the CA could never be perfect - the reason is simple - CA tries to
> detect bad mails on there header content and the used handshake protocol,
> but in 99.99% of all cases the body was the reason for a crash.
>
> Thomas
Hi Thomas,
Why the given 'variance / gap' between CA detecting 'bad' m
> changes in 2.0.2_3.2.02:
>
> - assp now dowloads in addition to the version.txt and assp.pl.gz the
> last
> changelog.txt to the >>docs folder<<, if the autoupdate feature is used
> - links for the current local and the current downloadable
> changelog.txt
> are now shown in the 'Infos and Stat
Hi Thomas,
The latest ASSP 2.0.2_3.2.02 is working well here.
1) Regarding the 'new format' for 'autoupdates' to 'include' the
[changelog.txt] file...
In this case, I note that this asset downloads 'automagically' into
the ASSP folder /docs rather than the original ASSP base dir '/'
> changes in 2.0.2_3.2.02:
>
> - assp now dowloads in addition to the version.txt and assp.pl.gz the last
> changelog.txt to the docs folder, if the autoupdate feature is used
> - links for the current local and the current downloadable changelog.txt
> are now shown in the 'Infos and Stats' -> 'Se
>Afaics Fritz and Thomas are doing their utmost to let ASSP to be the best
>anti spam solution available, so don't bother them with this stuff, they
>do a lot work already which i appreciate a lot!
ASSP team;
ASSP is likely 'already' the best, and I am indebted to the work of
Fritz and Thoma
> >Is it 'valid' for the ASSP developers to vote on 'user issues'?
>
> At least we have to do the stuff - and not to forget - we are also users.
> So it seems to be legal for us to vote. Btw. ask Fritz - it has taken him,
> Matti and Pascal over a month or even more to get the things working on S
> The next release will also download the changelog.txt from SF to the docs
> folder, if the autoupdate feature is configured and changes are made.
> And there will be a link right beside the assp version ( 'Infos and
> Stats'->'Server Information'), which will show the current local
> changelo
> ASSP development mailing list
> schreibt:
>>my voting: -1
>
>
> total: -2
>
> Fritz
> total: -2
>nein, -3 :D
Thanks ASSP Team -but-
Is it 'valid' for the ASSP developers to vote on 'user issues'?
P:)
--
All o
> add my -1 too, please :) see, I think you forgot to add
> another point; in a past there WAS an ASSP own site
Thanks good ASSP Team - 'but' -
"Is it 'valid' for the developers meant to vote on 'user issues' "?
P :)
-
> A *real* live website dedicated to ASSP would be very excellent!!!
>
> I would help support that community spirit, for ASSP is so +good+
Many thanks to Thomas Eckardt, GrayHat, and Fritz Borgstedt
for clarifying ASSP support levels - all from the good devel team!
The point to be made 'clearer'
> >I had to 'fight' this text out of 'sourceforge' resources:
>
> This URL is the same for several years now - you should keep my changelog
> postings - or read this text before EVERY update.
>
> Thomas
Hi Thomas,
Many thanks!
Fact is that your friend 'sourceforge' is a slow + painful critt
> What else do you want /need to know about the crash analyzer in addition
> to the changelog of 2.0.2_3.1.08?
>
> Thomas
Well **finding** the 'changelog of 2.0.2_3.1.08' would be a good start!
So for the *sake* of others reading this, here it is:
I had to 'fight' this text out of 'sourceforge'
> The 'crash analyzer' has reached the 'experimental' state. It could be
> used in production mode. How ever, it has to be configured via commandline
> parameter or 'CorrectASSPcfg.pm' (see the change log for 2.0.2_3.1.08 -
> experimental).
> The crash analyzer is disabled per default.
Many thank
> It's just a feeling, but I've not seen assp freeze or otherwise go down
> for months, except until somewhere around these two versions. Also, my
> e-mail client has been having a tough time with the server. It MIGHT be
> due to my internet connexion, which has been a little less reliable,
>
Using ASSP 2.0.2_3.1.10
The 'fraud bank mailers' are escalating, I see ASSP pass most of these;
about 10 per day!
Once, it was only 2 per week that slipped through ASSP?
Is anyone else seeing this fraud bank spam increase?
Peter
-
> 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.
>
> Thomas
Hi Thomas,
Since using the latest ASSP 2.0.2_3.1.10, I have noticed a large increas
> Hi
>
> Has anyone else seen their loads increase after upgrading to 3.1.10?
>
> Thanks
>
> Dale
For me on Linux 64-bit, ASSP 2.0.2_3.1.10 is stable at load average: 0.02,
0.10, 0.12
Though 'top' does show 'perl' is busy with the following resource use:
PID USER PR NI VIRT RESSH
> Hi all,
>
> I've done some tests on Dales system (CentOS) using the AsspSelfLoader.pm
> version 2.01 . With the enabled SelfLoader the system was crashing several
> times a day without any notice.
> This issue is still under investigation.
> I never saw that behavior on my systems, but I'm able
Sent: Saturday, June 25, 2011 6:46 PM
Subject: [Assp-test] attachments cause crash ?
> Hi all,
>
> in the last days I saw some crashes of V2 (Perl process ends without any
> action to see). These crashes are possibly caused by attachment
> MIME-headers like this one
>
> --000e0cd3ff9291e4f704a6
> Sorry - I was some days offline (relaxing in Spain). Don't worry - this
> is a bug in assp - will fix it today.
>
> Thomas
Thomas,
I am relieved you had some rest time away from ASSP issues. :)
I know you place a lot of good effort - supporting ASSP 'niggles'.
Peter
---
>>> Worker_3: Not a SCALAR reference at assp.pl line 20526
>>
>> Grepped the logs to find any "Not a SCALAR" and the grep
>> found nothing at all; as for the rebuild, it's running fine so I tend
>
> I stand corrected, I *HAVE* those messages, just... they're
> inside the "exceptions.log" file sitt
>> Well turning off dodomaincheck got rid of all the
>> error messages so it is related, are you guys
>> using this ?
>
> in my case, I have (from assp.cfg)
>
> DoDomainCheck:=3
In my case I also have; "DoDomainCheck:=3"
Listed as found in; "assp.cfg"
Peter
---
> GrayHat & Peter,
>
> What are the Perl versions you are using ?
Though Linux perl -v reports this:
"This is perl 5, version 12, subversion 3 (v5.12.3) built for
x86_64-linux-thread-multi"
The previous email response was what ASSP reports in the log..
Peter
---
> GrayHat & Peter,
>
> What are the Perl versions you are using ?
Answer:
ASSP version 2.0.2(3.1.05) (Perl 5.012003) (on linux)
Peter
--
EditLive Enterprise is the world's most technically advanced content
authoring t
>> Hi,
>>
>> I don't think this is a local issue. I get the same amount and type of
>> errors, like dale. Downgrading to 3.1.0.1 for example does not
>> generate these errors.
>
> Pascal, don't take it as a "personal" issue, please, I'm just trying
> to be of help; I'm running the latest v2 (.05)
>> Worker_3: Not a SCALAR reference at assp.pl line 20526
>
> Grepped the logs to find any "Not a SCALAR" and the grep
> found nothing at all; as for the rebuild, it's running fine so I tend
> to suspect that the issue may be somewhat "local" to your
> setup... which means that you may start by t
> Hi all,
>
> fixed in 2.0.2_3.1.04:
>
> - the mailloop detection was not working
> - some X-ASSP- header lines are added multiple times
>
> changed:
>
> - free worker detection is improved
Many thanks Thomas,
ASSP has become so much better since ASSP 2.0.2_3.0.24..
No problems seen here - "
> Hi all,
>
> fixed in 2.0.2_3.1.02:
>
> - ReservedOutboundWorkers was no more working since 2.0.2_3.0.24
> - unexpected restarts without writing an exception log since 2.0.2_3.0.24
> - unexpected high memory consumption since 2.0.2_3.0.24
Thomas,
The latest ASSP 2.0.2_3.1.02 has been running so
> On 2011-06-02 9:46 AM, Peter W Bowey wrote:
>> I have done some benchmarks on this latest ASSP 2.0.2_3.1.02.
>> Results show performance and memory as being 'lighter and faster'.
>> I am seeing about a 20% improvement in mail processing times.
>> Linu
> Hi all,
>
> fixed in 2.0.2_3.1.02:
>
> - ReservedOutboundWorkers was no more working since 2.0.2_3.0.24
> - unexpected restarts without writing an exception log since 2.0.2_3.0.24
> - unexpected high memory consumption since 2.0.2_3.0.24
Thomas,
I have done some benchmarks on this latest ASS
> Hi all,
>
> fixed in 2.0.2_3.1.02:
>
> - ReservedOutboundWorkers was no more working since 2.0.2_3.0.24
> - unexpected restarts without writing an exception log since 2.0.2_3.0.24
> - unexpected high memory consumption since 2.0.2_3.0.24
Many thanks Thomas,
The latest ASSP version 2.0.2(3.1.02
> Deleted pid file.. Rebooted.. All ok.. What happened
Gary,
When ASSP 'crashes' it sometimes does not have chance to remove the pid
file.
Removing it manually is often required for a ASSP fatal crash.
I understand that *all ASSP logs* go into the one log file.
The ASSP alert "Abort forced b
Grayhat,
> I'm not sure the issue is easy to reproduce since it may be (and imho
> probably is) caused by a number of factors (config settings, filter
> files...)
I inserted the given IP into ASSP's "ASSP Mail Analyzer:"
This is the result status:
Connecting IP: 91.189.90.139
Feature Matching
> Do you have a *nix box, and do you have fail2ban installed?
Many thanks Trevor,
Yes - Linux (Fedora 14 64-bit), but not yet with fail2ban.
I have added the given email 'boun...@canonical.com' to ASSP's [preHeaderRe]
Now monitoring the resuts - very deep.
Peter
---
The given incoming 91.189.90.139
will sometimes fire up to 3 attempts per second, stop for minutes break then
resume.
As I have had this IP severely blocked on the ASSP's 'PenaltyBox Extreme'
list for some time,
I think this should be 'good enough'.
Thoughts please
Peter
Thanks Trevor J,
I note that the latest (*.dev) ASSP 'crash' usually occurs with the last
contents of my ASSP logs showing this info:
--
[Worker_1] 91.189.90.139 info: found message size
announcement: 10.20 kByte
[Worker_1] [denyExtreme] 91.189.90.139 connection
from 91.189.
Hi Thomas,
The last 2 *.dev releases of ASSP actually do 'crash like a very bad
tempered
pig'.
I have had to rebuild a corrupted /tmpDB folders twice in one day!
EG: removed all '__db.00*' DBD files - simply because the ASSP informed
that all DBD locks were used?
Additionally, I now have a A
Add a 'coffee maker' too and a back massage device
Seriously, thanks for all the support you have given us ASSP users Thomas.
It is, really appreciated!
Peter Bowey
- Original Message -
From: "K Post"
To: "ASSP development mailing list"
Sent: Wednesday, May 25, 2011 12:24 AM
S
ASSP 2.0.2_3.0.21
Another noted problem showing in the ASSP Logs:
"AdminInfo: GroupsFile download failed: Cannot create"
Peter Bowey
- Original Message -
From: "Thomas Eckardt"
To: "ASSP development mailing list"
Sent: Wednesday, May 11, 2011 2:14 PM
Subject: [Assp-test] fixes in 2.
Thomas,
My ASSP log report running ASSP 2.0.2_3.0.21
I chose to run ASSP Web GUI RunRebuildNow
--
log event on host ASSP.nospam:
error: coding error: config value is not equal config hash in
RunRebuildNow - please report to development!
---
That might suggest that the new regex is too greedy.
Some regex's are a hazard for Perl.
Peter
- Original Message -
From: "Michelle Dupuis"
To:
Sent: Wednesday, April 20, 2011 7:02 AM
Subject: [Assp-test] Regex causes 100% CPU?
>I had a discussion going yesterday about the right reg
Hi Fritz,
Thanks, earlier today, it was proven through the use of a test script that
the problem originates from the Windows use of CPAN's Net::DNS::Resolver.
The setup of ASSP's 'DNSServers' was checked.
It is likely a bug with the Windows use of Net::DNS
Quote: "On Windows systems, an attempt
esolver->new;
>> my $query = $res->query("example.com", "NS");
>>
>>
>> if ($query) {
>> foreach $rr (grep { $_->type eq 'NS' } $query->answer) {
>> print $rr->nsdname, "\n";
>> }
com", "NS");
>
>
> if ($query) {
> foreach $rr (grep { $_->type eq 'NS' } $query->answer) {
> print $rr->nsdname, "\n";
> }
> }
> else {
> warn "query failed: ", $res->errorstring, "\n"
If you are using BIND (Named) you should have something like this:
--
view internal {
match-clients { lan_hosts; }; # match hosts in acl "lan_hosts"
recursion yes; # allow local recursive queries
notify no; # disable AA noti
;, "NS");
>
>
> if ($query) {
> foreach $rr (grep { $_->type eq 'NS' } $query->answer) {
> print $rr->nsdname, "\n";
> }
> }
> else {
> warn "query failed: ", $res->errorstring, "\n&qu
lookup
> works fine)...
>
> Could this by a Windows vs Linux thing? Is ASSP using a function call
> that isn't returning IP addresses in the format expected?
>
> From: Peter W Bowey [supp...@pbcomp.com.au]
> Sent: Friday, April 15, 2011 7
That is a strange DNS => "Name Server p�"
It should reflect your actual system DNS IP(s), so what is this weird "p�"
?
When I get a DNS error related to ASSP it looks like this "warning: Name
Server 210.23.129.34: does not respond or timed out"
or if DNS is not responding then you do see the
Looks Good!
Thanks Fritz for all your efforts to ASSP users / implementers!
Peter
Peter Bowey Computer Solutions
- Original Message -
From: "Fritz Borgstedt"
To: "ASSP development mailing list"
Sent: Friday, April 01, 2011 8:45 PM
Subject: [Assp-test] bombsubjectre.txt
> There is
Yep; all with sincere thanks to the FOLK who gave us (ordinary Linux /
Windows email server PHP / Javascript / HTML morons) ASSP (dpuble duh)!
Peter
Peter Bowey Computer Solutions
- Original Message -
From: "GrayHat"
To: "ASSP development mailing list"
Sent: Thursday, March 31, 2011
Agreed; thomas.ecka...@thockar.com == thomas.ecka...@thockar.com (equality
noted)?
You win the coveted ASSP gold sticker for March 2011.
Seriously, I appreciate the hard work you have done to place ASSP where it
is today!
For me, this means (simply), that I do not have to see about 600 spammy
Martin,
I had the same ASSP issues until it did this;
---
SMTP Secure Listen Port (listenPortSSL) = 'none'
SSL Destination (smtpDestinationSSL) = 'none'
Second SMTP Listen Port (listenPort2) = 587
Second
w about?
>
> The [0O]ff regex was suggested years ago to capture Off and 0ff (with a
> zero). That's been there forever, way before this error.
>
>
>
>
>
> On Tue, Mar 22, 2011 at 11:01 AM, Peter W Bowey
> wrote:
>
>>
>> Sorry Ken,
>>
>
t; though,
> why would it always hang on the exact same lines? Being that this is a
> 32bit os, I can't go above 4gb of ram. It running on a machine with a pair
> of dual core xeons.
>
>
> Going back to your original post, was there something specific that looked
> bad i
Hi Ken,
are willing to reduce the number of ASSP workers and try again.
Your recent error report suggest's to me that ASSP workers are dying from
lack of resources [memory].
I run 6 ASSP workers under Linux 64-bit with 8Gb on a 2 x dual-core XEON
server with 8Gb of memory.
The fact that yo
Hi Ken,
Some of that given Regex looks a bit off to me:
Have you checked for ASSP Regex errors at Worker/DB/Regex Status (from the
ASSP Web GUI)?
You should see a 'good' ASSP REPORT something like this:
failed database tables -
Well Google it - and it will become clear enough!
Changes were made some years ago [SLL+TLS]!
Port 465 has been abused and fell from 'grace'
While ASSP still supports this legacy port it is not secure enough for for
any SMTP.
I found this out the hard way, my ASSP [once] died every 30 minutes
Subject: Re: [Assp-test] Antwort: SMTP Secure Listen Port & SSLDestination
issues
> SMTPS is 465, not what you have.
>
> *Port (TCP/UDP): 465 (TCP)
> *Description: SMTP over SSL. TCP port 465 is reserved by common industry
> practice for secure SMTP communication using the SSL
Steve,
I [also] had several issues with that type of ASSP setup too [SMTP Secure
Listen Port & SSL Destination].
My current working setup; for ASSP version 2.0.2(3.0.05):
--
100 matches
Mail list logo
