Please don't knock v2. I'm running it on 3 virtual machines with 512mb ram each, and it runs for months without issues. It's been so stable (for me) I haven't even had time to update them (yes Thomas, I know - sorry)
Steve Sent from my iPhone On 16.03.2010, at 21:07, "Masood Rahim" <mas...@intertune.com> wrote: > > Hey Scott, > > You are not alone. I have V2 running across 4 different linux > servers with > specs that vary and traffic that varies and they are all dying > consistently. > They don't die at all on v1.4.3.1. This is the reason I have stuck > with > that version, because in the past I have updated to the newer > versions of v1 > and they will all consistently die. > > I'm still trying to follow some of the recommendations here. So far > perl > 5.10.1 instead of 5.8.8 has not helped one bit. I'm in the final > stages of > trying to implement the BerkeleyDB stuff although most of the limited > documentation looks like it is written for mysql so who knows if I > will be > able to get that to work correctly. > > As with your case the more the load the more likely assp v2 is > dying. It > just seems like when it gets to a point when the server can no > longer handle > the requests it just dies instead of timing out. I'll make sure the > BerkeleyDB is working and if that doesn't solve the problem I'm > going to > downgrade back to v1. Which sucks because I was really interested > in the > multi-threading, now I'll have to live with slow responses to port > 25 with > v1. > > But anyway this much is certain, same server with the same traffic > and setup > will not die in v1, but will die in v2. I've verified this on 4 > different > machines. I don't think that bodes well for v2. If the ASSP dev team > cannot get things to work where by a simple upgrade and doing > nothing extra > v2 doesn't at least operate consistently like v1 then people are > just going > to keep with v1. I have literally spent the past week trying to > address > these issues with v2 and so far I have gotten nowhere. > > Masood > > > -----Original Message----- > From: assp-test-requ...@lists.sourceforge.net > [mailto:assp-test-requ...@lists.sourceforge.net] > Sent: Tuesday, March 16, 2010 10:15 AM > To: assp-test@lists.sourceforge.net > Subject: Assp-test Digest, Vol 32, Issue 26 > > Send Assp-test mailing list submissions to > assp-test@lists.sourceforge.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/assp-test > or, via email, send a message with subject or body 'help' to > assp-test-requ...@lists.sourceforge.net > > You can reach the person managing the list at > assp-test-ow...@lists.sourceforge.net > > When replying, please edit your Subject line so it is more specific > than > "Re: Contents of Assp-test digest..." > > > Today's Topics: > > 1. Antw: Re: Antw: Re: ASSP2 autoupdate (admin) > 2. Re: Workers STILL stuck @LocalLdapDomain although > using"flatfile" (mxx) > 3. Re: Workers STILL stuck @LocalLdapDomain although > using"flatfile" (mxx) > 4. Re: Workers STILL stuck @LocalLdapDomain > althoughusing"flatfile" (GrayHat) > 5. Re: Workers STILL stuck @LocalLdapDomain > althoughusing"flatfile" (mxx) > 6. Re: Assp dying (Scott MacLean) > 7. Re: Workers STILL stuck > @LocalLdapDomainalthoughusing"flatfile" (GrayHat) > > > ---------------------------------------------------------------------- > > Message: 1 > Date: Tue, 16 Mar 2010 11:32:00 +0100 > From: "admin" <ad...@dc0dam.de> > Subject: [Assp-test] Antw: Re: Antw: Re: ASSP2 autoupdate > To: <assp-test@lists.sourceforge.net> > Message-ID: <4b9f6c300200001300000...@mail.dc0dam.de> > Content-Type: text/plain; charset=ISO-8859-1 > > Yes. > > Could it be, that ?: > > M??r-14-10 12:09:46 Error: Worker_5: error: got unexpected signal > TERM in > Worker_5: package - Thread::Queue, file - > /usr/local/lib/perl5/5.10.1/Thread/Queue.pm, line - 51! > > The same i have with USR1. > > Ralf > >>>> Thomas Eckardt <thomas.ecka...@thockar.com> 16.03.10 10.52 Uhr >>> >> runs as a daemon > > is 'AsADaemon' set to on ? > > Thomas > > > > > Von: "admin" <ad...@dc0dam.de> > An: <assp-test@lists.sourceforge.net> > Datum: 16.03.2010 09:12 > Betreff: [Assp-test] Antw: Re: ASSP2 autoupdate > > > > AutoupdateASSP : Download and Install > AutoRestartAfterCodeChange : 1 > AutoRestartCmd : empty > > AutoRestartCmd is empty because assp runs as a daemon. I start it > from a > shell-script. Here are the Scripts: > --------------------------- assp2 (mainscript) > --- > --- > ---------------------------------------------------------------------- > #!/bin/sh > # > # $FreeBSD: ports/mail/assp/files/assp.in,v 1.1 2006/07/18 03:08:23 > rafan > Exp $ # > > # PROVIDE: assp > # REQUIRE: LOGIN > # KEYWORD: shutdown > > . /etc/rc.subr > > name=assp2 > rcvar=`set_rcvar` > > start_cmd="/var/db/assp2/start" > stop_cmd="/var/db/assp2/stop" > restart_cmd=assp_restart > # command=/var/db/assp2/assp.pl > # command_interpreter=/usr/bin/perl > pidfile=/var/db/assp2/pid > extra_commands="reload" > reload_cmd=assp_reload > > > load_rc_config $name > : ${assp2_enable="NO"} > : ${assp2_flags="/var/db/assp2"} > > assp_reload() > { > kill -USR1 `cat $pidfile` > > } > > assp_restart() > { > /var/db/assp2/stop && /var/db/assp2/start } run_rc_command "$1" > > --- > --- > ---------------------------------------------------------------------- > -------------------------------------------------------------- > > ---------------------------------------- start > --- > --- > ---------------------------------------------------------------------- > ---------- > #!/bin/sh > # > # 'stop' - Shell script a la RedHat initialization routines # R. > Toth - > May/2003 # V1.00 - Initial attempt at creating a fully compatible and > compliant # shutdown script that's called out of '/etc/ > init.d' (linked > appropriately # to the rc-level you are running in. You can link > this as > 'K31assp', so that ASSP is # terminated just after 'sendmail', in > case you > are also # running sendmail locally for your Email needs. > # > > if [ "$1" = "" ] > then > BASE=/var/db/assp2; > else > BASE=$1; > fi > export BASE > echo Starting ASSP Anti-SPAM Proxy server in $BASE trap '' 1 LANG= > export > LANG exec $BASE/assp.pl $BASE > > --- > --- > ---------------------------------------------------------------------- > -------------------------------------------------------------- > > ---------------------------------------- Stop > --- > --- > ---------------------------------------------------------------------- > ---------- > #!/bin/sh > if [ "$1" = "" ] > then > BASE=/var/db/assp2; > else > BASE=$1; > fi > export BASE > echo Stopping ASSP Anti-SPAM Proxy server in $BASE pidfile=$BASE/pid > kill > `cat $pidfile` > > --- > --- > ---------------------------------------------------------------------- > -------------------------------------------------------------- > > Or is the Problem here (Exception.log) ? > > M??r-14-10 12:09:46 Error: Worker_5: error: got unexpected signal > TERM in > Worker_5: package - Thread::Queue, file - > /usr/local/lib/perl5/5.10.1/Thread/Queue.pm, line - 51! > > > Best Regargs > Ralf > >>>> Thomas Eckardt <thomas.ecka...@thockar.com> 16.03.10 8.15 Uhr >>> > check your setting of 'AutoUpdateASSP' , 'AutoRestartAfterCodeChange', > 'AutoRestartCmd' > > read the GUI ! > > Thomas > > > > > Von: "admin" <ad...@dc0dam.de> > An: <assp-test@lists.sourceforge.net> > Datum: 16.03.2010 08:10 > Betreff: [Assp-test] ASSP2 autoupdate > > > > Hello, > > For some time ago, I have problems with download the update. ( ASSP > runs > under Freebsd Version 8). > Now I have the following : ASSP download automatic the new Version and > extract the new Version in the right folder. > But assp didn?t start automatic. Can someone can explain me, what > assp need > to start automatic ? Restart from the GUI doesn?t go too. > > Best regards > > Ralf > > --- > --- > ---------------------------------------------------------------------- > -- > Download Intel? Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Assp-test mailing list > Assp-test@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/assp-test > > > > DISCLAIMER: > ******************************************************* > This email and any files transmitted with it may be confidential, > legally > privileged and protected in law and are intended solely for the use > of the > > > individual to whom it is addressed. > This email was multiple times scanned for viruses. There should be no > known virus in this email! > ******************************************************* > > > > --- > --- > ---------------------------------------------------------------------- > -- > Download Intel? Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Assp-test mailing list > Assp-test@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/assp-test > > > > > DISCLAIMER: > ******************************************************* > This email and any files transmitted with it may be confidential, > legally > privileged and protected in law and are intended solely for the use > of the > > individual to whom it is addressed. > This email was multiple times scanned for viruses. There should be no > known virus in this email! > ******************************************************* > > > > > > ------------------------------ > > Message: 2 > Date: Tue, 16 Mar 2010 13:24:24 +0100 > From: mxx <m...@mailspot.at> > Subject: Re: [Assp-test] Workers STILL stuck @LocalLdapDomain although > using"flatfile" > To: ASSP development mailing list <assp-test@lists.sourceforge.net> > Message-ID: > <sig.26919903ea.sig.1691c3ca0f.4b9f7878.9070...@mailspot.at> > Content-Type: text/plain; charset="US-ASCII"; > format="flowed" > > Hi, > > thanks LOTS for all your helpful information and assistance! So much > appreciated! > > I tried the vrfy approach and enabled vrfy on my MTA. A telnet from > localhost worked fine (of course enabled the block from outside option > in assp). > > However as soon as I set LocalAddresses_Flat to '' and LocalDomains to > file:files/domains.txt ( a file containing entries (one per line) as > suggested as @mydomain.com=>vrfyhost:port, which is in my case looks > like @example.com=>localhost:25000), it seems as if ANY recipient > mailaddress is considered "ok" by assp > > "to: dasdfas...@example.com message ok -> /usr/share/assp/notspam/ > xxx.eml" > > This is the same when I set both, LocalAddresses_Flat to a file which > contains @example.com=>localhost:25000 and set LocalDomains to the > file > that contains *example.com=>localhost:25000 > > When I only set LocalAddresses_Flat to the file which contains > @example.com=>localhost:25000 and set my local domains manually in the > textbox LocalDomains, ALL mail is rejected because of user unknown. > > > If anyone knows what could be wrong with my setup, please help me! > > Also the option "block vrfy from external clients" is really useful, > but > shouldn't there also be an option to block EXPN from external hosts? > > Thank you very much! > > Max > > > > ------------------------------ > > Message: 3 > Date: Tue, 16 Mar 2010 15:50:47 +0100 > From: mxx <m...@mailspot.at> > Subject: Re: [Assp-test] Workers STILL stuck @LocalLdapDomain although > using"flatfile" > To: assp-test@lists.sourceforge.net > Message-ID: > <sig.2691c69dce.sig.06916caa93.4b9f9ac7.7030...@mailspot.at> > Content-Type: text/plain; charset="US-ASCII"; > format="flowed" > > Sorry posted wrong info: > >> However as soon as I set LocalAddresses_Flat to '' and LocalDomains >> to >> file:files/domains.txt ( a file containing entries (one per line) as >> suggested as @mydomain.com=>vrfyhost:port, which is in my case looks >> like @example.com=>localhost:25000), it seems as if ANY recipient >> mailaddress is considered "ok" by assp >> > > @example.com=>localhost:25000 and @mydomain.com=>vrfyhost:port is > set to > *example.com=> in the case of the localdomains file for > LocalDomains of > course.. > > > > > ------------------------------ > > Message: 4 > Date: Tue, 16 Mar 2010 16:26:01 +0100 > From: "GrayHat" <gray...@gmx.net> > Subject: Re: [Assp-test] Workers STILL stuck @LocalLdapDomain > althoughusing"flatfile" > To: "ASSP development mailing list" <assp-test@lists.sourceforge.net> > Message-ID: <011601cac51c$fcc956d0$1400a...@apra.it> > Content-Type: text/plain; charset="iso-8859-1" > > >> However as soon as I set LocalAddresses_Flat to '' and LocalDomains >> to file:files/domains.txt ( a file containing entries (one per line) >> as suggested as @mydomain.com=>vrfyhost:port, which is in >> my case looks like @example.com=>localhost:25000), it seems as >> if ANY recipient mailaddress is considered "ok" by assp > > thou shalt not add "@" to the domain names > > Seriously, the list should be > > example.com=>vrfyhost:port > example1.com=>vrfyhost:port > > and so on, no "@" at all inside that file > > > > > > > ------------------------------ > > Message: 5 > Date: Tue, 16 Mar 2010 17:33:11 +0100 > From: mxx <m...@mailspot.at> > Subject: Re: [Assp-test] Workers STILL stuck @LocalLdapDomain > althoughusing"flatfile" > To: assp-test@lists.sourceforge.net > Message-ID: > <sig.16918de3a3.sig.2691a6cd26.4b9fb2c7.3040...@mailspot.at> > Content-Type: text/plain; charset="US-ASCII"; > format="flowed" > > Hi GrayHat > > On 03/16/2010 04:26 PM, GrayHat wrote: >> >> thou shalt not add "@" to the domain names >> >> > :D > >> Seriously, the list should be >> >> example.com=>vrfyhost:port >> example1.com=>vrfyhost:port >> >> and so on, no "@" at all inside that file >> > > Replied to my own post shortly before stating that this was a typo, I > only added '@' before the domain names inside the LocalAddresses_Flat > file. Is it ok there? > The LocalDomains file is "*example.com...." . > So the asterisk is wrong there too?It's like that in the description > in > the web interface.. > > Ok, I'll try without the asterisks.. > > Thank you!! > > > > ------------------------------ > > Message: 6 > Date: Tue, 16 Mar 2010 12:37:52 -0400 > From: Scott MacLean <a...@hollsco.com> > Subject: Re: [Assp-test] Assp dying > To: ASSP development mailing list <assp-test@lists.sourceforge.net> > Message-ID: <4ce12724-ddf6-4c7b-9dce-b6f3c9810...@mail.frogstar.com> > Content-Type: text/plain; charset="us-ascii"; format=flowed > > I'm also having problems with ASSP dying on me. It's not like I have > seen it happen before - typically, when ASSP dies for me (at least in > the past), it just slowly grinds to a halt, refusing to accept any > more connections, until my watchdog service goes in, kills it, and > restarts > it. > > Now, it's just terminating itself with no notice. The logs show it is > operating normally, accepting connections and processing mail, with > no indications of slowing or problems of any kind. In the most recent > instance, which is typical, I see: > > Mar-16-10 12:06:57 [Main_Thread] Info: Main_Thread got connection > request > Mar-16-10 12:07:58 [startup] Starting as a service > Mar-16-10 12:07:59 [startup] ASSP-professional version 2.0.2(0.0.03) > (Perl 5.010001) (on MSWin32) initializing > > Coincidentally, in the Windows event viewer, I see this: > > 3/16/2010 12:06:57 The Anti-Spam Smtp Proxy service terminated > unexpectedly. It has done this 1 time(s). The following corrective > action will be taken in 60000 milliseconds: Restart the service > > So basically, ASSP is running along just fine, suddenly terminates, > and Windows restarts the service 60 seconds later. I am seeing this > happen 15-20 times a day, during daytime hours, when the server is > processing mail. It happens less often during the night, when the > server is not under as much of a load. The last line in the log when > it dies is always "Main_Thread got connection request". > > > Also: the GUI reports that 2.0.2(1.0.02) is available. Unlike > previous versions, where the link pointed to a .pl file, it now > points to a .gz file. Fine, I downloaded the .gz file, unpacked it, > and ended up with a ~390K "assp.pl" file containing binary data only. > Guessing by the binary content that it was a GZipped file, I renamed > the assp.pl file to assp.gz, and sure enough, it contained a 1.8M > assp.pl file, which contained the correct file. > > Is this correct? This double GZipped, incorrectly named file seems > wrong to > me. > > > ------------------------------ > > Message: 7 > Date: Tue, 16 Mar 2010 18:14:55 +0100 > From: "GrayHat" <gray...@gmx.net> > Subject: Re: [Assp-test] Workers STILL stuck > @LocalLdapDomainalthoughusing"flatfile" > To: "ASSP development mailing list" <assp-test@lists.sourceforge.net> > Message-ID: <015701cac52c$376095b0$1400a...@apra.it> > Content-Type: text/plain; charset="iso-8859-1" > >>> example.com=>vrfyhost:port >>> example1.com=>vrfyhost:port > >> So the asterisk is wrong there too? > > the correct format for LocalDomains is the above one; > that is no "@" nor "*" as for the address_flat, I'd suggest > you to AVOID it and instead use VRFY to check for the > existence of addresses; in any case do NOT use "*" > in there or it will just validate ANY address so making > it totally useless; the "*" should ONLY be used in case > you REALLY want to wildcard a domain, but then you'll > also have to configure the mailserver accordingly > > > > > > ------------------------------ > > --- > --- > ---------------------------------------------------------------------- > -- > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > > ------------------------------ > > _______________________________________________ > Assp-test mailing list > Assp-test@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/assp-test > > > End of Assp-test Digest, Vol 32, Issue 26 > ***************************************** > > > --- > --- > --- > --------------------------------------------------------------------- > Download Intel® Parallel Studio Eval > Try the new software tools for yourself. Speed compiling, find bugs > proactively, and fine-tune applications for parallel performance. > See why Intel Parallel Studio got high marks during beta. > http://p.sf.net/sfu/intel-sw-dev > _______________________________________________ > Assp-test mailing list > Assp-test@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/assp-test ------------------------------------------------------------------------------ Download Intel® Parallel Studio Eval Try the new software tools for yourself. Speed compiling, find bugs proactively, and fine-tune applications for parallel performance. See why Intel Parallel Studio got high marks during beta. http://p.sf.net/sfu/intel-sw-dev _______________________________________________ Assp-test mailing list Assp-test@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-test
