I’ve been working on a case with Microsoft’s Office365 support for several weeks trying to find out why email sent *to* a particular user was not being journalled. All the other mail seemed to be journalled to the external recipient, email from the user was working, just not email to that user.
The experience was quite frustrating as Microsoft’s support were terrible at calling back and could not grasp the concept of email tracking. Their solution after making a change was to wait a day to see if it was fixed although it was quite apparent that the Microsoft servers were not even trying to send the email (by looking at the Trace Logs you can see what email was being sent and received).
After checking the connectors were setup, mail properly scoped, the user had no rules on their mailbox, Microsoft’s solution was to delete the mailbox and reset it up again. Not so easy when the mailbox/user is federated with Active Directory and the user happens to be the owner of the company. That was not a conversation I was going to have with them!
The only thing that was different with this user was that in troubleshooting this issue we had set the user up to receive the journalling non delivery reports. I figured that if the emails were not being delivered, maybe sending him the errors would help. However no reports were being received either. However, according to KB 2829319 this behaviour can be seen. Although I had removed the journal receipient in the web gui, the emails were still not being journalled until I added another external email address to the configuration using the powershell command set-transportconfig -JournalingReportNdrTo [email protected]
At this point, all the email started to be journalled.
Note that we only added the recipient into the mix when I was trying to work on the initial problem so it looks like this wasn’t the only fix.
The other thing we did was change the outboundconnector to be onpremises. Changing the setting in the GUI we then ran Set-OutboundConnector archivemymailconnector -routeAllmessagesviaonpremises $true.
These two combinations seemed to fix the issue.
One thing I also learnt was that it is really useful to send multiple emails between changes and keep the subject line starting the same. Use the date/time at the end of the email. That way you can sort the email logs by Subject and just pick out the ones you were working on. By having the subject start with zzz followed by Round X (ie zzz Round 1 – change connector – 1345pm and zzz Round 1 – change connector 1346pm ) then the results are likely to appear at the end of your mail logs if you sort by subject. Sorting by Date was not always a good idea as mail flow could occur between mail coming into the server and mail leaving the server.
After about 3 weeks and many calls with Verizon technical support we finally got to the bottom of being unable to connect via a VPN on USB Verizon wireless cards (an older PCMCIA card was still working fine).
It turns out that the IP Code was set to general – which is normally placed on residential air cards to restrict ip traffic. The tech removed this “feature” and we confirmed vpn worked again.
So, if you are having this problem, contact Verizon Technical support and ask them to remove General IP code from the phone. If the Tier1 support person doesn’t know what you are talking about, request they instant message level 3 support who will know what you are talking about.
Good luck and I hope this prevents 3 weeks of VPN failure for other people.
Thanks to Eric for persevering and finally getting an answer
I checked on Dell’s website yesterday for the latest wifi drivers for the Inspiron 600m to fix the widely reported vulnerabilitys. Dell has a driver available but when you download the file, you can extract the files from it. However double clicking on the setup program causes the dellinfo.exe program to crash followed by a message stating “Error – This installer does not support installation on this computer.”
So far I’ve chatted with about 3 people on the dell chat program. The scary thing was when a tech asked me “Why is it your downloading the driver if the wireless card is ok?” – I had to (patiently) explain that I’m trying to download a driver to patch the critical vulnerability that is (from the readme) “Urgent = Dell highly recommends applying this update as soon as possible. The update contains changes to improve the reliability and availability of your Dell system.”
His solution was to send me the driver cd but we got cut off before we managed to exchange shipping address’s.
I checked the driver on another inspiron 600m this morning and the dellinfo.exe crashed on this machine but it tried to install the drivers but failed to do so with 2 more crashes that were reported to microsoft.
I tried chat this morning and the tech stated that the driver may be corrupt and I would need to contact customer care to report this. I called the customer care line 1 800 456 3355×7241969 who then after not understanding a word I was talking about put me through to support who then told me that they had put me through to the wrong department and I’m now on hold again – awaiting to put me through to the wireless support card. They can’t support me as apparently someone else installed the driver “2 hours ago” and therefore the download must be ok. A conference call to hardware support was the next step. Unfortunately hardware support were too busy to answer the phone so the tech guided me to the intel website and I downloaded the driver from the driver page on intel.com. Whilst I was downloading this driver my boss tripped over the phone cable, pulled the phone off the desk and hung up – I let out an involuntary wail as it was the end of 90 minutes with “technical hold support”. However the wireless drivers from Intel loaded ok but interestingly the windows driver version is the same as the version that I was currently running (220.127.116.11), but the Intel Wireless software (an alternative to Windows Wireless configuration utility) was upgraded a couple of versions to 10.5.0.3.
Note that if you scroll down on the driver page you can actually just download the windows driver by itself (something I should have done as I don’t use the IBM configuration software as the Windows Management software is easier to use as it is standard across all the laptops.