|
Tough. There can't be one obvious choice or the EU will try to screw billions of dollars out of it!
|
|
|
|
|
Short Flying soldier's ascension was important (9)
Easy as I am off on Friday
cheers,
Super
------------------------------------------
Too much of good is bad,mix some evil in it
|
|
|
|
|
Jump boy == PARA
Ascension == MOUNT
PARAMOUNT
Thank you.
veni bibi saltavi
|
|
|
|
|
Was easy right ? 
Your chance tommorow to give tougher one
cheers,
Super
------------------------------------------
Too much of good is bad,mix some evil in it
|
|
|
|
|
Para gave it away. Bloody kids jumping out of planes, then moaning when the Artillery don't provide a fire storm in exactly a different place from where the buggers said they would be.
veni bibi saltavi
|
|
|
|
|
I wanted to give the clue as
PAR + AMOUNT or PAR + AM +(C)OUNT but was not sure if it will get solved. So Had to dilute down a little.
Thursday is not a good time for me to post a CCC as I am off every Friday
cheers,
Super
------------------------------------------
Too much of good is bad,mix some evil in it
|
|
|
|
|
Today i found out that one of the employees here has left us for more than one month now.
He recieves a daylie mail of changes on inventory and stuff by one of my programms. Bad thing is, no one told me he left, so emails kept stacking on his account.
I personally think such mails are good if errors occur or you need a daylie feedback, but what happens if you forget to who you send emails?
How do you think about this?
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
I'm sure he didn't tell you because he wants to sell the business information to his new employer... 
Anything that is unrelated to elephants is irrelephant
Anonymous
-
The problem with quotes on the internet is that you can never tell if they're genuine
Winston Churchill, 1944
-
I'd just like a chance to prove that money can't make me happy.
Me, all the time
|
|
|
|
|
Don't you get error that such email address does not exist any more?
|
|
|
|
|
Uhm, programm is running on a task server that executes it once a day.
So, nope im not getting an error 
Instead... omg, i think something bad happend...
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
Shouldn't it work like this:
- Find the people from AD to which mail should be sent. People could be filtered out by using AD groups.
- Send emails to people located.
If the account still exists after a person had left the organization, it is big problem.
|
|
|
|
|
Yeah that would be a great idea 
I should change that, in fact it was just one person to recieve the email 
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
If it's just internal, perhaps you could send it to a single mailing list and make it the IT departments job to keep that updated..
Cup of tea time ![Java | [Coffee]](https://codeproject.freetls.fastly.net/script/Forums/Images/coffee.gif) 
How do you know so much about swallows? Well, you have to know these things when you're a king, you know.
modified 31-Aug-21 21:01pm.
|
|
|
|
|
1) Code checks with the corporate domain controller - if the account does not exist or the account is locked, no email gets sent.
2) Generally speaking dashboards are better than email notification. Most people have outlook rules et up that just ignore the emails anyway and email delivery is not guaranteed.
|
|
|
|
|
Duncan Edwards Jones wrote: 2) Generally speaking dashboards are better than email notification.
Disagree. Filing a bug on an application I'm nominally in charge of supporting but not actively working on, that I'll only find out about if I explicitly visit the AINICOSBNAWO project dashboard is a guarantee that I won't see it for months if ever.
Did you ever see history portrayed as an old man with a wise brow and pulseless heart, waging all things in the balance of reason?
Is not rather the genius of history like an eternal, imploring maiden, full of fire, with a burning heart and flaming soul, humanly warm and humanly beautiful?
--Zachris Topelius
Training a telescope on one’s own belly button will only reveal lint. You like that? You go right on staring at it. I prefer looking at galaxies.
-- Sarah Hoyt
|
|
|
|
|
Do you have recipients hard coded? If so, is it possible to re-write the software to pull from a table of recipients versus hard-coded?
|
|
|
|
|
1 recipient -> hard coded yeah 
if(this.signature != "")
{
MessageBox.Show("This is my signature: " + Environment.NewLine + signature);
}
else
{
MessageBox.Show("404-Signature not found");
}
|
|
|
|
|
I was looking after the local office of a small US company, including being the signatory for banking purposes. Five years after I left that company, I still get mobile messages at the beginning of every month about the amount credited to that banking account; deleting these fifteen odd messages is a monthly task.
|
|
|
|
|
Avijnata wrote: is a monthly task.
Bill them for it? 
|
|
|
|
|
|
Programs should really mail things to a group account if they have to do something like this. When someone leaves, they get removed from the group. It's as easy as that.
|
|
|
|
|
The trouble is that, most places I've worked, the groups themselves change every five minutes, so you end up either mailing to non-existent groups, or forever updating the mailing list (and e-mail templates! Soooo sick of having to change the "To" and "CC" lists in e-mail templates!)
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
We recommend using LDAP groups, so you'd add a person to that group and when you remove their account from the system, they're automatically removed from the group. It's a very simple system to maintain.
|
|
|
|
|
Er, yeah. I'm talking about the fact that one minute you can have groups "Dev-A", "Dev-B", and "QA", but the next minute, everyone's been reshuffled, and you've got "Implementation1", "back-end1", and "Testing1".
And the following week, "Testing1" is absorbed into "Implementation1", which is then split into...
... Etc. I'm sure you get the idea.
I wanna be a eunuchs developer! Pass me a bread knife!
|
|
|
|
|
After many years of this problem, we just decided to start using only groups. But I see about a hundred places changes need made. 
We send a lot of emails. Most get ignored.
We have a dashboard of sorts. Mostly ignored.
You can lead a horse to water, but you can't make it drink.
Mongo: Mongo only pawn... in game of life.
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
