When your boss tells you, in so many words, that you should consider seeking alternative employment because he doesn't know where the company's going, why, it makes you want to drink youself into a goddamn stupor. SO WITHOUT FURTHER ADO... HEY, IS IT A CRIME AGAINST DECENCY TO PUT CUBAN RUM IN DR PEPPER? I NEED TO KNOW FOR A SCHOOL PROJECT.
When your boss tells you, in so many words, that you should consider seeking alternative employment because he doesn't know where the company's going, why, it makes you want to drink youself into a goddamn stupor. SO WITHOUT FURTHER ADO... HEY, IS IT A CRIME AGAINST DECENCY TO PUT CUBAN RUM IN DR PEPPER? I NEED TO KNOW FOR A SCHOOL PROJECT.
<dkim-milter-discuss@lists.sourceforge.net>: host mail.sourceforge.net[66.35.250.206] said:
550-Postmaster verification failed while checking <rone@eforceglobal.com>
550-Called: 209.177.149.166
550-Sent: RCPT TO:<postmaster@eforceglobal.com>
550-Response: 550 <postmaster@eforceglobal.com>: Recipient address rejected: eforceglobal.com
550-Several RFCs state that you are required to have a postmaster
550-mailbox for each mail domain. This host does not accept mail
550-from domains whose servers reject the postmaster address.
550 Sender verify failed (in reply to RCPT TO command)
Yeah, yeah, it would be nice if eFORCE's mail server were RFC-compliant, but at the same time, i'd love to print out section 2.10 of RFC 793, roll it up, and smack SourceForge's nose with it.
<dkim-milter-discuss@lists.sourceforge.net>: host mail.sourceforge.net[66.35.250.206] said:
550-Postmaster verification failed while checking <rone@eforceglobal.com>
550-Called: 209.177.149.166
550-Sent: RCPT TO:<postmaster@eforceglobal.com>
550-Response: 550 <postmaster@eforceglobal.com>: Recipient address rejected: eforceglobal.com
550-Several RFCs state that you are required to have a postmaster
550-mailbox for each mail domain. This host does not accept mail
550-from domains whose servers reject the postmaster address.
550 Sender verify failed (in reply to RCPT TO command)
Yeah, yeah, it would be nice if eFORCE's mail server were RFC-compliant, but at the same time, i'd love to print out section 2.10 of RFC 793, roll it up, and smack SourceForge's nose with it.
It looks like gBox has sold off all of its employees to eFORCE Global, who will then turn around and rent our services to gBox to support the application. We get new offer letters on Tuesday. This happened after another deal we had on the table fell through earlier this week, primarily due to rampant ego problems on the part of our angel funder.
On the plus side, this is the last time he's going to screw us. But it's hard to imagine that the team we have now will remain intact after this 270° jerk. And, naturally, it's entirely possible we're all going to get lowballed on Tuesday. I wanted to come here, and decided to stay, because i'm calling the shots and rebuilding the infrastructure in my own image, and i accepted the risks because of that. But it still sucks.
It looks like gBox has sold off all of its employees to eFORCE Global, who will then turn around and rent our services to gBox to support the application. We get new offer letters on Tuesday. This happened after another deal we had on the table fell through earlier this week, primarily due to rampant ego problems on the part of our angel funder.
On the plus side, this is the last time he's going to screw us. But it's hard to imagine that the team we have now will remain intact after this 270° jerk. And, naturally, it's entirely possible we're all going to get lowballed on Tuesday. I wanted to come here, and decided to stay, because i'm calling the shots and rebuilding the infrastructure in my own image, and i accepted the risks because of that. But it still sucks.
