From: Mike S. <msh...@nu...> - 2003-05-28 12:47:54
|
I've got a backup mail server also, so I'm not worried about losing messages, only about the delay you mentioned. I will probably have the need to update the whitelist once a day (overnight). It just seems more graceful to me to be able to manipulate the whitelist without taking down ASSP. ---------------------------------------------------- Mike Shambaugh Chief Technology Officer Nucleus Medical Art, Inc. http://www.nucleusmedicalart.com/ http://www.medicallegalart.com/ 1275 Shiloh Road Suite 3130 Kennesaw, GA 30144 Voice: (800) 333-0753 ---------------------------------------------------- > From: Steve B <st...@bo...> > Reply-To: ass...@li... > Date: Wed, 28 May 2003 13:35:21 +0100 > To: ass...@li... > Subject: Re: Re-2: [Assp-user] your comments please on web configuration p age > > Since adding assp to the chain, i have setup a backup mail server (i know > you should have one anyway) that collects mail when assp is down and passes > tham on to assp when its back up. This means no mail is lost or returned > only delayed. > > Its would be ideal of course if assp could have all settings/changes made > whilst it is up. > > Maybe John has much of this in mind with v2 > > At 08:19 28/05/2003 -0400, you wrote: > >> What does everyone think about the possibility of adding an ASSP-specific >> extension to the standard set of SMTP commands to handle whitelisting? I've >> had the same issue that Dave is alluding to here. It would be really great >> if I could update the whitelist explicitly without having to take down ASSP. >> >> How about if ASSP recognized the special SMTP command "WHITELIST" during the >> SMTP conversation (in addition to "RCPT TO", "MAIL FROM", etc.)? The one >> parameter after the command would be the address (or domain) to add to the >> whitelist. Like: "WHITELIST no...@ma...". The command could be >> ignored unless it comes from a local domain (or even only localhost if we >> want to be very careful). This command obviously would not be passed along >> to the MTA. >> >> My biggest problem is that I've got a rather large database of clients who I >> would like to add to my whitelist, but in order to do that, my email server >> has to be down to the outside world for quite a while. >> >> Something like this would allow not only for the whitelist to be updated >> without taking down ASSP, it would also allow the whitelist to be more >> easily updated by automatic mechanisms local to the server. >> >> Any opinions? >> >> >> ---------------------------------------------------- >> Mike Shambaugh >> Chief Technology Officer >> Nucleus Medical Art, Inc. >> http://www.nucleusmedicalart.com/ >> http://www.medicallegalart.com/ >> 1275 Shiloh Road >> Suite 3130 >> Kennesaw, GA 30144 >> Voice: (800) 333-0753 >> ---------------------------------------------------- >> >> >>> From: dk...@pw... >>> Reply-To: ass...@li... >>> Date: Tue, 27 May 2003 19:17:00 -0500 >>> To: ass...@li... >>> Subject: RE: Re-2: [Assp-user] your comments please on web >> configuration p age >>> >>> SIG-HUP would be perfect! (actually preferred) Thanks for considering it. >>> It doesn't have to be *too* readable -- Maybe just a bit better than a >>> sendmail.cf >>> Would it re-read the whitelist if I did manual additions via list.pl or >>> overwrite it with the one in mem? >>> >>> It could spit some stats on STDOUT too and do the laundry.. and.. and.. >>> and.. >>> Don't you just hate my requests? :) >>> >>> -- >>> Dave >>> >>>> -----Original Message----- >>>> From: John Hanna [mailto:jh...@cp...] >>>> Sent: Tuesday, May 27, 2003 5:04 PM >>>> To: ass...@li... >>>> Subject: Re: Re-2: [Assp-user] your comments please on web >>>> configuration >>>> page >>>> >>>> >>>> Ok... So I can take a hint... Human Readable it will be, and >>>> I'll have to >>>> autodetect changes as well I suppose... Though I bet you VI >>>> types wouldn't >>>> mind a SIG-HUP to force a re-read... >>>> >>>> j >>> >>> >>> ------------------------------------------------------- >>> This SF.net email is sponsored by: ObjectStore. >>> If flattening out C++ or Java code to make your application fit in a >>> relational database is painful, don't do it! Check out ObjectStore. >>> Now part of Progress Software. http://www.objectstore.net/sourceforge >>> _______________________________________________ >>> Assp-user mailing list >>> Ass...@li... >>> https://lists.sourceforge.net/lists/listinfo/assp-user >> >> >> >> ------------------------------------------------------- >> This SF.net email is sponsored by: ObjectStore. >> If flattening out C++ or Java code to make your application fit in a >> relational database is painful, don't do it! Check out ObjectStore. >> Now part of Progress Software. http://www.objectstore.net/sourceforge >> _______________________________________________ >> Assp-user mailing list >> Ass...@li... >> https://lists.sourceforge.net/lists/listinfo/assp-user >> >> >> >> --- >> Incoming mail is certified Virus Free. >> Checked by AVG anti-virus system (http://www.grisoft.com). >> Version: 6.0.481 / Virus Database: 277 - Release Date: 13/05/2003 > > Steve. > > http://www.bov.nu - Homepages. > http://www.prismnortheast.co.uk - Support site for children with severe > epilepsy. > > My email has spam filtering: Please report any problems to pos...@bo... > Spam collecting spiders may send spam to no...@bo... :-) > > > --- > Outgoing mail is certified Virus Free. > Checked by AVG anti-virus system (http://www.grisoft.com). > Version: 6.0.481 / Virus Database: 277 - Release Date: 13/05/2003 > |