<div dir="ltr"><div><div><br><br>I haven't put a LOT of time into it yet, it was just one of those 'putter about' projects. My first thought was to have a mail server just so I could get a little more insight into it's setup. Of course, it didn't end there...<br><br></div>Using postfix and dovecot I got a simple server up and running quite quickly, of course did not allow mail relaying... TLS certs were next. Certs have always been annoying for me, I don't use them enough to <i>really</i> get into it, but after a little bit of reading I managed to get it working.<br><br></div><div>Spam Assassin <i>was</i> next, but I got sidetracked for a bit with Owncloud and RoundCube.<br><br></div><div>Owncloud is a personal 'cloud', kinda neat, somewhat pointless on a system with 5Gb of disk space. :D Roundcube is webmail for postfix type mail servers. Basically, if you have a shell account, you have a roundcube account... It's rather nice!<br><br></div><div>Next... Spam assass--- er, nope. Another sidetrack: Getting my mail account (and calendar from Owncloud) onto my BlackBerry.<br><br></div><div>Now, with the Christmas season in full swing, I've barely touched it. So far no one out there knows the IP / DNS name of the server, so that's what's keeping me safe... Well, as safe as hiding behind the curtains during a home invasion, but still. So far, so good. My plans did end at Spam Assassin, wasn't planning a blacklist, but now I probably will add that to the list.<br><br></div><div>As for the dangers? Well, it's a pointless little VPS that can die a firey death and the domain isn't a permanent one I want to keep. Call it practice, call it fun, call it a cheese sandwich, I don't care... :)<br><br></div><div>DMARC! I remember reading about this a little while ago, but only in the 'rings a bell' sense. Sounds like something to read up on at some point. Thus far, I've not had issues sending / receiving mail from <a href="http://gmail.com">gmail.com</a> or <a href="http://rogers.com">rogers.com</a>.<br><br></div><div>Q. Is it worth it? Will I run into trouble? Will I pull my hair out fighting spam? (Tune in next week...)<br><br>A. I have NO idea yet. I don't learn lessons from watching others fail, I learn lessons from trying and possibly failing in my own, unique way. So until I get buried under a ton of spam messages, I'll keep this project going...<br></div><div><br></div><div><br></div><div><br><br><br></div><div>Next, SPAM ASSASSIN! Promise. :)<br><br></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Dec 19, 2014 at 10:14 AM, Khalid Baheyeldin <span dir="ltr"><<a href="mailto:kb@2bits.com" target="_blank">kb@2bits.com</a>></span> wrote:<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Fri, Dec 19, 2014 at 4:49 AM, B. S. <<a href="mailto:bs27975@yahoo.ca">bs27975@yahoo.ca</a>> wrote:<br>
><br>
</span><span class="">> The idea of running one's own mail server has always seemed a little 'scary' - not just to me, but others here have expressed similar.<br>
><br>
> So many little fiddly bits, DNS stuff [can't recall the term, not DFC - the MX record isn't the problem, it's the rest], multiple programs chained together, blacklists, spamassasin, don't know what all else.<br>
><br>
> Always seemed too much work. Anyone using yahoo these days probably wonders if it's less work than Yahoo has been!<br>
><br>
> Is there a current best practices how to on running one's own e-mail server (IMAP, not POP) out there these days? [Googling it will just bury you.]<br>
<br>
</span>I used to be in this camp (those who avoid running email servers) and<br>
I am still in it somewhat, with some modifications.<br>
<br>
I still don't run any POP servers, or spam filters. I forward the<br>
accounts that are in my domain to a web email (mostly Gmail).<br>
<br>
But, what happened recently is that I modified SMTP so that I am able<br>
to overcome Yahoo (and others, like Cox and Verizon) implementing<br>
DMARC and hence my email bouncing from those domains.<br>
<br>
Basically, what I did was re-implement SPF, added DKIM and a PTR<br>
record. These can be tedious to implement, and test, but once you do<br>
them, things work again, and you don't get bounces anymore.<br>
<br>
The details are here<br>
<br>
<a href="http://baheyeldin.com/technology/linux/setting-up-spf-and-dkim-on-postfix.html" target="_blank">http://baheyeldin.com/technology/linux/setting-up-spf-and-dkim-on-postfix.html</a><br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
Khalid M. Baheyeldin<br>
<a href="http://2bits.com" target="_blank">2bits.com</a>, Inc.<br>
Fast Reliable Drupal<br>
Drupal optimization, development, customization and consulting.<br>
Simplicity is prerequisite for reliability. -- Edsger W.Dijkstra<br>
Simplicity is the ultimate sophistication. -- Leonardo da Vinci<br>
For every complex problem, there is an answer that is clear, simple,<br>
and wrong." -- H.L. Mencken<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
<br>
_______________________________________________<br>
kwlug-disc mailing list<br>
<a href="mailto:kwlug-disc@kwlug.org">kwlug-disc@kwlug.org</a><br>
<a href="http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org" target="_blank">http://kwlug.org/mailman/listinfo/kwlug-disc_kwlug.org</a><br>
</div></div></blockquote></div></div>