Just checked, it's cool now - thanks cthree.

 

Hmm email notification seems to be in-op again.

 

ERROR: IMAP server closed the connection.
Server responded:* BYE Internal login failure. Refer to server log for more information

 

I've been tweaking a few settings, those issues are short lived.

I just completed configuring address extensions. That's why it was acting weird.

Here is how they work and how you use them:

when someone sends mail to foo@s2ki.com the message goes into foo's inbox. However your address can be extended using a + to do a few neat things, for example foo+bar@s2ki.com. If foo has a mail folder named "bar" (case sensitive) then the message will go directly to the bar folder. If you don't it will go to foo's inbox but the To: address will still be foo+bar so you can filter it yourself after delivery if you choose to.

So, let's say you want to organize all of your mail from cnn.com into its own mail folder. Without extensions you would apply a filter to move all mail where From: contains "cnn.com" to a folder named cnn. With extensions you would simply register on cnn.com's website using the email address foo+cnn@s2ki.com and create a mail folder named cnn in either webmail or your IMAP mail client like Outlook Express, Apple Mail, Thunderbird, etc. THIS DOES NOT WORK FOR PEOPLE WHO DOWNLOAD THEIR MAIL WITH POP (Nor do webmail folders; you shouldn't use POP, use IMAP).

There are issues with case sensitive folder names, Apple Mail for example doesn't allow me to send mail to foo+CNN@s2ki.com, it downcases it to foo+cnn@s2ki.com. The extension/folder name is case sensitive so a message to foo+cnn will not find its way into a CNN or CnN or Cnn or cnN folder, it will end up in the general inbox. Special characters including spaces are also a possible issue. I recommend you name your mail folders with lowercase letters and numbers only and use _ or . instead of spaces. It's not required but if you want to use an extended address it will make it easy.

Extensions will form part of the spam mitigation stuff once I get that back in place.

 

I spent the whole day today doing additional work on the mail server. I implemented a number of background things you aren't going to see but I've also implemented very basic SPAM filtering. As I mentioned in the previous post, if you have a mail folder named "spam" in your webmail or IMAP client, mail identified as SPAM will be directed there. If you don't you'll get it in your inbox and can filter it by the "X-Spam-Flag" mail header field. A value of YES means the server thinks it's SPAM, a value of NO means it's no quite SPAM, more SPAMMY. If the header line is missing, it's considered clean.

Have a look at the full headers of your received email to help sort out filtering that works best for you.

 

This morning:

Error connecting to IMAP server: mail.
111 : Connection refused


Erik - Great work on the things you mentioned above. I am excited to put that to use!!

 

Im still getting error messages on my email.
I can log in but I cant send anything.

Email delivery error
Server replied: 1 Can't execute command '/usr/sbin/sendmail.postfix -i -t -frossos2k@s2ki.com'.

 

try sending again. I made a small change to the configuration which was causing issues. It should be ok now.

 

The mail server now supports SSL/TLS for POP, IMAP and SMTP. Please update your account settings in your email client software to use SSL for sending and receiving mail. It's entirely optional but I recommend you use it anyway. This doesn't affect webmail at all, just if you use a mail client like Apple Mail, iPhone, Outlook Express or Thunderbird, etc.

 

Secure SSL access to webmail at https://www.s2ki.com/mail is working correctly.

There is a small bit of SPAM tagging implemented but anything more sophisticated will need to wait for another day. I'm calling member mail complete at this point.