Vista - SMTP over SSL - Certificate issue

I use SMTP over SSL, port 465. The certificate name from the mail server
doesn't match the server name (shared email server). It is expected and is
OK. This conflict kicks up a warning / confirmation when I send email. I
usually select the "Continue to use this server" button on the warning /
confirmation. I accidentally hit the "Do not continue to use this server"
button, and now I cannot send email. MS Mail doesn't warn / confirm any more,
it just rejects the certificate. Reboot doesn't reset this setting - not
session based. I can't find any settings to reset this.

How can I remove this setting regarding not using the certificate with the
name conflict? I want to continue to use this certificate, despite the name
conflict. Any ideas?

Try removing the mail account, closing and reopening WinMail and then add it
back again. Maybe it will forget then.

steve

"DRM" <DRM@discussions.microsoft.com> wrote in message
news:4F79883A-511B-4986-B620-49EAC4F1C966@microsoft.com...
>I use SMTP over SSL, port 465. The certificate name from the mail server
> doesn't match the server name (shared email server). It is expected and is
> OK. This conflict kicks up a warning / confirmation when I send email. I
> usually select the "Continue to use this server" button on the warning /
> confirmation. I accidentally hit the "Do not continue to use this server"
> button, and now I cannot send email. MS Mail doesn't warn / confirm any
> more,
> it just rejects the certificate. Reboot doesn't reset this setting - not
> session based. I can't find any settings to reset this.
>
> How can I remove this setting regarding not using the certificate with the
> name conflict? I want to continue to use this certificate, despite the
> name
> conflict. Any ideas?

Have you tried removing the mail account under Tools/Accounts - Mail tab,
then close Windows Mail and reboot? On startup, reopen Windows Mail and
create the account again. Then test it.
--
Jim Pickering
MVP-Windows Mail applications
Please reply only to the newsgroup.


"DRM" <DRM@discussions.microsoft.com> wrote in message
news:4F79883A-511B-4986-B620-49EAC4F1C966@microsoft.com...
>I use SMTP over SSL, port 465. The certificate name from the mail server
> doesn't match the server name (shared email server). It is expected and is
> OK. This conflict kicks up a warning / confirmation when I send email. I
> usually select the "Continue to use this server" button on the warning /
> confirmation. I accidentally hit the "Do not continue to use this server"
> button, and now I cannot send email. MS Mail doesn't warn / confirm any
> more,
> it just rejects the certificate. Reboot doesn't reset this setting - not
> session based. I can't find any settings to reset this.
>
> How can I remove this setting regarding not using the certificate with the
> name conflict? I want to continue to use this certificate, despite the
> name
> conflict. Any ideas?

It seems the certificate reject gets tied to the email message, not the Mail
app configuration, not the computer. I deleted the one email in the outbox,
recreated the email, and sent. It sent just fine and I started receiving the
prompt again when I send messages.

Thanks for your suggestions. MS Mail is sending email OK again.

"Jim Pickering" wrote:

> Have you tried removing the mail account under Tools/Accounts - Mail tab,
> then close Windows Mail and reboot? On startup, reopen Windows Mail and
> create the account again. Then test it.
> --
> Jim Pickering
> MVP-Windows Mail applications
> Please reply only to the newsgroup.
>
>
> "DRM" <DRM@discussions.microsoft.com> wrote in message
> news:4F79883A-511B-4986-B620-49EAC4F1C966@microsoft.com...
> >I use SMTP over SSL, port 465. The certificate name from the mail server
> > doesn't match the server name (shared email server). It is expected and is
> > OK. This conflict kicks up a warning / confirmation when I send email. I
> > usually select the "Continue to use this server" button on the warning /
> > confirmation. I accidentally hit the "Do not continue to use this server"
> > button, and now I cannot send email. MS Mail doesn't warn / confirm any
> > more,
> > it just rejects the certificate. Reboot doesn't reset this setting - not
> > session based. I can't find any settings to reset this.
> >
> > How can I remove this setting regarding not using the certificate with the
> > name conflict? I want to continue to use this certificate, despite the
> > name
> > conflict. Any ideas?
>

How can you disable this certificate warning?

"DRM" wrote:

> It seems the certificate reject gets tied to the email message, not the Mail
> app configuration, not the computer. I deleted the one email in the outbox,
> recreated the email, and sent. It sent just fine and I started receiving the
> prompt again when I send messages.
>
> Thanks for your suggestions. MS Mail is sending email OK again.
>
> "Jim Pickering" wrote:
>
> > Have you tried removing the mail account under Tools/Accounts - Mail tab,
> > then close Windows Mail and reboot? On startup, reopen Windows Mail and
> > create the account again. Then test it.
> > --
> > Jim Pickering
> > MVP-Windows Mail applications
> > Please reply only to the newsgroup.
> >
> >
> > "DRM" <DRM@discussions.microsoft.com> wrote in message
> > news:4F79883A-511B-4986-B620-49EAC4F1C966@microsoft.com...
> > >I use SMTP over SSL, port 465. The certificate name from the mail server
> > > doesn't match the server name (shared email server). It is expected and is
> > > OK. This conflict kicks up a warning / confirmation when I send email. I
> > > usually select the "Continue to use this server" button on the warning /
> > > confirmation. I accidentally hit the "Do not continue to use this server"
> > > button, and now I cannot send email. MS Mail doesn't warn / confirm any
> > > more,
> > > it just rejects the certificate. Reboot doesn't reset this setting - not
> > > session based. I can't find any settings to reset this.
> > >
> > > How can I remove this setting regarding not using the certificate with the
> > > name conflict? I want to continue to use this certificate, despite the
> > > name
> > > conflict. Any ideas?
> >