Hello Mumara Team and Community,
I've compiled a list of feature requests that would significantly improve workflow, deliverability, and management within Mumara Campaigns. I hope these can be considered for future development.
---
1. Tracking Link Parameter Encryption
Category: Tracking & Performance
* Problem: Long tracking links (often exceeding 200-250 characters) can cause issues with certain email clients, messaging apps, or link previews that truncate URLs. This can break tracking and degrade the user experience.
* Proposed Solution: Add an option to encrypt the parameters in tracking links (e.g., everything after the `?`). This would dramatically shorten the overall URL length.
* Example:
* Current: `https://click.domain.com/27XHWN53/HFZR2M6/?contact_id=19598&list_id=15367...` (very long more than 250 characters)
* Requested: `https://click.domain.com/27XHWN53/HFZR2M6/?__efq=1XzZiNTLF3DLgyluxV8QOs9Y` (under 120 chars)
* Benefit: Improved compatibility across all platforms, cleaner-looking links, and maintained tracking integrity.
---
2. Node-Specific List-Unsubscribe Mailto Header
Category: Compliance & Deliverability
* Problem: When scheduling a broadcast using multiple nodes (from different IPs/domains), the `List-Unsubscribe` header must point to an endpoint that can handle the unsubscribe request for that specific node's context. Currently, it's unclear if this is node-specific.
* Proposed Solution: In the Node Settings, add a field to define a `List-Unsubscribe: mailto:` email address for that specific node. During broadcast scheduling, the user should be able to confirm which `mailto` address to use, similar to how the unsubscribe link is confirmed.
* Benefit: Ensures RFC compliance and optimal inbox placement by providing a accurate, node-specific unsubscribe method within the email headers.
---
3. PowerMTA Command Control Dashboard
Category: Infrastructure & Management
* Problem: For users managing a multi-node PowerMTA infrastructure, executing common commands (e.g., restart, stop, start, view queues) requires individual SSH access to each server, which is time-consuming.
* Proposed Solution: Create a dedicated dashboard/page within Mumara for nodes using PowerMTA integration. This page would allow authorized users to execute common PowerMTA commands directly from the Mumara interface, with the ability to perform actions on multiple nodes simultaneously.
* Benefit: Massive time savings for server administrators, quicker response to issues, and centralized monitoring of the sending infrastructure.
---
4. Advanced Segment Organization with Grouping
Category: Contacts & Segmentation
* Problem: As the number of segments grows, managing them becomes difficult in a single, flat list. Finding and organizing related segments is inefficient.
* Proposed Solution: Introduce a secondary view for managing segments, mirroring the functionality of the "Secondary View" for contact lists. This should allow users to create groups (and potentially subgroups) to categorically organize segments (e.g., "Engagement Segments," "Geographic Segments," "Product Interest Segments").
* Benefit: Drastically improves segment management, clarity, and efficiency, especially for large-scale accounts with complex segmentation strategies.
---
5. Modernized DKIM DNS Record Generation (h=sha256)
Category: Security & Deliverability
* Problem: The current DKIM record generated by Mumara does not explicitly specify the signing algorithm (`h=sha256;`). While the implicit default is often acceptable, explicitly defining the stronger `sha256` algorithm is a modern best practice.
* Proposed Solution: Update the DKIM DNS record generator to include the `h=sha256;` tag.
* Current Format: `v=DKIM1; k=rsa; p=MIICIjANB...`
* Requested Format: `v=DKIM1; h=sha256; k=rsa; p=MIICIjANB...`
* Benefit: Adherence to modern security standards, potentially improving authentication results with strict DMARC policies (e.g., `reject`), and signaling to receiving mail servers that stronger cryptography is used.
---
Thank you for considering these enhancements. I welcome feedback from the community as well.
I've compiled a list of feature requests that would significantly improve workflow, deliverability, and management within Mumara Campaigns. I hope these can be considered for future development.
---
1. Tracking Link Parameter Encryption
Category: Tracking & Performance
* Problem: Long tracking links (often exceeding 200-250 characters) can cause issues with certain email clients, messaging apps, or link previews that truncate URLs. This can break tracking and degrade the user experience.
* Proposed Solution: Add an option to encrypt the parameters in tracking links (e.g., everything after the `?`). This would dramatically shorten the overall URL length.
* Example:
* Current: `https://click.domain.com/27XHWN53/HFZR2M6/?contact_id=19598&list_id=15367...` (very long more than 250 characters)
* Requested: `https://click.domain.com/27XHWN53/HFZR2M6/?__efq=1XzZiNTLF3DLgyluxV8QOs9Y` (under 120 chars)
* Benefit: Improved compatibility across all platforms, cleaner-looking links, and maintained tracking integrity.
---
2. Node-Specific List-Unsubscribe Mailto Header
Category: Compliance & Deliverability
* Problem: When scheduling a broadcast using multiple nodes (from different IPs/domains), the `List-Unsubscribe` header must point to an endpoint that can handle the unsubscribe request for that specific node's context. Currently, it's unclear if this is node-specific.
* Proposed Solution: In the Node Settings, add a field to define a `List-Unsubscribe: mailto:` email address for that specific node. During broadcast scheduling, the user should be able to confirm which `mailto` address to use, similar to how the unsubscribe link is confirmed.
* Benefit: Ensures RFC compliance and optimal inbox placement by providing a accurate, node-specific unsubscribe method within the email headers.
---
3. PowerMTA Command Control Dashboard
Category: Infrastructure & Management
* Problem: For users managing a multi-node PowerMTA infrastructure, executing common commands (e.g., restart, stop, start, view queues) requires individual SSH access to each server, which is time-consuming.
* Proposed Solution: Create a dedicated dashboard/page within Mumara for nodes using PowerMTA integration. This page would allow authorized users to execute common PowerMTA commands directly from the Mumara interface, with the ability to perform actions on multiple nodes simultaneously.
* Benefit: Massive time savings for server administrators, quicker response to issues, and centralized monitoring of the sending infrastructure.
---
4. Advanced Segment Organization with Grouping
Category: Contacts & Segmentation
* Problem: As the number of segments grows, managing them becomes difficult in a single, flat list. Finding and organizing related segments is inefficient.
* Proposed Solution: Introduce a secondary view for managing segments, mirroring the functionality of the "Secondary View" for contact lists. This should allow users to create groups (and potentially subgroups) to categorically organize segments (e.g., "Engagement Segments," "Geographic Segments," "Product Interest Segments").
* Benefit: Drastically improves segment management, clarity, and efficiency, especially for large-scale accounts with complex segmentation strategies.
---
5. Modernized DKIM DNS Record Generation (h=sha256)
Category: Security & Deliverability
* Problem: The current DKIM record generated by Mumara does not explicitly specify the signing algorithm (`h=sha256;`). While the implicit default is often acceptable, explicitly defining the stronger `sha256` algorithm is a modern best practice.
* Proposed Solution: Update the DKIM DNS record generator to include the `h=sha256;` tag.
* Current Format: `v=DKIM1; k=rsa; p=MIICIjANB...`
* Requested Format: `v=DKIM1; h=sha256; k=rsa; p=MIICIjANB...`
* Benefit: Adherence to modern security standards, potentially improving authentication results with strict DMARC policies (e.g., `reject`), and signaling to receiving mail servers that stronger cryptography is used.
---
Thank you for considering these enhancements. I welcome feedback from the community as well.