> Since IMail is receiving ALL mail from just IMGate, if one msg from > IMGate triggers this auto-block, then IMail blocks all mail from > IMGate, ie, all mail from internet. ouch.
That is a bad design indeed, since there are no exceptions to the auto-blocking. > The limit is good (IMGate has similar and many more types of limits > but the reject is per-message) but the action is wrong. How do any of those messages ever pass IMGate in the first place? Can't IMGate be set to block per-message using the same criteria? Not that you'd need IMail's support at that point, but I'm unclear on why IMGate doesn't/can't short-circuit the feature anyway. > I recommend that nobody use this feature, until Ipswitch corrects it It's the default, so I'd bet just about everybody is using it. We usually deploy with it turned on and have never found support a burden. I think the payoff, as long as the IMail server as the MX, outweighs the risk. -Sandy To Unsubscribe: http://www.ipswitch.com/support/mailing-lists.html List Archive: http://www.mail-archive.com/imail_forum%40list.ipswitch.com/ Knowledge Base/FAQ: http://www.ipswitch.com/support/IMail/
