SECURITY ALERT: Impact of Heartbleed bug of OpenSSL on Mithi Connect Xf

This security message is to notify you of a major security vulnerability that has just surfaced within the past 3 days, and referred to as Heartbleed. We urge you to read up our security alert/announcement about this bug in OpenSSL and its impact on Mithi Connect Xf, which is deployed in your environment, and whether you need to take any action.

See more at: http://www.mithi.com/forum/security-alerts/380-impact-of-heartbleed-bug-on-mithi-connect-xf.html#384

Posted in Connect Xf Email Server | Tagged , , , | Leave a comment

How does Mithi SkyConnect co-exist with Google Apps on the same SMTP Address space (email domain)?

Requirement:

There is a requirement to host the email infrastructure of a company across 2 different solutions, such that both the solutions share the same SMTP address space and the company can divide their mailboxes across the two solutions. This is typically done to allow a set of users to use one of the solutions for the value that it offers and allow the remaining users to derive benefit from the value delivered by the other mailing solution.

Essentially your critical requirements are not met entirely by one solution, but the benefits offered by that solution cannot be ignored either. In the case of Google Apps (GApps), some of the key management people, may need to use the GApps features and may need tighter integration with their G+ profiles etc, which will not be available with the Mithi solution. At the same time, the remaining set of users, have no need for all the capabilities of GApps and it would be most effective to host them on a simpler solution.

A Co-existence solution, as the name suggests, is a solution where 2 or more mailing systems work seamlessly together to provide a common/ shared address space (email domain name like acmecorp.com), and if possible a centralized directory for authentication and personal properties of entities (users, groups), and common contacts of all mailing systems to all users.

Such a solution allows the organization to host separate groups of users on different systems depending on their usage requirements. E.g. in an organization with 1000 users, a typical co-existence between Connect Xf/Mithi SkyConnect and GApps will allow the organization to host 100 users on GApps and 900 on Connect Xf/Mithi SkyConnect, sharing a common domain name in their email ids, and with seamless mail flow between the users of both systems.

Key benefits of such a setup

  • It provides the critical features/ functionalities required by the top management in a way they would want.
  • It also enables the organization to save big time on the overall infrastructure, management and upgrade costs, by ensuring that a majority of the users remain on a low-cost, resource-efficient system.
  • It brings in value from the open world, which gives the business an IT edge, like archival, mobility for almost all types of devices, access to free clients and applications like Thunderbird, Jabber chat clients etc. E.g. With open technologies, you could use any Android based phone/ pad/ tab, iPhone, iPad, to get seamless access to email, calendar, chat, and address book, while on the move. A possibility like this allows the field force to be more connected to each other and not just the top management.

Working

To explain the working, we have assumed an example domain of acmecorp.com and also assumed that there would be 100 users on GApps and 900 users on the Mithi Setup (Connect Xf or Mithi SkyConnect).

The GApps system has a feature which supports such co-existence configurations to share an SMTP address space. This is done via the
Google Apps > Settings for Email > Advanced Settings – Routing (Email routing)

You would need to configure catchall routing as explained below.

Setup:

  1. On GApps setup, add the acmecorp.com domain and configure the 100 users, who will use the GApps setup.
  2. Also Add an alias to this domain called gapps.acmecorp.com
  3. On the Mithi setup, configure the remaining 900 user accounts who will access their mailboxes from the Mithi setup.
  4. On the GApps setup, configure the email routing for the catchall account (all mail meant for unknown email ids of acmecorp.com) to push this mail to the Mithi Connect Xf or Mithi SkyConnect server host name as the destination.
  5. On the Mithi setup, add and configure the remaining 100 accounts (whose mailboxes are on GApps) to forward mail to the corresponding email id on the alternate domain viz. gapps.acmecorp.com (forward to alternate domain)

The mail flow explanation which is below will make it clear as to why we need an additional domain as an alias on GApps.

Hybrid solution of GApps with Mithi SkyConnect for sharing same email domain name (SMTP address space)

Co-Existence between Google Apps and Mithi SkyConnect or Connect Xf

Inbound Mail flow:

The MX for acmecorp.com and gapps.acmecorp.com will land on the GApps servers, which will deliver mail locally for the users hosted on the GApps server, and forward mail for unknown users to the host name specified for the Mithi server. GApps will assume that if the mail is destined for an email id of acmecorp.com, which doesn’t exist on GApps as a mailbox, is a user on the foreign email system and will use the configured destination host to route mail to the foreign mail server.

Mail destined for gapps.acmecorp.com is aliased to acmecorp.com e.g. mail sent to user@gapps.acmecorp.com is translated to user@acmecorp.com via the domain aliasing capability.

Local Mail flow on acmecorp.com domain:

  1. GApps to GApps: An acmecorp user of the GApps system sends a mail to another acmecorp user on the GApps system. This mail is routed internally within GApps and delivered to the recipient.
  2. GApps to Mithi: An acmecorp user of the GApps system sends a mail to another acmecorp user on the Mithi system. Since the recipient ID is unknown, GApps will route this mail via the catchall configuration to the Mithi server. The Mithi server accepts the mail and delivers it to the recipient’s mailbox.
  3. Mithi to GApps: An acmecorp user of the Mithi system sends a mail to another acmecorp user on the GApps system. The Mithi system will attempt to deliver the mail to the acmecorp.com recipient on the Mithi system, who is configured to forward the mail to an alternate domain with the same user id (forward to alternate domain). E.g. if useronmithi@acmecorp.com sends a mail to userongapps@acmecorp.com, the mail delivery configuration of this user instructs the Mithi system to forward the email to userongapps@gapps.acmecorp.com. This is routed to the Internet as an outbound mail and is received via the GApps system on the MX landing points. Thus the GApps system receives a mail for userongapps@gapps.acmecorp.com, and because of the domain alias configuration of the gapps.acmecorp.com domain and the acmecorp.com domain, the mail is delivered to the userongapps@acmecorp.com, which is then delivered to the recipient’s mailbox locally.
  4. Mithi to Mithi: An acmecorp user of the Mithi system sends a mail to another acmecorp user on the Mithi system. This mail is routed internally within the Mithi server and delivered to the recipient.

Outbound Mail flow:

  1. GApps to Internet: An acmecorp user on GApps sends a mail to an external recipient. This mail is routed to the Internet directly from the GApps system.
  2. Mithi to Internet: An acmecorp user on Mithi sends a mail to an external recipient. This mail is routed to the Internet directly from the Mithi system.

Virus and Spam control:

  1. Since MX is landing on GApps, the spam and virus scanning for all the mail is done by the GApps system. Thus the spam scanning on the Mithi system is disabled since it is redundant.
  2. Outbound mail from GApps are scanned for Spam by the GApps system
  3. Outbound mail from the Mithi system are not scanned for spam.
  4. The virus control engine is enabled on the Mithi system and all mail (inbound, outbound and local) are scanned for viruses.

Deliver-ability:

To ensure that the recipients can perceive the hybrid mailing system to be one, its important to configure the SPF record to contain the IP addresses of the outbound relay servers from both GApps and the Mithi setup. The SPF record has to be configured with your DNS service provider.

Address Books

The Mithi users will see the entire address book since all the 1000 users are added to the directory (although 100 of them will not have their mailboxes there). This makes it possible for the users of the Mithi system to see a complete global address book comprising of all 1000 users. As for the GApps users, they will only see an address space of 100 users unless you can populate the Global address list on GApps with all the 1000 users and also maintain this during provisioning (Adding and deleting users)

Authentication

The users on GApps and Mithi will maintain their own passwords in the respective directories and via the respective interfaces. The password policies etc will apply from the separate systems respectively.

Archival

Using this kind of coexistence, it is possible to achieve seamless mail flow, but not possible to have archiving done for all mail of all users at a single point. The archival will necessarily need to be configured at two different points, viz. for the 100 users on GApps and for the 900 users on the Mithi system.

Cross References:

http://www.mithi.com/emailserver-workingofcoexistence

http://www.mithi.com/forum/15-coexistance/233-co-existence-on-cloud.html

http://www.mithi.com/forum/15-coexistance.html

Posted in Collaboration Infrastructure | Tagged , , , , , , , , , | Leave a comment

The One Page Execution Plan for a business of any size

Greetings!

Is your business stuck in a low/no growth rut? In your business, do you observe any of the following symptoms

Symptoms:

  1. Your company consistently misses financial targets (even realistic ones)
  2. Your company consistently is unable to achieve all that it sets out to do (Goals)
  3. Many team members complain of lack of clarity in what is expected of them
  4. Many a times, you produce something which is not really required at that point in time
  5. Most days, you come in and start the day afresh with new ideas and next best thing to do. Its as if there is no continuity (And you dont just leave it an idea but change priorities of the relevant teams and put it to play.)
  6. … and so on and so forth.

In other simple words
“You keep feeling that you are just not getting there”

Diagnosis

Analysing why a business experiences such symptoms, could be the topic of a big book (several books). And hundreds of books/articles have been written on this subject. A lot of businesses and consultants exist to just help your business go past such constrictive phases.

The problem could be in many parts and aspects of your business. From something as basic as whether there is need for your product in the market, Funding, to your strategy, to your team composition and right onto the execution where the rubber meets the road.

My purpose here is to help you sort out ONE possible cause for this, and that relates to point 4 above (execution). Hence I assume that your product has an accessible market, you have adequate funds, and your strategy is good, working by proof to some extent.

ONE possible Cause of poor execution
In our own business (Mithi) over the last few years, we have grappled with issues that come with scaling up and scaling out and experienced similar symptoms along the way. We were quite sure of our product, service and market since that was proven over the years by consistently releasing solid product versions and acquiring large marquee customers whose businesses depended on our solution. When we embarked on a program (strategy) to REACH out to more customers, acquire and service them in high SPEED, and at the same time continue to grow in PRODUCT EXCELLENCE, our ways of working and our systems were severely challenged by these new goals.

Looking deeper we discovered that one reason for us slowing down was lack of ALIGNMENT amongst teams (to some extent the teams were pulling in different directions and their efforts and results were not adding up CONSISTENTLY to the final goal). Put another way, given ENOUGH TIME, we would “GET THERE” for sure. But it would be an excruciatingly slow journey

Solution

We felt that to fix this execution gap, we needed:
I. Clear unambiguous TARGETS CLEARLY COMMUNICATED to the teams
We broke our targets into two types viz. Leading Indicators and Lagging indicators.

Lagging indicators are numbers which measure the results you wanted for your business. Typically financial targets and may include numbers like number of customers acquired etc.

Leading indicators are numbers which measure the output of the activities that you chose for achieving your business targets. E.g. number of mailers sent out, number of calls to be made, number of product releases to be done, etc.

While deciding these, you must be able to make the connection that consistently achieving the Leading indicators (execution of chosen activities/initiatives HAS a very high chance of achieving the Lagging indicators (results)

II. Clearly documented milestones, which are repeatedly communicated to respective teams

  • The strategy had to broken into short term, medium term and long term projects/initiatives for each department with monthly milestones defined.
  • The monthly milestones to be further broken down into weekly milestones
  • The above to be DOCUMENTED top down, and CLEARLY COMMUNICATED to each department’s team REPEATEDLY

Note: The above projects if viewed from a birds eye, should give an indication of each initiative adding up to take the company TOWARDS its goals. In this definition, the sequence of events and date/time based milestones have to be properly thought out. E.g. a particular initiative, lets say promoting a new feature in the marketing department obviously cannot happen unless the feature is ready and released by the product team.

III. Routines
Never underestimate the power of routines. These define the activities to be done periodically for the entire company. E.g. the marketing team to send weekly mailers, the product team to do perform daily builds and daily upgrades on the inhouse servers, daily monitoring of critical resources, monthly team meetings, etc.

I plan to write a separate article on routines, but suffice it to know that consistently performing routines, day on day, week on week, month on month can add up tremendously to achieving solid depth and results in those areas of work.

Routines also bind the deliverables of each team, since there is always an interdependence.

IV. Weekly Reports to indicate progress
You need indicators to show progress (or the lack of it) and not “touchy feely” discussions. Establish a system to generate weekly reports on all agreed upon leading and lagging indicators and don’t just stop there.

V. Have Weekly reviews, around the indicators to course correct
Have weekly reviews around the reports to understand the gaps in execution, decide upon the changes to the plan, make the changes to the overall plan and proceed into the next week.

One of the most important things about this is that the execution plan should be available in one page to allow that top view (which is what is typically missing once you deep dive into the execution). Looking at this weekly will reset your vision to the targets and the milestones and this very simple exercise itself will increase clarity and dramatically increase your chances of reaching your targets.

Its not a new science that you must define targets, define a strategy, break it down, clearly communicate it and follow through on it. Such methods are followed by thousands of successful businesses around the world. Via this post, I am not really proposing a radically different way of execution, but just a simple tool to tie up all the elements required for effective execution (will talk about this in my next post)

In essence it is about

  1. All of you agreeing to the direction to go
  2. All of you having the necessary team work to pull in the same direction
  3. All of you being result foccussed by measuring and course correcting continuously

Is any of this rocket science? Of course not.

Do you follow this in your business? You may want to ask yourselves?

Posted in Getting Better | Tagged , , , , , | Leave a comment

How does Connect Xf or Mithi SkyConnect prevent email spoofing?

Q We have our hosted setup and we had one very bad experience of an email compromised after sending. It was in between changed/manipulated and sent to the recipient. That resulted in major loss. The  originator did not send that content in the email. Will hosting in Mithi Cloud prevent it? How?

What you are describing is called “Email Spoofing”. A user sends a mail but makes it appear as if it was sent by another user. There are various ways “spoofers” achieve this:

To explain the scenarios, lets take an example: Ravi and Smita are colleagues in the same organisation and Ravi sends a mail on behalf of Smita (Ravi has spoofed Smita’s email id)

1. Ravi hacks into Smita’s email box (since she has a weak password and the email system doesn’t have any password security in place e.g. password history, account lockout, password age, etc) and sends a mail on Smita’s behalf. In this scenario the mail has gone from Smita’s account, but she is unaware of it.

From a Mithi solution perspective, the chance of this happening is vastly reduced by applying the following security policies for each account

  • Strict Password Policies to ensure complex password, regular password rotation, automatic account lockout on several unsuccessful attempts and always fresh passwords by referring to the password history.
  • Access control to define which services the user can access and the trusted network ranges from which the user can access the server.
  • Mail Policies to control whereall each user can send mail and under what condition.
  • Every mail send request requires authentication by the a valid sender in the network.

2. Ravi impersonates Smita: Ravi connects to the organisation mail server, authenticates using his own account but sends a mail containing Smita’s email id in the “From ID” header. When the recipient gets this mail, it appears to have been sent from Smita’s email id. This is possible with mail servers which have a weak authorisation system.

From a Mithi solution perspective, this can be prevented by applying the following security policies for each account

  • Email Spoof Check: This means that if Ravi is authenticating then the mail should also contain ONLY Ravi’s email id in the “From ID” field. If the authentication id and the From ID don’t match, the mail will be rejected. Here is a detailed explanation on how email spoofing is prevented in Connect Xf.
  • Domain Spoof check: This means that if a mail gateway server in the client’s premises has been authorised to send mail via Connect Xf/Mithi SkyConnect, the mail originating from that server must belong only to the listed domains. This prevents the mail gateway server from sending mail from foreign domains (open relay) in case it gets compromised.

3. Ravi impersonates Smita from an external mail system: Ravi sends a mail to the recipient on Smita’s behalf but by using an external mail server or mail sending toolIn this method, Ravi sends a mail using a tool and using the services of an open relay server on the Internet or by creating his own server. He composes the mail and sets Smita’s email address in the mail header (MIME structure).

Modern mail servers and mail landing services, now easily detect this by

  • IP reputation of sender. The IP of the server from which the mail originates should belong to the sender’s domain as designated by the Sending organisation in the SPF record in the DNS. Hence, while Ravi will succeed in sending the mail, the recipient server will reject the mail in all likelihood due to bad IP reputation.

In case the recipient mail server doesn’t have strong policies, it may accept the mail and deliver it to the recipient and the mail may appear that it came from Smita. On closer inspection of the mail, it is possible for the recipient to determine that it is a spoof however, but this needs technical expertise of understanding mail headers.

4. In transit  modification of mail.Normally mail can sniffed in transit (i.e. the contents can be read) and modified at hop points by mail administrators if they have the privilege. Under normal working conditions these are rare situations. However from a Mithi deployment perspective we ensure that the following practices are followed to bring the chance of this happening to near zero

  • SSL/TLS: All access to services happens over secure encrypted layer. This means that all the data flow from client to server and server to server is encrypted over SSL/TLS.

Considering all the above systems deployed by Mithi SkyConnect, there is near zero chance of a spoof mail making it through the network

Other references:

  • http://www.mithi.com/connectxf-datasheet-mailpolicy/131.html
  • http://www.mithi.com/support-internalspamattacks.html
  • http://luxsci.com/blog/the-case-for-email-security.html
  • http://www.mithi.com/product-productdatasheet.html#Security

Posted in Connect Xf Email Server | Tagged , , , | Leave a comment

The Myth of Delegating Responsibility via Email

Yes! Yes! the post title has a contradiction, which is deliberate…please bear with me and read on.

Dropping the ball

1. Sales team requesting for special help from the product management team

Mail from a sales team member Maria to the product team member, Ravi
“Dear Ravi,  - Can you please create a comparison document between our product and the ZDF product and send it across to Mr. Sen of AcmeCorp asap. Your team is in the best position to create this since you have in depth competitive knowledge. – Cheers, Maria”

After a few days, when Mr. Sen followed up for the comparison document (He must desperately want your product to be following up for co-laterals from your ultra-responsive sales team), Maria exclaimed in surprise
“But I thought Ravi would have sent it to you. I had sent him a mail asking him to. let me check and Revert”

Angry mail from Maria to Ravi, with a CC to Ravi’s boss.
“Dear Ravi – Please explain why you didnt send the comparison document to Mr. Sen as per my instructions. The customer is very upset at this delay and lapse. Its shocking to have the customer follow up for documents he had asked for. This demonstrate how poor our response is. – Maria”

Response from Ravi.
“Dear Maria – Ooops!! when I saw your mail, I was kind of tied up with some other activities and the mail went out of site. I do apologize for this. I’ll get cracking on it right away. – regards, Ravi.”

2. A few escalation mail (amongst about 200 mail received daily) to the Service Manager.

The Service Manager’s response to each:

“Dear Mr. Customer – I’ll check on this with my team and revert by tomorrow. – regards, SM”

The next day the Inbox lands a few more and some reminders from the customers about their unattended complaints.

3. Minutes of the meeting being circulated among the attendees

4. Boss questioning a direct report.

Boss – “What happened about the meeting at Acmecorp? “
Ravi – “Hmm, I had sent a mail to Kavi to meet Acmecorp since he is in Delhi itself. Looks like I will have to followup.”
Boss – “But the issue is important and should have been attended before the last month end. We are late on this.”
Ravi – “I know, but I had instructed Kavi well before time. I would have to pull him for this lapse.”

I could go on writing scores of examples (several of which I myself encounter on a daily basis) of such hanging conversations, leading to delayed deliveries, misunderstanding among team members and eventually negative business impact. This is what we call “Dropping the ball”

So who is responsible for the outcome of the conversation?

Lets assume that Maria is running a sales process to work towards closing opportunities and at some stage needs help from a product team member. This maybe an exception. Under normal circumstances, the marketing material is well stocked and available easily.

Once Maria fans out the work, and gets busy with other opportunities, this issue is more likely to be off the radar. It would come to fore, only when Mr. Sen demands the document he asked for.

It should be noted that Maria is the owner of the work and is wholly responsible to deliver the document. Its upto her to ensure Ravi completes it on time. If Ravi cannot do it on time, she has to figure out alternatives. Whereas, the entire conversation above is about blaming Ravi for not completing the document on time.

Who tracks commitments and ensures they are kept?

To a lot of mail, the Service Manager simply writes a line that he would check and revert by tomorrow or on a particular date. These are again exceptions since under normal circumstances, where the customer is well served, there would be no escalations.

Once the SM responds to one mail and moves to the next and the next, until he clears his Inbox, he is more likely to have forgotten the number of commitments.

A commitment is an unsaid bond of Integrity between the two parties and is expected to be honored by the Initiator.

Who will take action on a mail work on the various different aspects of the written matter?

MOMs (Minutes of Meetings) put on record the happenings, but are many a times not clear directions for who will do what. And if there is anything to do.

There is an unsaid, unclear assumption by the sender that the various people receiving the mail have the necessary context and behavior patterns to recognize that the MOM is also giving their work some direction and setting the expectation for delivery from the recipients. But does this really happen?

So what are the various types of official conversations we engage in?

So it seems that in our daily official work using multiple channels (verbal, email, chat, social media), we broadly have the following types of conversations (I believe all conversations fit into one of these types, if you have some others, please do let me know)

  • Simply share information which doesn’t expect any response or responsive action. (JFYI-Just For Your Information notes, Forwards, Alerts, Reports , Thank you notes, Vacation replies, etc)
  • Have an ongoing conversation about a subject which simply is to collectively build knowledge, refine the idea and may or may not conclude in actionables for either parties. (Ideating, Feedback, Working out the concepts, details about projects/Initiatives, etc)
  • Request for help from a colleague and/or external agency (Instructing a colleague, Lodging a complaint, Request for comment, etc)
  • Make commitments to a colleague or external agency for completing the promised action by a certain date and time (Response from Customer Support, response to an request for help, deferring the action due, etc.)
  • Capture happenings and events as an official record for action and future reference. (Minutes of meetings, sending official documents like orders, quotations, agreements, confirmations, approvals, etc.)

So how can we “hold” the ball instead of “dropping it” while still having these unstructured conversations

There is no disputing the value of email or talking in having such INTERACTIONS/CONVERSATIONS or sending information from one person to another or from one person to many people. However these conversations may remain just conversations unless the sender has a way to track the expectation from the recipient and the receiver has appropriate systems in place to act on these inputs.

Unless Maria has a tracking sheet or TODO list, which records that she has fanned out the work to Ravi and is expecting it by a specified time, and this tracking sheet is reviewed daily by Maria as a practice, and the items dont go off the list until they are complete, the ball is likely to be dropped.

Unless the Service Manager flags those pending conversations for action later and/or puts calendar reminders for the commitments, the commitments are likely to be compromised.

Unless the one to many communcation is clear with instructions to named people, the message is likely to remain vague. This would need to be combined with a system like Maria uses.

Unless Ravi can track the fact that he has fanned out a meeting to Kavi, and Kavi tracks that as an item/event to be attended to, the chance of that being missed is high (thanks to high level of interruptions)

So how do I manage my conversations

When I observe my way of working (also considering the large number of emails which make their way to my Inbox), I have developed this habit of scanning my mailbox 2-3 times a day by :

  1. Marking a mail as READ without opening based on sender and subject, if I am convinced it has no value to me at all at this point in time.
  2. Respond/Redirect mail ON THE SPOT, which don’t need too much analysis, design, review etc. Typically approvals, acknowledgements, re-directs, shares etc. This means I dont have to revisit this and the task is complete.
  3. For mail which need some work or review with my team, make a commitment with a date and time and RECORD THIS COMMITMENT in my TODO list/Calendar (I am old world guy and a traditional TODO list in notepad works best for me :-) )
  4. For the projects which I am working on, I may fan out tasks to my team members, partners, external agencies, etc and I RECORD THE INSTRUCTION in my tracking sheet/project planner so that I can look at them daily and follow up in case the “ball has been dropped”. This way I stay on top of the deliverables and its my responsibility.

Hence to put it simply my email box is NOT my workbench. Instead my TODO list, Calendar and Project planning sheets are my workbench. Email is just a carrier.

If the sender and the recipient can use these simple ways to track the work allocated, the benefits cannot even be measured.

On a larger scale how does this work

While the methods discussed above will work quite well for individuals, what should we do for email ids which are contact points for very large number of conversations like the customer support email id, sales email id, etc.

The most popular and most reliable way to handle this is to deploy a ticketing system which is hooked into the email system.

Thus the customer sends an email, which is automatically converted into a ticket with a unique id, the support staff have a special common interface to access these tickets, respond to them from the ticketing interface and also collate all back and forth responses into the same ticket to track the entire conversation, which may span across days. Thus inflow and outflow happens over email but the conversations are collated and tracked in a database and accessed via a special interface.

Conclusion

Sending out an email or a giving verbal instruction does not ensure that the task will be done, even if both the parties are highly committed. A system is required, which is more than the email inbox,  to support their functioning.

At the end of the day, the originator of the work is the person whose responsibility it is to see that the work is completed or the desired outcome of the conversation is achieved.

You can never really delegate responsibility! (the contradiction in the blog post title)

The medium of the conversation then is only about deciding the best, most suitable form to transport the information, present it and build understanding.

I would love to hear from my friends on their own work experience with conversations.

Posted in Getting Better | Tagged , , , , , , , , | Leave a comment

2 Restaurants: Same Location: 1 a Success: 1 a Failure

One of our favorite holiday spots is Goa. We enjoy relaxing on the beach spending the whole day alternating between the water, sun and shade and recharging our batteries with the solar energy :-) . Normally we stay at the same resort (comfort zone) which is a stones throw from the beach. On our earlier trips, sometimes we used to dine in an Italian restaurant which is housed within the resort. Great food, great ambiance, great service.

Recently on our vacation this year, we saw that the resort had started another restaurant in premise. This was a restaurant serving Indian cuisine.

I observed that whenever we made dinner plans, we never really felt like trying this new restaurant, whereas in all our 7 days, we managed to dine at the Italian restaurant twice. I also observed that it was season time, and there were foreign guests coming into the Italian restaurant, whereas the Indian restaurant had virtually no guests. Since I run a business myself, I was curious to learn from what was playing out, to make one of the restaurants successful and the other a virtual failure.

I ran through a little diagnosis to arrive at the possible cause:
1. I first looked at the location and ruled that out since both were in the same spot. The same footfalls were available to both businesses.
2. I then looked at their model and presentation. While they were different, they both were fairly good and standard. They both displayed prominent signages, prominently showed their menu at the gate to help the discerning visitor to take a decision, and had decent layouts.
3. I then pondered over whether the type of cuisine is making a difference and ruled that out as a possible cause since there were other Indian as well as Italian restaurants flourishing in the same market.
4. Its quite possible that simply by virtue of being around for longer, the Italian restaurant was more successful. Being longer, means word of mouth referrals would have built up a loyal guest following who revisit year on  year.
5. I did feel that the name of the Indian restaurant was not much suggesting that it was representing an Indian restaurant.
6. While all of the above were very minor considerations, I feel that the clear difference in the two restaurants was that of the attitude of the respective owners.

I recall that when we visited earlier, the owner of the Italian restaurant (an Indian business man from North India) would have conversations with us, while he would be waiting at the gate of the restaurant to draw in guests. I also recall how he would walk upto the guests as they would scan the menu and converse with them about their preferences and also inform them of any offers which were in play. Subsequent years, he would remember us and take the efforts to talk to us. All evening he would shuttle between the restaurant and the gate and do the selling himself. I have seen him personally standing and receiving orders from guests, so he can also consult them about the food.

I didn’t note any of this in the owners of the new startup. I observed them to be always preoccupied in their own little world and never found them selling, talking to guests or really being present on the floor. The staff of this restaurant would always be sitting around since there were no guests. Little did they realise that these were subtle gestures to keep guests away. The energy was that of “Are you sure you want to eat here”. Come to think of it, in all the 7 days we must have passed the restaurant 3-4 times a day while going to and from our room, but not once were we invited to have a meal at the restaurant, or any special offer made to us as resident guests. I must say that none of the owners made any effort to have conversations with us. I would say that resident guests are prime targets for in premise restaurants. Once they dine in, the word of mouth kicks in. Essentially I felt as if the owners were really not interested to run this restaurant, which obviously percolated down to the staff and all in all they put up a listless performance. It was almost as if they were happy not to have customers.

I feel that while systems and processes, presentation etc are necessary but these are not sufficient. Without a deep interest what you are creating, continuous improvement in the product and operations, and that entrepreneurial go-getter energy, most businesses, even great ideas are bound to fail.

On the other hand, the commitment energy of the owner is contagious and soon spreads to the people to create a rocking team. You have to just watch for getting into a founder’s trap :-)

Its all about attitude. Talent, Capability and Skill only compliment a great Attitude.

How’s your Attitude and Being?
Are you welcoming customers or driving them away?
Do you think of customers as a boon or a bane?
Do you look at customer complaints as problems or opportunities?
Are your best people facing the customer?
Do you have frequent conversations with your customers?

Our yoga institute (Param Yoga) has a very interesting and apt slogan
“How we do” matters more than “What we do”


Posted in Getting Better | Tagged , , | Leave a comment

Can we use a desktop based bulk mail software to send mail via Mithi SkyConnect?

To prevent misuse and SPAM from the service, Our solution accepts mail over SMTP with the following restrictions:

  1. A single mail cannot be to more than 35 recipients.
  2. A single user/emailid cannot send more than 150 mail a day unless you make a special request and we will whitelist that particular ID to be able to send upto 5000 mail a day. No email ID can send more than 5000 mail a day.
  3. All SMTP transactions are authenticated and the email id used as a sender should be from the configured domain only.
  4. The maximum size of the mail can be 15 MB

Note: The above values are true at the time of writing this article. For the latest up-to-date information on the policies applicable at Mithi SkyConnect, please click here.

You may review with the features of your bulk mail software to confirm that it adheres to the above policies especially:
1. Authenticated sender id
2. Sending one mail per recipient so that it doesn’t cross the maximum recipient limit.

Please note that either ways any single ID would be restricted to maximum of 5000 mail a day (which we will whitelist once you make a request to us).

Posted in Connect Xf Email Server | Leave a comment

Why don’t the ‘sent items’ from my Outlook client sync with my server mailbox’s ‘sent items’

If your Outlook (or any desktop email client) is connecting to the mail server over POP protocol than this will not work.

POP is a protocol which works only on the Inbox. Its a dated protocol, whose job is to retrieve the mail from the server, download it to the client and let the client do all the mail management. Once the mail is POPPED off the server, it is the client software’s responsibility to manage the mail.

The user can create local folders to bifurcate the mail, define rules to automatically do this, etc. Mail sent from such accounts are sent via SMTP on the server and are stored on the Sent Items of the client.

The POP protocol does not support writing back to the server and hence the sent items cannot be written back to the server.

All this comprises the local mail store (PST files in case of Outlook) and needs to be backed up and maintained.

The above note suggests that if the user is OK to maintain the mail on their client PC (backups, etc), you may use the POP protocol.

However if you need to maintain your mail on the server and be in sync across multiple devices and clients, it is highly recommended to use the IMAP protocol for accessing your mail. The IMAP protocol is also very efficient and higher performing. Using this, all the IMAP folders are maintained in sync across all access clients and devices. This allows you to get a uniform view no matter what client you use. This includes the sent items as well.

References:

http://xf.wiki.mithi.com/index.php/Mail_sent_by_Blackberry_not_appearing_in_sent_items_of_desktop_client

http://www.makeuseof.com/tag/pop-vs-imap/

http://www.ucl.ac.uk/isd/staff/mail/faq/imap-pop

Posted in Connect Xf Email Server | Leave a comment

Message bounced due to sending limit – How many emails can I send via Mithi SkyConnect SMTP? Is there a limit?

This limit has been imposed to prevent spam attacks on servers from clients who exploit this if they get authenticated access.

The way it works is that, if a spammer gets authenticated access to a mailbox, he can send multiple spam mail in one connection (upto the limit of max recipient count) and repeat this, thus flooding the queue with junk mail. Another way this happens is that the client PCs (typically those having MS Outlook) can get infected with viruses and these viruses send mail via the server (without the user’s knowledge).

To prevent such spam attacks (which are very common), we have imposed a restriction on the maximum number of recipients in a single mail. This is a common practice and is followed worldwide by leading mailing companies e.g.

https://support.google.com/mail/answer/22839?hl=en

http://help.yahoo.com/l/us/yahoo/smallbusiness/bizmail/pop/pop-36.html

We suggest that if you want to send mail to multiple recipients
1. You may make a Group (distribution list) with your contacts and send a single mail to the DL. There is no limit on how many recipients can be added to the DL/Group
2. You could use a bulk mail software application on your desktop (there are several free ones too) to send mail to multiple recipients, one at a time. Mind you but this would be limited to the maximum number of mail allowed for a single sender.
3. You may use the services of a bulk mailing service if you have a large number of recipients for your mail.

For more information about the limits imposed by MithiSkyConnect, please visit this link

http://xf.wiki.mithi.com/index.php/Mithi_SkyConnect_Service_Level_Agreement-SLA#What_are_the_policies_applicable.3F

 

Posted in Collaboration Infrastructure, Connect Xf Email Server | Leave a comment

Reasons why Enterprise choose Mithi’s SkyConnect over an ISP mail solution

SaaS or PaaS ?

Abstract
Business should consider carefully whether they want to be delivered  a true SaaS solution (Software as a Service) or an infrastructure-focused PaaS solution (Product as a Service). While the former is about providing Managed Services, the later is about providing Infrastructure and Product. The difference could be big.
Software as a service is usually run by software makers themselves, while PaaS could be provided by third party vendors who provide the Product and the Infrastructure.
The depth of understanding and capability between different PaaS providers could vary considerably, with varying quality of services. On the other hand the software makers usually have the deepest insight into their products and can therefore can exercise the most amount of control on the quality of service around their product.

Leveraging existing Product and learning
E.g. With an installed base of 3,50,000 mailboxes & 600 servers worldwide managing in-house email setups for some of the leading businesses in India and with over 10 years of active development work behind its product, Mithi has a deep experience necessary to deliver high quality software services. Mithi’s cloud based email and collaboration software service is a natural progression, guided by the desire to provide a new delivery channel for an existing product that allowed existing customers quick and easy deployment and a smooth transition to the cloud.
Having the exact same product and service infrastructure that delivers the Connect Xf enterprise software for its SaaS solution SkyConnect, Mithi can deliver a much higher level of service and support to its customers than most PaaS providers.
With both the software maker and the service provider being the same, it is all built, tested, deployed  and managed by one team. As a result, customers are guaranteed a High Quality end user experience, with no buck-passing between platform provider and software vendor.

Devise new features by leveraging cloud capabilities
Mithi chooses to invest in developing new features around customer requirements rather than tool sets. E.g. by evaluating feedback from our customer base, it was easy for us to imagine a service where the customers wouldn’t have to install anything.
Therefore Sky Connect was designed with the following capabilities :
a.       Instant on
b.      Backup/Restore
c.       Remote Access (admin)
d.      Production and Staging
e.      Automatic Updates
f.        24X7 Support SLA.
When moving to the cloud, Mithi took the extra effort to leverage the inherent advantages of the platform we’re using.

Leveraging Capabilities for Flexibility, Performance and Reliability
The built-in security architecture, elaborate policies structure, reporting and strong back end (administrative) system to manage large number of users backed by an experienced support and delivery team ensures 24X7 availability and ensuring optimum performance, are all a result of leveraging the existing infrastructure, knowledge base & experience that comes from supporting mission critical email set-ups.
These features create true points of differentiation that are not easy to replicate by PaaS providers.

Try it for yourself.
As a prospective customers you can see, experience and interact with a product before taking it any further.  A free trial options allows you to create mailboxes on a Private Domain-Creating accounts on your mobile device and Desktop clients. Click here to Try it Now or write to us at presales@mithi.com for a personalized web demo for any specific feature or configuration.

Posted in Getting Better | Leave a comment