Re: [Assp-user] SMTP delaying issue with upgraded ASSP installations
Questions and Answers for users of ASSP Anti-Spam SMTP Proxy assp-user@lists.sourceforge.net schreibt: p.s. Any suggestions for making this a little less error prone, especially for new users. A FAQ or wiki entry detailing this particular scenario, or perhaps coding enhancements to detect/correct this issue automatically? I am willing to do, make a proposal, what to do when. fritz - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
Re: [Assp-user] SMTP delaying issue with upgraded ASSP installations
Please tell me, what was in the field smtpdestination in your installation? fritz - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
Re: [Assp-user] SMTP delaying issue with upgraded ASSP installations
Questions and Answers for users of ASSP Anti-Spam SMTP Proxy assp-user@lists.sourceforge.net schreibt: delayok() I do not get it, what _INBOUND_ has to do with it. The call to the subroutine just makes sure that there is a smtpdestination. Did you have a empty smtpdestination field or what was really in that field? The only situation, which makes sense to me, would be, that from the beginning, you put some wrong content into the field including the port: eg not.avalid.entry:125, because the other routines regarding smtpdestination are forgiving and would catch the port out of the wrong entry. So to makes things short; the problem has nothing to do with the possibilities of _INBOUND_ but erose from a incorrect entry in smtpdestination. If you would have put there 125 or 2525 it would have been also solved. fritz - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
Re: [Assp-user] SMTP delaying issue with upgraded ASSP installations
I was using a hostname.domain:port combo (e.g. hostname.sub.domain.tld:1234). This has been working well for several years with only delaying appearing to have a problem. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Fritz Borgstedt Sent: Sunday, January 21, 2007 5:34 PM To: Questions and Answers for users of ASSP Anti-Spam SMTP Proxy Subject: Re: [Assp-user] SMTP delaying issue with upgraded ASSP installations Please tell me, what was in the field smtpdestination in your installation? fritz - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
Re: [Assp-user] SMTP delaying issue with upgraded ASSP installations
Not limiting smtpDestination to just ip addresses opens up all sorts of possible benefits (e.g. DNS based round-robin server load-balancing). Besides, DNS is a much nicer way to deal with ip address changes than going to each ASSP installation and manually changing the smtpDestination (imho). -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Fritz Borgstedt Sent: Sunday, January 21, 2007 6:57 PM To: Questions and Answers for users of ASSP Anti-Spam SMTP Proxy Subject: Re: [Assp-user] SMTP delaying issue with upgraded ASSP installations Questions and Answers for users of ASSP Anti-Spam SMTP Proxy assp-user@lists.sourceforge.net schreibt: I was using a hostname.domain:port I do not know about several years, only about 3 years and since then it was always address:port as everywhere in ASSP and as all examples in the documentation show. fritz - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
Re: [Assp-user] SMTP delaying issue with upgraded ASSP installations
Not limiting smtpDestination to just ip addresses opens up all sorts of possible benefits (e.g. DNS based round-robin server load-balancing). Besides, DNS is a much nicer way to deal with ip address changes than going to each ASSP installation and manually changing the smtpDestination (imho). May be, but we are discussing here the is situation. - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
Re: [Assp-user] SMTP delaying issue with upgraded ASSP installations
Ok, finally had a chance to look at this issue outside of the it's broken user construct - and there appears to be a simple fix. I have seen postings in the ASSP Help forum related to the same delaying not working issue, and at this point I can only make the assumption that those users are doing something similar to me... running ASSP on the same box as the receiving MTA _AND_ using the local interface IP/hostname of the MTA in the 'smtpDestination' field (as a side note we are actually running multiple MTAs on this host). In poking around in the perl code I noticed a particular condition for handling delaying when using the __INBOUND__ keyword. Hmmm... ok, so it looks like delaying needs a little help when dealing with local-local socket connections. I replaced the hostname:port combo in the 'smtpDestination' field with __INBOUND__:port and voila... she works. The web interface help text for 'smtpDestination' is as follows... quote The address:port of your message handling system's SMTP server. If only the port is entered, or the keyword __INBOUND__:port is used, then the connection will be established to the same IP where the connection was received. This is useful when you have several IPs with different domains/profiles in your MTA. Examples: 127.0.0.1:125,127.0.0.1:125|127.0.0.5:125, 10.0.1.3, 10.0.1.3:1025, __INBOUND__:125, 125, etc. /quote Looking back on the problem I'm smacking myself on the head for not narrowing the issue down earlier, but I just did not make the initial connection in my head that delaying and smtpDestination might be conjoined at the hip. In any event a particular problem that has been bugging me for over a year now seems resolved. As always - humble thanks to the ASSP team for the best anti-spam product on this (or any other) planet. p.s. Any suggestions for making this a little less error prone, especially for new users. A FAQ or wiki entry detailing this particular scenario, or perhaps coding enhancements to detect/correct this issue automatically? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Charles Marcus Sent: Monday, January 08, 2007 11:23 AM To: Questions and Answers for users of ASSP Anti-Spam SMTP Proxy Subject: Re: [Assp-user] SMTP delaying issue with upgraded ASSP installations Melbourne E. Wells wrote: filepaths all check out. I'm going to re-make a config from scratch and see what happens - in the meantime if anyone has additional suggestions I'm all ears. Run a diff against the two files to see where they differ? I'm curious myself... -- Best regards, Charles - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
Re: [Assp-user] SMTP delaying issue with upgraded ASSP installations
filepaths all check out. I'm going to re-make a config from scratch and see what happens - in the meantime if anyone has additional suggestions I'm all ears. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of [EMAIL PROTECTED] Sent: Thursday, January 04, 2007 4:44 AM To: Questions and Answers for users of ASSP Anti-Spam SMTP Proxy Subject: Re: [Assp-user] SMTP delaying issue with upgraded ASSP installations On 3 Jan 2007 at 22:51, Melbourne Wells wrote: Have you got all the necessary subdirectories for your filepaths? paul - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
Re: [Assp-user] SMTP delaying issue with upgraded ASSP installations
Melbourne E. Wells wrote: filepaths all check out. I'm going to re-make a config from scratch and see what happens - in the meantime if anyone has additional suggestions I'm all ears. Run a diff against the two files to see where they differ? I'm curious myself... -- Best regards, Charles - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
Re: [Assp-user] SMTP delaying issue with upgraded ASSP installations
Melbourne Wells [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hello all, I have several ASSP installations of varying age (most are currently 1.2.6 - incrementally upgraded from 1.1.0 etc...) I have noticed that on most (perhaps all) of my older ASSP installations that are now running 1.2.6, delaying will not work (no delay related log activity, no delay related debug output, etc). All of the installations that I'm looking at right now are using current ActivePerl on Win2K boxes. The interesting thing is that a recent clean install of ASSP and ActivePerl on a fresh OS installation resulted in a working delaying function on that particular server. I have started to compare the assp.cfg on the working box with the assp.cfg on the non-working boxes by hand to see if it might be a config oddity, but as of yet I have not found anything that looks out of place. If anyone has had similar problems or can point me to the right place to take a hammer to, I'd be most appreciative to hear from you. Thanks. Is it possible that the emails coming through have already been white-tupled? ie: already delayed in the past, so no more reason to delay them anymore? Eric - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
Re: [Assp-user] SMTP delaying issue with upgraded ASSP installations
Hi Eric, thanks for the response. Currently inbound SMTP is not even being processed by delaying despite the fact that delaying is turned on in the config. The only thing I have not tried yet is to have ASSP re-create a default config and merge in the important settings from my existing config. Before I do that I was hoping that someone might have come across this issue before and found a specific solution. I'm not even sure that ASSP is at fault (it might be an odd issue with my perl installation) but I'm focusing on ASSP right now because it's the easiest thing to poke at. For your viewing pleasure, my database cleanup output follows... Jan-3-07 22:09:12 Saving whitelist Jan-3-07 22:09:12 Saving redlist Jan-3-07 22:09:12 Saving delaying records Jan-3-07 22:09:12 Saving penalty records Jan-3-07 22:09:12 Saving cache records Jan-3-07 22:09:12 Cleaning up delaying databases ... Jan-3-07 22:09:12 Cleaning delaying database (triplets) finished; keys before=0, deleted=0 Jan-3-07 22:09:12 Cleaning delaying database (whitelisted tuplets) finished; keys before=0, deleted=0 Jan-3-07 22:09:12 Saving penalty records Jan-3-07 22:09:12 Saving cache records Jan-3-07 22:09:12 Cleaning penalty records... Jan-3-07 22:09:21 PB: cleaning black finished; IPs before=13209, deleted=209 Jan-3-07 22:09:21 PB: cleaning white finished; IPs before=142, deleted=0 Jan-3-07 22:09:21 Cleaning cache records... Jan-3-07 22:09:21 RBLCache: cleaning cache finished; IPs before=56, deleted=0 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Eric B. Sent: Wednesday, January 03, 2007 9:43 AM To: assp-user@lists.sourceforge.net Subject: Re: [Assp-user] SMTP delaying issue with upgraded ASSP installations Melbourne Wells [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Hello all, I have several ASSP installations of varying age (most are currently 1.2.6 - incrementally upgraded from 1.1.0 etc...) I have noticed that on most (perhaps all) of my older ASSP installations that are now running 1.2.6, delaying will not work (no delay related log activity, no delay related debug output, etc). All of the installations that I'm looking at right now are using current ActivePerl on Win2K boxes. The interesting thing is that a recent clean install of ASSP and ActivePerl on a fresh OS installation resulted in a working delaying function on that particular server. I have started to compare the assp.cfg on the working box with the assp.cfg on the non-working boxes by hand to see if it might be a config oddity, but as of yet I have not found anything that looks out of place. If anyone has had similar problems or can point me to the right place to take a hammer to, I'd be most appreciative to hear from you. Thanks. Is it possible that the emails coming through have already been white-tupled? ie: already delayed in the past, so no more reason to delay them anymore? Eric - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user - Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT business topics through brief surveys - and earn cash http://www.techsay.com/default.php?page=join.phpp=sourceforgeCID=DEVDEV ___ Assp-user mailing list Assp-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/assp-user
