Production code adds a BCC to email account of developer
-
No idea why he was "spying" on a client. We only found this out after he left and we took over the account.
private MailMessage BuildMailMessage(...)
{
...mailMessage.BCC.Add("guys@address.com");
..
}:confused:
.
-
No idea why he was "spying" on a client. We only found this out after he left and we took over the account.
private MailMessage BuildMailMessage(...)
{
...mailMessage.BCC.Add("guys@address.com");
..
}:confused:
.
Some of us have done that at my job to temporarily monitor production emails to be sure everything is working as expected.
-
No idea why he was "spying" on a client. We only found this out after he left and we took over the account.
private MailMessage BuildMailMessage(...)
{
...mailMessage.BCC.Add("guys@address.com");
..
}:confused:
.
Somewhere (the daily WTF?) I saw <a href="mailto:....bcc=guys@address.com.."> link. Seems to be not so uncommon.
-
Some of us have done that at my job to temporarily monitor production emails to be sure everything is working as expected.
-
I can understand why a dev would want to monitor things to ensure that everything is working properly. I also understand why a customer would not like the idea of being spied upon. :)
Just because the code works, it doesn't mean that it is good code.
Potayto, potawto. Another thing we do is retain any emails sent from our servers. I suppose that could be considered spying too.
-
Some of us have done that at my job to temporarily monitor production emails to be sure everything is working as expected.
AspDotNetDev wrote:
Some of us have done that at my job to temporarily monitor production emails to be sure everything is working as expected.
Yeah, that would be my initial reaction too. Just making sure the body/to/ccs/etc are working right. Of course, I'm coming from my world, where we have several automatically-generated emails. Although I would typically write this info to a log instead of copying myself/someone else. A little disappointing that dev didn't configure the 'emailChecker' address so it could be easily de-configured.
-
No idea why he was "spying" on a client. We only found this out after he left and we took over the account.
private MailMessage BuildMailMessage(...)
{
...mailMessage.BCC.Add("guys@address.com");
..
}:confused:
.
Thinking the best, he wanted to be sure that the system was running perfectly, thinking the worst, he may be working for someone else... However, if the account was a corporate account (and not his personal email account), most likely he was monitoring the system.
CEO at: - Rafaga Systems - Para Facturas - Modern Components for the moment...