What would stop you from trying bashemail (https://bashpilot.com/bashemail/) this month? Be specific about how you handle this today. Also say the maximum you would pay per month in USD (0 if nothing).

Jeffery Wymanneutral

Well, the biggest thing stopping me right now is that I've gotten pretty good at managing SpamAssassin and looking through Exim logs myself. It takes time, sure, but I know my system and my clients' needs inside and out. I'm also a bit hesitant about adding another moving part to the servers; reliability is key, and I worry about introducing potential issues. The pricing isn't fully clear either – is it per server, per client account? If it's unlimited accounts for $23 per month, that's doable. If it scales per account, it might get expensive quickly for 30 clients.

Simulated interest: 40/100

Antonia Goyetteneutral

The main hesitation for me is the potential disruption. We currently rely on a mix of built-in Plesk rules, whitelists, and manual triage for most of our 60 customers. While one cluster uses a third-party filter, I'm wary of introducing another change, especially without a clear pilot program. My team spends too much time logging outbound complaints manually into spreadsheets, so the promise of containing outgoing abuse is appealing, but I'd need to see how it integrates and if it truly simplifies our process without risking MX record issues. I'd be willing to consider up to $15 per month for this service, billed monthly.

Simulated interest: 30/100

Deependra Devarneutral

My current setup with Postfix and Rspamd is working well for filtering spam and malware for my agency clients, and I've refined the Rspamd rulesets to catch emerging threats. The key is that I don't require MX record changes, which is crucial for my clients. While BashEmail's promise of on-server filtering without DNS changes is appealing, I'd need to understand how it integrates with my existing Postfix configurations and if it can be as granular as my current manual header checks and custom Rspamd rules. I also recently centralized my mail logs, so I'd need to see how BashEmail handles logging and if it would complicate my current troubleshooting workflow. The pricing is unclear regarding what constitutes a 'hosting account' for my use case, as I manage individual VPS instances, not typical shared hosting accounts. I would be willing to pay $15 per month for this service, provided it integrates seamlessly and offers comparable or superior filtering without adding complexity.

Simulated interest: 50/100

Hendrik Sagonasneutral

What would stop me? The main concern is the time investment. Today, I handle spam with a combination of free filters and manually curated blacklists. It's time-consuming, but it's what we know and it works within our tight budget. Introducing a new system means learning it, integrating it, and ensuring it doesn't break our current setup, which I prefer to avoid if possible. I'd need to be convinced it saves more time than it costs to implement. If it truly automated much of the manual blacklist work and reduced false positives significantly, I might consider a price around $12 per month, as that's the lower tier advertised for a limited number of accounts.

Simulated interest: 40/100

Josephine Auer-Abbottneutral

The main thing stopping me right now is the time it takes to manage spam. I'm currently relying on the built-in cPanel filtering, manually checking quarantines, and using a spreadsheet for known senders. It's a bit of a manual process, and while it works, it's not ideal. I'd be willing to pay up to $23 per month for a solution that streamlines this, especially if it keeps mail on my server and avoids DNS changes.

Simulated interest: 60/100

Jayden Wagenaarnegative

The main hesitation for me would be how it integrates with our existing Plesk setup and Rspamd. We've built a fairly robust system for handling spam, with custom Lua rules and manual log tracing for outbound abuse, which is documented in a shared sheet. I'd need to be convinced that BashEmail doesn't disrupt this workflow or introduce unnecessary complexity. If it truly automates the outbound abuse tracing and offers granular control over Rspamd configurations without requiring extensive rewriting of our existing rules, I might consider it. For now, I'm not willing to pay for it, as our current methods, while manual, are effective and low-cost. $0 per month.

Simulated interest: 20/100

Brent Schimmelneutral

Honestly, what would likely stop me is the time it would take to properly integrate it and ensure it doesn't cause any issues for my clients. I currently handle abuse logs by making notes in a text file and reviewing them manually when complaints come in. It's a bit of a faff, but it's familiar. The product says it keeps mail on the server without MX changes, which is good, but I'd need to be sure it works seamlessly with cPanel and doesn't break anything. The pricing for unlimited accounts is $23 per month, which is a bit steep for my current operation given I'm a one-man band. I'd be looking at around $5 per month maximum, if I could be sure it was a significant time saver without any client-side disruption.

Simulated interest: 30/100

Wilma Steuberneutral

Our current process involves extensive use of spreadsheets and ticket tags to manage spam complaints and outbound reputation issues. While BashEmail's promise of filtering on the server without DNS changes is appealing, especially for our Plesk and DirectAdmin setup, I'm concerned about integrating a new tool. We'd need to understand how it impacts our existing workflows and if it truly simplifies things or just adds another layer. The "Lite" plan at $12 per month for up to 10 accounts seems affordable, but I'd need to see a trial to assess its effectiveness and integration before committing. I wouldn't pay more than $12 per month for this service.

Simulated interest: 40/100

Raymond Lucasneutral

I'd be hesitant to try BashEmail this month, primarily because integrating a new system with my existing patchwork setup could disrupt my clients' stability—not to mention the resistance I'd face from those tied to their DNS providers. Right now, half my fleet already uses a competitor, and the other half relies on manual log reviews. Adding another layer might complicate things further. That said, if I did pursue it, the key selling point for me would be the promise of no MX or DNS changes, which aligns with my clients' needs. The $23 per month for the Standard plan seems steep, but it might be justifiable if it saves time and reduces manual log reviews. My maximum acceptable price would be around $15 per month, as anything higher would strain my budget given that I manage multiple servers. I'd need to see a cost-benefit analysis before committing.

Simulated interest: 50/100

Opalina Abbottneutral

This looks very promising, especially the 'mail stays on your server' and 'no MX record change' features. My current approach involves a mix of free filters, custom Python scripts, and manual intervention for both inbound spam and outbound abuse. It's time-consuming. What concerns me is the "unlimited hosting accounts" plan at $23 per month. With only six people at my startup, managing this across potentially hundreds or thousands of customer accounts on a server feels like a big leap. I need to understand the per-server cost better. If it scales linearly with accounts, that’s one thing, but if it’s a flat fee per server regardless of account count, that’s a significant investment for us right now. I’d be willing to pay $7 per month for a pilot on one server to evaluate its efficacy against our current methods.

Simulated interest: 60/100