Possible Views Integration?

One way to get Views integration would be to save each contact message as a node. Then it would be easy to integrate with Views, CCK, Rules... anything which deals with nodes (which is everything). If we go that route, we would expose a custom content type... something like "Contact Submission", similar to how Webform does it. Do you like that language, or should it be something else? "Submission", "Contact Form Submission", "Contact Message"?

I thought a little more about your request, and I don't see a clear path to integrating this in any smart way with Views. Since contact submissions are not nodes, the "view type" would have to be something like "Contact submission". It wouldn't center around the node, so it would be very limited (similar to how a Term or User view is limited).

In fact, if you really want more control over the presentation and management of your contact form submissions, I recommend creating a custom content type, use CCK to add your form fields, and then use Rules to send an e-mail to the proper destination. Then, you could easily create your Views.

While I'm on the subject of alternatives, I might mention two other alternatives to this module, and why I think there is still a need for Contact Save.

Mail Logger logs all outgoing e-mail, which meets the first need of Contact Save. However, it logs everything, including auto-replies and CCs... it's main purpose is for logging. Contact Save is specifically geared toward the core Contact module, saving only the submissions, and giving admins the ability to respond through the website to those messages which never arrive in their inbox.

Webform also saves form submissions, which again meets the first need of Contact Save. So, if you are building a simple form without conditional recipients, then Webform is the way to go. However, if you want to send the email to different recipients based on the category the user selects, that is trickier. Yes, you can do it with Webform, but you either have embed the email addresses in the HTML (which lets spammers harvest them #422026: Anyway to protect emails in a select list?), or you have to use the "additional processing" field to map the category the user chose with the proper email address (something which most people will find difficult). Perhaps if one of these two tickets gets resolved, Webform will be the way to go:

#687606: Add conditional email sending feature

#282436: Multiple Options, Same Value in 'Select' Form Element (+ Protect from Spam Harvesters)