Thanks.
Thanks.
Just want to inform the community that we are facing an IMail bug since we are on version 12.2.
If we go to User Administration in a large domain, which contains more than about 40'000 to 50'000 user accounts, the WAdmin.exe Utility hangs and will not response anymore.
In the event log we can see a .NET Runtime 'System.OutOfMemoryException'.
The issue is committed by the IMail Support Team as a official IMail bug, but no workaround is available until today. (Issue exists only in version 12.2)
I'm using the server as a secondary MX for a specific domain. I have set up "store and forward and etrn" as it is told in the user's guide. Everything works just fine but the problem is that:
SPAM mailers query the secondary MX record for the domain and make a dictionary attck although the primary server is online. Imail stores all the mail without being able to check if the mail address exists or not. And this causes a huge number of SPAM mails coming to the secondary mail server...
Is there another way doing it or am I doing something wrong?
Thanks
I have heard from a users about the poor performance of the web mail for some time. After upgrading to 12.2 SP1 to be "current" and after uninstalling Collaboration and CommTouch to prevent any unused components from getting in the way, I'll report various error conditions I have encountered today in case they are related.
Failed to Load Provider Source (seems to happen very frequently)
[code]12/28/2012 - 12:50 PM : info@(removed).com:ERROR: GetUserProfile(info@(removed).com) - Failed to load the provider source
12/28/2012 - 12:50 PM : info@(removed).com:GetReminders - Failed to load the provider source
at Ipswitch.Messaging.Framework.Providers.Legacy.IMailSecUserProvider.LoadProviderSource()
at Ipswitch.Messaging.Framework.Providers.Legacy.IMailSecUserProvider..ctor(Host host)
at Ipswitch.Messaging.Framework.Providers.Legacy.LegacyProviderFactory.GetUserProvider(Host host)
at Ipswitch.Messaging.Framework.Host..ctor(MessagingSystem system)
at Ipswitch.Messaging.Framework.Providers.Legacy.IMailSecHostProvider.Get(IMailHost imailSecHost, MessagingSystem system)
at Ipswitch.Messaging.Framework.Providers.Legacy.IMailSecHostProvider.Get(String hostName)
at Ipswitch.Messaging.Framework.HostContainer.Get(String host)
at Ipswitch.Messaging.iClient.Utility.GetImailUser(String username)
at Ipswitch.Messaging.iClient.ImailProfileProvider.GetUserProfile(String username)
at Ipswitch.Messaging.iClient.ImailProfileProvider.GetPropertyValues(SettingsContext context, SettingsPropertyCollection collection)
at System.Configuration.SettingsBase.GetPropertiesFromProvider(SettingsProvider provider)
at System.Configuration.SettingsBase.GetPropertyValueByName(String propertyName)
at System.Configuration.SettingsBase.get_Item(String propertyName)
at System.Web.Profile.ProfileBase.GetInternal(String propertyName)
at System.Web.Profile.ProfileBase.get_Item(String propertyName)
at Ipswitch.Messaging.iClient.CalendarService.GetReminders(String userTZInfo)[/code]
This screen shot shows message(s) having been selected to be deleted (using the checkbox) - yet the bottom pane states "no message has been selected".
I recommend improving the text in the bottom pane to be more specific and clarify:
"No message has been selected for preview"
This will prevent the user from thinking that their checkbox selections are no being recognized and looking for "ways" to overcome this "error" message!
Not sure if it's a matter of z-Order or if it's a matter of it NOT really being "modal", causing a subsequent event to "supersede" the event that the message is waiting to confirm:
The message "hidden"/grayed in the screen shot above is the Delete "confirmation" message:
11:08 12:26 POP3D (007CE1B9) Purge error 26, check locks, multiple accesses for {user} {domain} from {userIP}
Any ideas?
Tech Support told me that it's from multiple devices attempting to retrieve emails at the same time; however this is happening to users who have just the 1 PC, no phones, no other devices attempting to retrieve emails.
Any insight would be most appreciated.