#14 Major Mail Aliases ISSUE

closed-accepted
nobody
None
5
2010-06-22
2010-06-16
Matt Crook
No

When using Mdaemon, when adding Mail Aliases, they don't show up after in the list, I also noticed, that it does not set the ItemTypeID in the SQL database, it just leaves it "NULL" value when it should be set to 16. Now showing anything after setting that, I still don't get anything, however it does count it as an alias.

Is this because maybe the mdaemon part is incomplete? If so I will take a look at it later?

Discussion

  • Matt Crook

    Matt Crook - 2010-06-16

    I did an upgrade and checked a few things. It seems when upgrading from DNP to WSP, I noticed in the database table "ServiceItemTypes" under the "DisplayName" of "MailForwarding" it still read "DotNetPanel.Providers.Mail.MailForwarding, DNP.Providers.Base" instead of "WebSitePanel.Providers.Mail.MailAlias, WebSitePanel.Providers.Base"

    Whats up with the left overs??!?!?! I thought this process was invisible? lol I will start looking in the source of the upgrade package so an update can be made ASAP!!!!

     
  • Matt Crook

    Matt Crook - 2010-06-16

    Now, when I click on a users alias it gives me this error:

    System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Value cannot be null.
    Parameter name: type
    at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
    at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters)
    at WebsitePanel.EnterpriseServer.esMailServers.GetMailForwarding(Int32 itemId)
    at WebsitePanel.Portal.MailForwardingsEditForwarding.BindItem()

     
  • Matt Crook

    Matt Crook - 2010-06-22
    • status: open --> closed-accepted
     
  • Matt Crook

    Matt Crook - 2010-06-22

    It appears it was human error all along. When making the database changes that I showed above, make sure to watch out for CAPS!!!!!
    look at the rest of database entry's and make sure they look the same, if not, you will get an error like me. Of course, make sure its set for MailAlias

    again, THE DATABASE IS CASE SENSITIVE W A T C H O U T

    thank you

    PS: Looking at upgrade code to fix this issue.
    anyone? or is this a waste of time since this post will most likely help anyone not wanting to waste as many hours I did :(

    PSS Close this and label as fixed

     

Log in to post a comment.