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.php&p=sourceforge&CID=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.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Assp-user mailing list
Assp-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/assp-user

Reply via email to