# Milestone M37 – DKIM-based email sending, better ticket creation & robust migrations

> NeetoDesk M37 introduces DKIM-based email sending, enhanced ticket creation with 2-way search, and improved bulk migration handling.
- **Authors**: Akash Srivastava
- **Published**: 2025-06-02
- **URL**: https://www.neeto.com/neetodesk/blog/milestone-m37-updates
- **Page title**: NeetoDesk Milestone M37: DKIM Email, Smarter Ticket Creation & Robust Migrations
- **Meta description**: NeetoDesk M37 introduces DKIM-based email sending, enhanced ticket creation with 2-way search, and improved bulk migration handling.
- **Keywords**: NeetoDesk, Milestone M37, DKIM email, ticket creation, customer search, bulk migration, attachment handling, email forwarding, and support automation

---

Let’s go through what we got done in milestone M37 (May 19 – Jun 01).

### **New features and enhancements 🚀**

#### ✅ **Support for DKIM-verified domains**

NeetoDesk now supports sending ticket emails from customer domains once verified using DKIM authentication.

#### ✅ **Improved attachment handling**

Attachment handling during bulk ticket migrations is now more robust—errors are isolated to specific faulty attachments.

#### ✅ **Smarter customer search in ticket creation**

Shipped 2-way search by email and name when creating tickets, making it easier to find and populate customer info.

#### ✅ **Track the original sender on forwarded emails**

When an agent forwards an email on behalf of a customer, the original sender is now tracked using a keyword in the subject body and attached to the ticket.

### **Bug fixes ⚒️**

#### ✅ **Web form submission fixes**

Resolved issues preventing web forms with Google reCAPTCHA from being submitted. Also fixed errors in embed previews.

#### ✅ **Duplicate attachment handling**

Fixed a runtime error caused by duplicate attachments in incoming emails.

#### ✅ **Special character fixes in migrations**

Handled improper character escaping during bulk ticket migrations.

#### ✅ **Response time seeding fix**

Fixed runtime errors caused by missing response time data in tickets created through migration.