I wanted to switch to IMail from SmartMax (MailMax) because
1. MailMax inexplicably would hang and start bouncing mail. When I had one
processor on that machine it would run it up to 100% and hang (not the
server, just the mail delivery), not delivering msgs out of the queue. With
two processors, it would only go to 50%. Random occurences. POP login would
still work, the queue would just fill and also some incoming msgs bounced.
Very embarrassing.
2. If my settings were wrong, well, MM tech support was never able to help
me, even with full access to my server and now apparently some backdoor
that they don't even tell you about, they go in w/o warning.
3. No notification of patches/updates, no version history etc. Lots of
undocumented options, ie the only way you could find out about it was to
complain or ask, then magically it would be sent to you... why make me do
this.
4. Their xtra cost webmail product had a lot of problems initially and
altho it now works pretty reliably - just not as nice as Imail + the
fantastic HumanKind templates.
MailMax was much less expensive than IMail. Now I THOUGHT that by spending
$1,500 plus service contracts, Ipswitch would be a well paid enough company
to provide a product and service superior to MailMax. I used MailMax for
over a year and I really kept hoping it would start being reliable for me.
Another thing that would have improved MailMax would be a support list like
this one, to share tips. I hope IMail development/customer service is
listening, as this list is giving them important feedback.
My 2c.
- April
At 10:27 PM 05/15/2000 -0400, you wrote:
>I do agree with your statement that a mail server
>sold on the ISP market should not crash if the
>admin of one virtual domain creates a mail loop.
>As a general design rule, all software should protect
>itself against bad user input. Either ignore it or try
>to process data as gracefully as possible.
>
>The 50 user limit on aliases is another example. If
>Imail can not handle aliases with over 50 users,
>instead of going into long delivery delays it should
>either:
>
>1. Bounce any message to the suspect alias sending
>the moderator a message indicating "Too many
>addresses on alias".
>
>2. Forward the message and list to the list manager for
>processing.
>
>Having to tell domain admins to limit their list aliases
>to 50 and that if they go over 50 they must convert to
>a list sounds too manual for software used in the year
>2000. None of the screens tell you whether you reached
>the "magic" number so an admin must count each address
>to check whether they reached 50.
>
>----- Original Message -----
>From: "Mark McDonald" <[EMAIL PROTECTED]>
>To: <[EMAIL PROTECTED]>
>Sent: Monday, May 15, 2000 6:56 PM
>Subject: RE: [IMail Forum] setflags - Set Imail user flags from the command
>line - IpSwitch, what gives here?
>
>
>Yeeee Haw! It's amazing that IPSwitch can't produce these little utilities.
>I just got off the phone with IPSwitch tech support about a SMTP32.EXE Dr.
>Watson error we're having. They just told me, and I quote:
>
>"Go through every alias/list, and make sure you don't have any mail loops".
>
>
>I know it's not the support Reps fault, but come on. They don't admit this
>is a bug, rather an incorrectly configured mail system. No matter how ANY
>of our users configure their boxes/domains, it should NOT bring our entire
>mail system to a screeching halt. Back to the subject, Keep in mind, on
>this particular IMail installation, we have about 700 Domains, and thousands
>upon thousands of Lists/Aliases. They said it's not a Bug in IMail, and
>it's a user-end problem. How does that make all you Admins feel, that any
>of your Host Admins can create two aliases that point to each-other, and
>crash your entire Mail system. Yet, it's not a bug. Wonderful.
>
>Check out this quote on their site:
>
>"IMail delivers greater performance than proprietary mail systems, offering
>scalability to over 100,000 accounts on a single server"
>
>Yea right, then you have a problem and call Tech support and they tell you
>"Sir, you need to go through each account manually to detect which user
>created an alias loop. It's not our problem."
>
>It would be nice to hear IPSwitch say "Yes, we know about it. We have our
>developers looking into that problem, and we have it marked as an urgent
>bug. We should have it fixed shortly".
>
>Can anybody recommend a mail system that can take abuse from users and still
>run?
>
>
>-Mark McDonald
>[EMAIL PROTECTED]
>
>The Siteserver Network!
>Voice: 800.610.9856, Ext. 231 - Fax: 888.333.2710
>
>
>
>Please visit http://www.ipswitch.com/support/mailing-lists.html
>to be removed from this list.
>
>
Please visit http://www.ipswitch.com/support/mailing-lists.html
to be removed from this list.
