Page 1 of 1

Nerdshack

Posted: Sun Nov 04, 2007 1:52 am
by war1
Nerdshack has changed its name to Lavabit. It has always been a reliable POP3 service. Now it has added IMAP. Server name is lavabit.com for POP3, IMAP, and SMTP.

IMAP is available in regular and SSL mode. Server ports are 143 and 993 respectively. There is no IDLE as yet.

Lavabit has only one folder on server, Inbox. It does not have webmail, but is working on an webmail interface.

http://lavabit.com/

Posted: Mon Nov 05, 2007 10:01 am
by JRF
Thanks war1 , for the good news .

The Lavabit site is very comprehensive , they offer a lot features , up to 1GB storage free account , and very decent limitations .

You may even have all your data strongly encrypted in their servers (available for custom plans , from $8/year , probably US$) .

Retrieving and sending in PP runs fine (using Imap+SSL and SMTP+SSL+authentication) .

The IMAP protocol is announced there , but was not incorporated to the documentation .

Unfortunately there is no mention in their site to the development of IDLE .
------------------------------------
But I have a question regarding the SMTP operation : for security reasons I never use the To: field , all the destinations I place in BCC: .

Using Lavabit-SMTP (in PP) , the emails I sent have used the BCC: destinations as I have written them in the To: field , meaning that when the msgs are received , all receiver addresses are shown .

I rather think this is a Lavabit problem than a PP sending issue , anyway , comments from other users are welcome .

Posted: Mon Nov 05, 2007 10:05 am
by war1
JRF, I have not tested the BCC field suing PP and Lavabit. So I do not know where the error lies.

Posted: Mon Nov 05, 2007 6:10 pm
by Jeff
Just tested it myself and it does seem strange. I also tried putting in a different 'to' address, and in that case, the BCC does not get shown. So if "to" is empty, it shows the entire BCC in the "to" field; and if there's a "to" and a "bcc", then the "bcc" will not get shown. This is specific to lavabit.

This may not affect all email clients, as some email clients may substitute an empty "to" field with "undisclosed recipients" or something similar. But I wouldn't call what lavabit is doing as desirable. But then, I'm not sure how desirable BCC-only emails are either ;)