We've been using outlook to send and receive emails for years.. since yesterday, when we try to send an email, a dialog pops up asking for userid / password. Receiving emails works perfectly fine and given it's the same password for pop3 and SMTP, something has to have gone wrong at virgin's end.
Opsys : win7 & win10 mail client : outlook 2007 SMTP Server : smtp.virginmedia.com Port : 465 Encryption : SSL user : @blueyonder.co.uk / @virginmedia.com for different mailboxes.
These details haven't changed for a long time.
This happens on 3 different PCs
Can log into virginmedia.com email and can send from there.
Phoned support, no help, kept saying I should be using imap and that smtp should be working because my wifi was fine and then tried to get me to go to a different service that I'd have to pay for.
The password servers sometimes get out of sync. This can usually be fixed by resetting the password via the My Virgin media page for the account concerned. By entering the existing password as the new password should force the resync.
_________________________________________________________ Graham I am a VM customer. There are no guarantees that my advice will work.
As a Very Insightful Person, I'm here to share my knowledge. I don't work for Virgin Media.
Happened to me too, and the Wife. Both (on different PCs) on Outlook.
Found the answer. In "advanced" settings in the Internet email settings, (the area where you can "test" account settings, "more settings" button) "Outgoing server" tab, there is a radio button marked "log onto incoming mail server before sending mail". Check this, and all will be well.
Been using Outlook on PCs with Blueyonder/Virgin media for 20 years, and two days ago, it changed. Two days without managing to reply resulted...
My guess is that there used to be individual user authentication for the incoming mail server, and also for the outgoing SMTP server, but it is now all handled by the incoming server, so if you don't log onto that first, you are going no-where. Wish they would not fiddle, and if they have to, how about working out the ramifications first, and making first line support be party to it?