<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
    xmlns:content="http://purl.org/rss/1.0/modules/content/"
    xmlns:dc="http://purl.org/dc/elements/1.1/"
    xmlns:atom="http://www.w3.org/2005/Atom">
    <channel>
        <title>spam — LowEndSpirit</title>
        <link>https://staging.lowendspirit.com/index.php?p=/</link>
        <pubDate>Thu, 09 Apr 2026 17:19:24 +0000</pubDate>
        <language>en</language>
            <description>spam — LowEndSpirit</description>
    <atom:link href="https://staging.lowendspirit.com/index.php?p=/discussions/tagged/spam/feed.rss" rel="self" type="application/rss+xml"/>
    <item>
        <title>Security Breached. what do i need to do?</title>
        <link>https://staging.lowendspirit.com/index.php?p=/discussion/5948/security-breached-what-do-i-need-to-do</link>
        <pubDate>Mon, 22 May 2023 10:09:02 +0000</pubDate>
        <category>Help</category>
        <dc:creator>milkboy</dc:creator>
        <guid isPermaLink="false">5948@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>So one of my Hosting DA panel got hack. <br />
My 30++ years old "i-got-hacked" cherry has been popped.  <img src="https://staging.lowendspirit.com/plugins/emojiextender/emoji/twitter/blush.png" title=":3" alt=":3" height="18" /> <br />
It is only sending Spam emails on a few accounts.<br />
All of the password are &gt;20-key generated.</p>

<p>As this is my first, I'm unsure nature of the breach and what i need to do.<br />
I have check a few sites (i.e haveibeenpwn) for breaches, but found none</p>

<p>As a precaution i have:</p>

<ul>
<li>Suspended the DA user account and server for a day. (i control both user and reseller account)</li>
<li>Change all user password in the domain.</li>
<li>Change SSL (after i unsuspend later)</li>
<li>Notify the provider of the breach</li>
</ul>

<p>So do i need to do anything else?<br />
How do i know if its a simple password breach or much worse?</p>

<p>EDIT:<br />
changed the title to reflect nature of the breach<br />
Found the offending pc. office user brought their laptop to a 3rd party services during the weekend.<br />
so far seems to be a spambot, scanned all the other check the entire office pc seems good.<br />
wasted entire day  <img src="https://staging.lowendspirit.com/plugins/emojiextender/emoji/twitter/cry.png" title=":'(" alt=":'(" height="18" /></p>
]]>
        </description>
    </item>
    <item>
        <title>Heimdall: An open-source personal email guardian</title>
        <link>https://staging.lowendspirit.com/index.php?p=/discussion/700/heimdall-an-open-source-personal-email-guardian</link>
        <pubDate>Thu, 27 Feb 2020 18:25:45 +0000</pubDate>
        <category>Technical</category>
        <dc:creator>Voss</dc:creator>
        <guid isPermaLink="false">700@/index.php?p=/discussions</guid>
        <description><![CDATA[<p>I came across this piece of OSS that could be useful for some of you: <a rel="nofollow" href="https://medium.com/swlh/how-i-built-heimdall-an-open-source-personal-email-guardian-68e306d172d1" title="[link 1]">[Link]</a> / <a rel="nofollow" href="https://github.com/fterh/heimdall" title="[Github]">[Github]</a></p>

<p>In broad strokes, here's a summary of what Heimdall does:</p>

<ul>
<li>Heimdall is a self-hosted email alias/forwarding service</li>
<li>It's a self-hosted and self-managed service, you have complete control over your data</li>
</ul>

<p>It allows you to:<br />
1. Receive safely: Receive emails on single-use aliases and forward them to your personal inbox.<br />
2. Reply anonymously: Reply to emails from your alias without revealing your personal email address.<br />
3. Attachments: Attachments are supported on incoming and outgoing emails (subject to size limits - see below).<br />
4. Email commands: Manage your aliases through email directly - no separate app or website required.<br />
5. Usage stats: Easily check the usage stats of each alias.</p>

<p>Disclaimer: I have nothing to do with this project. I read the article and wanted to know what you think of it.</p>
]]>
        </description>
    </item>
   </channel>
</rss>
