Select the search type
  • Site
  • Web
Search
You are here:  Support/Forums
Support

Bring2mind Forums

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 05/28/2007 11:24 PM by  Peter Donker
e-mail notification on subscription - failing
 2 Replies
Sort:
You are not authorized to post a reply.
Author Messages
SwanB
New Member
New Member
Posts:3


--
05/26/2007 2:14 PM

    When activaiting subscription on folders and documents in the DMX-module, we assume the DMX is supposed to send an e-mail to subscribers when changes and updates occur ?

    Our DMX is unfortunately failing in this respect.

    We are running DMX v. 03.04.07, on a DNN 3.2.2 installation. I have tested two different SMTP servers, and while the regular DNN e-mail notification is working flawless, the DMX is "gracefully" failing.

    The Edit.Notification with default value (EMAIL_DMX_NOTIFICATION) is present in the Logging.acsx.en-US.resx as well in the Logging.acsx.resx file. 

    I would be most grateful for any suggestion why this behaviour.

    Thank you for an otherwise great product.

    Best regards,

    Swan B.

    SwanB
    New Member
    New Member
    Posts:3


    --
    05/28/2007 3:02 PM

    To further elaborate on the issue. 

    On the same server, (different web site, and sql database) we are running another licence of DMX(v. 03.04.07), on a DNN 4.3.7. On this installation the subscription e-mail feature is e-mailing notifications fine.

    One difference is that the none working site , do have in Site Settings a Home Directory: Portals/1, while the non working do have in Site Settings a Home Directory: Portals/0

    I do not know if this info help on the issue ?

    Best regards

    SwanB

    Peter Donker
    Veteran Member
    Veteran Member
    Posts:4536


    --
    05/28/2007 11:24 PM
    I don't think the Home Dir is the issue. My guess is that there's something up with DNN 3.2.2. The email core DNN email function has unfortunantely changed 'signature' regularly over the past 2 years. This has meant that 've had to chase email issues continuously with each release as it could fail in any of the past platforms. I'll see if I can track this one down, but it's going to take a while to do as I need to find the time to set up a DNN 3.2.2/NET 1.1 environment where I can test this.
    Peter
    You are not authorized to post a reply.