This is a very strange change in behavior, and I think this would cause many people problems. If the the SMTP MTA that ASSP is talking to is unavailable, ASSP essentially should act as a secondary MX (sort of). ASSP should simply queue messages. It can continue to block and work on messages, but those that pass all tests, should sit and wait for the destination MTA to come back online.
Unless I am reading this wrong, which I really hope I am, this means, if your ASSP and remote MTA are on different machines, then even a server reboot will cause messages during the time it takes the machines to reboot to be allowed. There is no guarantee ASSP is on the same machine, let alone the same subnet. Any small glitches is a window in which VRFY or RCPT is now unavailable. Those messages all pass, most of which will be user not known, thereby generating a bounce. Do I understand this correctly? -- Scott * If you contact me off list replace talklists@ with scott@ * > - if VRFY or RCPT TO is used to verify the recipient address > and the MTA is not available the address was rejected - it is > now accepted in this case ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/assp-test
