G'day,
When setting up the Continua email notification I couldn't test the connection credentials, or used my ISP mail relay (no authentication).
I’ve removed the requirement for a username and password. I’ll get around to the validate button once I sort a few bugs out first. I’m hoping the validate makes the next build but the requirement for username/password definitely will.
Sweet and I have email notification routing working and there is a shiny “Validation” button!
Build 926, reverts some code, so that anonymous email relay is not possible.
A new event has been added to the event log:
Exception: FaultException`1
Message: User Name cannot be null or empty.
Stack Trace: at Continua.Services.NotificationService.Validate(PublisherDTO publisherDTO)
at SyncInvokeValidate(Object , Object[] , Object[] )
at System.ServiceModel.Dispatcher.SyncMethodInvoker.Invoke(Object instance, Object[] inputs, Object[]& outputs)
at System.ServiceModel.Dispatcher.DispatchOperationRuntime.InvokeBegin(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage5(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.ProcessMessage31(MessageRpc& rpc)
at System.ServiceModel.Dispatcher.MessageRpc.Process(Boolean isOperationContextSet)
You should be able to save it even if validate fails. I’ll change the validate code to ignore it anyway