When I originally set up IMGate, I had to switch from RAV to reject-unlisted-recipient for this very reason. Imail couldn't handle the dictionary attacks, and it couldn't handle the RAV from the dictionary attacks. The whole point of IMGate for us was to take the load and processing power for the dictionary attacks off of Imail. The RAV still connected to Imail to verify the address, rendering IMGate useless as far as Imail was concerned. The only way it would seem to have any effect on the dictionary attacks is with reject-unlisted-recipient.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Len Conrad Sent: Wednesday, January 26, 2005 10:45 AM To: [email protected] Subject: [IMGate] Re: Imail bogus connects in high volume >To look at where the connections are coming from? the connections are from Imail to postfix. I'll report whether upgrading from RAV to reject_unliseted_recipient fixes the pb, or not. Judging from the number of IMail users that have Imail screwing up from large volumes of unknown users, I have to say Imail is becoming less acceptable as an MX machine as the volumes go up. Imail is vulnerable as MX. Len
