RuggedInbox.com - Free offshore email

[ruggedinbox.com]

I've got a problem with receiving mails in thunderbird. It asks every time to confirm an exception for ruggedinbox. I import the certificate and get the warning again. This warning shouldn't show up from importing the correct certificate and even after accepting the exceoptin it pop-up again and again. So I can't receive any mails within thunderbird.
Are there any suggestion?

Hi, that's because the valid SSL certificate is installed only on the web server (webmail).
POP/IMAP and SMTP are still using the self-signed certificate, that's because we decided not to trust CAs (and for the webmails we suggest using the onion address http://s4bysmmsnraf7eut.onion/rc).
We are not thunderbird users but didn't receive any complaints, anyway, would you consider using claws-mail ?

I would like to pick up on this and suggest (gently!!) that I, as a grateful user, do have a problem with the lack of a non-self-signed SSL certificate for IMAP.

I use Postbox, The Bat! (on Windows) and K-9 (on Android). I don't really want to use Claws Mail.

Postbox and The Bat! point-blank refuse to connect without a certificate. I have tried more than once.

K-9 accepts the lack of a certificate at first, but then kick it out and will not connect.

This is such a good email service! Could you (please!) re-consider your stance on certification, so that users of email clients other than Claws can access emails by IMAP or POP?

Thanks!

Hi, we are getting a lot of requests on that, we'll change the configuration on the server as soon as possible in order to use the valid certificate even on pop/imap/smtp.

Thanks for the feedback!

[ruggedinbox.com]

Hi ok we brought and installed a proper ssl certificate for smtp/pop/imap on the domain mail.ruggedinbox.com (which is the MX record)
and did some tests on thunderbird/icedove + torbirdy in order to check for exceptions.

Since we were there, we did some packet sniffing and it doesn't appear to leak.

On Debian Wheezy this is the install procedure:

on terminal, as root, type:
apt-get install icedove tor
(icedove is the debian name for thunderbird)

open a browser (perhaps TBB) and download the torbirdy add-on: https://addons.mozilla.org/en-us/thunderbird/addon/torbirdy/

open icedove, go to preferences -> press on the 'switches' button on top right, near the 'Search all add-ons' search box -> 'Install Add-on From File ...'
and select the 'torbirdy-0.1.X-tb.xpi' file you downloaded before.

Close and reopen icedove.

On bottom right you should read the following, in green: TorBirdy Enabled: Tor

Now you can input / create a new mail account.
Insert your username and password.
We tested POP.
Since torbirdy is installed, the wizard is disabled .. you'll need to change some settings manually:

go to preferences -> Account Settings

* Server Settings:
Server Name: mail.ruggedinbox.com
Port: 995
User Name: xxx@ruggedinbox.com
Connection security: SSL/TLS
Authentication method: Normal password

* Outgoing Server (SMTP) -> Edit
Server Name: mail.ruggedinbox.com
Port: 465
Connection security: SSL/TLS
Authentication method: Normal password
User Name: xxx@ruggedinbox.com

Now you should be able to send and receive, all traffic will be routed thru Tor and you'll never get the ssl certificate exception.

The new ssl configuration applies also to other clients, with or without Tor they should validate ruggedinbox.com and/or mail.ruggedinbox.com

[BurungHantu]

Thanks for your good work, we've added your email service to our list: https://www.privacytools.io/#email

Everyone, please feel free to participate in our community project.

[ruggedinbox.com]

Thanks for your good work, we've added your email service to our list: https://www.privacytools.io/#email

Everyone, please feel free to participate in our community project.

Hi! Thanks for including RIB and thanks for your efforts, very nice project!

By coincidence, we were going to contact you right now when we saw this post
We'd like to add a 'warrant canary' on RIB's home page, that's a very clever idea.
We'll contact you now ..

[ruggedinbox.com]

Hi so a user asked us if we could install this plugin: https://squirrelmail.org/plugin_view.php?id=153
but as you can see, it is broken: http://squirrelmail.5843.n7.nabble.com/G-PGP-Encryption-plugin-td9828.html
and here: http://squirrelmail.5843.n7.nabble.com/G-PGP-plugin-td21818.html

That said, the SquirrelMail project has some bounties: https://squirrelmail.org/donations.php#smbounty
where you can read "Update GPG plugin .. Proposed bounty: $2000"
so we pressed 'Purchase' and were contacted by Paul Lesniewski of the SquirrelMail team http://squirrelmail.org/donate_paul_lesniewski.php
which confirmed that the project accepts bitcoins.

The plugin would provide correct Content-Type header (multipart/encrypted) so email client processes the message properly without hassle for recipient
and also search public keys on keyservers and encrypt the messages.

So here we are trying to fundraise the requested amount, 8.412371 BTC ( calculated with https://www.coindesk.com/calculator ) giving as a deadline 30 days from today: 26th June 2015.

We don't know any trusted/privacy oriented fundraising platform (never used one), so we just setup a dedicated BTC address: 1AH1mMYQvoHUUK55UY8hdguBbJNK6LrARm
and if the amount is not reached, we'll send back the funds to the sender addresses.

Now send some coins and make this happen!


Thanks,
RIB team

[Somedday]

This week, we have noticed that we are not able to send email.
Here is the log:


* Account 'xxxxxxx@ruggedinbox.com': Connecting to SMTP server: ruggedinbox.com ...
[02:57:22] SMTP< 220 csds.local ESMTP
[02:57:22] ESMTP> EHLO localhost
[02:57:22] ESMTP< 250-csds.local
[02:57:22] ESMTP< 250-8BITMIME
[02:57:22] ESMTP< 250-AUTH PLAIN LOGIN
[02:57:22] ESMTP< 250-XCLIENT NAME HELO
[02:57:22] ESMTP< 250-XFORWARD NAME ADDR PROTO HELO
[02:57:22] ESMTP< 250-ENHANCEDSTATUSCODES
[02:57:22] ESMTP< 250
[02:57:22] ESMTP> STARTTLS
[02:57:22] ESMTP< 500 5.5.1 Error: unknown command
** error occurred on SMTP session
*** Error occurred while sending the message:
500 5.5.1 Error: unknown command
* Account 'xxxxxxx@ruggedinbox.com': Connecting to POP3 server: ruggedinbox.com...
[03:01:44] POP3< +OK Welcome to ruggedinbox.com
[03:01:44] POP3> USER xxxxxxx@ruggedinbox.com
[03:01:44] POP3< +OK
[03:01:44] POP3> PASS ********
[03:01:45] POP3< +OK Logged in.
[03:01:45] POP3> STAT
[03:01:45] POP3< +OK 0 0
[03:01:45] POP3> QUIT
[03:01:46] POP3< +OK Logging out.

Thank you in advance, for your help.

[khawaja07]

Hello everyone, fresh new service: https://ruggedinbox.com
Still in BETA, currently completely free and ad-free, Tor friendly, offshore (Europe, Bulgaria), no personal details needed, no question asked, session expiration friendly (10 hours), limited number of accounts available.

If you prefer a self-signed ssl certificate, here you are: https://ruggedinbox.com:444

Also available as a Tor hidden service: s4bysmmsnraf7eut.onion

Feedback is welcome!

nice service man!!
to be anonymous...
thumbs up !!!

[ruggedinbox.com]

This week, we have noticed that we are not able to send email.
Here is the log:


* Account 'xxxxxxx@ruggedinbox.com': Connecting to SMTP server: ruggedinbox.com ...
[02:57:22] SMTP< 220 csds.local ESMTP
[02:57:22] ESMTP> EHLO localhost
[02:57:22] ESMTP< 250-csds.local
[02:57:22] ESMTP< 250-8BITMIME
[02:57:22] ESMTP< 250-AUTH PLAIN LOGIN
[02:57:22] ESMTP< 250-XCLIENT NAME HELO
[02:57:22] ESMTP< 250-XFORWARD NAME ADDR PROTO HELO
[02:57:22] ESMTP< 250-ENHANCEDSTATUSCODES
[02:57:22] ESMTP< 250
[02:57:22] ESMTP> STARTTLS
[02:57:22] ESMTP< 500 5.5.1 Error: unknown command
** error occurred on SMTP session
*** Error occurred while sending the message:
500 5.5.1 Error: unknown command
* Account 'xxxxxxx@ruggedinbox.com': Connecting to POP3 server: ruggedinbox.com...
[03:01:44] POP3< +OK Welcome to ruggedinbox.com
[03:01:44] POP3> USER xxxxxxx@ruggedinbox.com
[03:01:44] POP3< +OK
[03:01:44] POP3> PASS ********
[03:01:45] POP3< +OK Logged in.
[03:01:45] POP3> STAT
[03:01:45] POP3< +OK 0 0
[03:01:45] POP3> QUIT
[03:01:46] POP3< +OK Logging out.

Thank you in advance, for your help.

Hi, all working fine here. Do you still have the issue ?

[khawaja07]

This week, we have noticed that we are not able to send email.
Here is the log:


* Account 'xxxxxxx@ruggedinbox.com': Connecting to SMTP server: ruggedinbox.com ...
[02:57:22] SMTP< 220 csds.local ESMTP
[02:57:22] ESMTP> EHLO localhost
[02:57:22] ESMTP< 250-csds.local
[02:57:22] ESMTP< 250-8BITMIME
[02:57:22] ESMTP< 250-AUTH PLAIN LOGIN
[02:57:22] ESMTP< 250-XCLIENT NAME HELO
[02:57:22] ESMTP< 250-XFORWARD NAME ADDR PROTO HELO
[02:57:22] ESMTP< 250-ENHANCEDSTATUSCODES
[02:57:22] ESMTP< 250
[02:57:22] ESMTP> STARTTLS
[02:57:22] ESMTP< 500 5.5.1 Error: unknown command
** error occurred on SMTP session
*** Error occurred while sending the message:
500 5.5.1 Error: unknown command
* Account 'xxxxxxx@ruggedinbox.com': Connecting to POP3 server: ruggedinbox.com...
[03:01:44] POP3< +OK Welcome to ruggedinbox.com
[03:01:44] POP3> USER xxxxxxx@ruggedinbox.com
[03:01:44] POP3< +OK
[03:01:44] POP3> PASS ********
[03:01:45] POP3< +OK Logged in.
[03:01:45] POP3> STAT
[03:01:45] POP3< +OK 0 0
[03:01:45] POP3> QUIT
[03:01:46] POP3< +OK Logging out.

Thank you in advance, for your help.

Hi, all working fine here. Do you still have the issue ?

no its just working fine like a charm for me..
one question i wanna ask..will ever our real location will be trapped ??
in any case??

[Somedday]

I still have problems.  However, I decided to try a test and it went through.  all is good.  Sorry I posted this issue.

[Somedday]

Well, that didn't work.   
I was able to send, and then I cannot send.  I tried many times today but, I get the following error:

POP3< +OK 0 0
POP3> QUIT
POP3< +OK Logging out.
* Account 'xxxxxxx@ruggedinbox.com': Connecting to SMTP server: ruggedinbox.com ...
SMTP< 220 csds.local ESMTP
ESMTP> EHLO localhost
ESMTP< 250-csds.local
ESMTP< 250-8BITMIME
ESMTP< 250-AUTH PLAIN LOGIN
ESMTP< 250-XCLIENT NAME HELO
ESMTP< 250-XFORWARD NAME ADDR PROTO HELO
ESMTP< 250-ENHANCEDSTATUSCODES
ESMTP< 250
ESMTP> STARTTLS
ESMTP< 500 5.5.1 Error: unknown command
** error occurred on SMTP session
*** Error occurred while sending the message:
500 5.5.1 Error: unknown command

I do not remember making any changes on my end, it just stopped sending.  I can receive without any trouble.
I see the error comes after STARTTLS.  What can I do to check my setting?  Here are the Send settings in Claws:

send:
generated message-id: yes
send account mail address in Message-ID: no
generate x-mailer header: no

SMTP authentication (SMTP AUTH): yes
Authentication method: Automatic
User ID: empty
Password: empty
Authenticate with POP3 before sending: no

SSL:
POP3:
Use SSL for POP3 connection

Send (SMTP):
Use STARTTLS command to start SSL session

Use non-blocking SSL: yes

Advanced:
SMTP port: no
POP3 port: no
Domain name: no
(everything is unchecked)

If you can think of anything that I can check, I would appreciate it!
Thank you!

[Somedday]

Update:
Ok, after failures all day, the email finally went through in the evening.  I have no clue as to why.
So, I hardly know how to approach this erratic problem.  I do not know what to look for being that it is erratic like this.
Scratching my head.

Update 06/08/2015:
I have not been able to send.  The error in the post above means that there is something wrong with my Claws settings?  It comes after "STARTTLS".  Any idea what I can look for in my own settings?  Claws is able to connect to serve and download all incoming email.  I am only having a problem with sending.

Thanks in advance!


Update #2 06/08/2015:

I decided to check my router settings.  As I went through the security settings, I remembered checking the "Anti-Hacking" checkbox a few weeks ago.  I removed the checkbox and the email sent.  I caused my own problem.  Doing too many things at once, otherwise I would have remembered the change I made immediately.

I really, really like Claws, and Ruggedinbox. 

[zorro888]

Hello everyone. Yes, it's a nice free offshore email. Does anybody know how to check IP address for incoming emails. Need help. Thanks.

[tarsua]

Hello everyone. Yes, it's a nice free offshore email. Does anybody know how to check IP address for incoming emails. Need help. Thanks.

You can try this http://whatismyipaddress.com/trace-email but im not sure it will work with ruggedinbox

[zorro888]

Thanks for your reply. Actually I use this site http://whatismyipaddress.com/trace-email every day. My point is to find the IP address of the sender in the
body of incoming email. Its easy to find IP in MSN, Yahoo, Google emails. But how to find the same in Ruggedinbox?
Thanks.

[NonSenseXwN6iHjm9mlk]

FBI message OUTDATED, Not replying here will make us assume things....
Today is  :   July 26, 2015, 08:51:14 PM   , while i am writing here .

The content of the file https://ruggedinbox.com/canary.txt was that moment :


*********************************************************************************************
We do not know about any seizures, warrants or searches of the following
servers:

 - ALL public servers
 - ALL hidden servers

We do not know about any seizures, warrants or searches of staff hardware.
We never placed any backdoors in our servers or network and never received any requests to do so.

Today is 2015-07-16

We can't guarantee no secret searches have been performed.
We can't guarantee the private key wasn't secretly compromised.
We can't guarantee the staff won't give in to force.

Be extremely careful if this file disappears or is outdated.

Public Key: https://ruggedinbox.com/rib.pub.txt (or http://s4bysmmsnraf7eut.onion/rib.pub.txt)

This message expires in 14 days.

*********************************************************************************************

[ruggedinbox.com]

FBI message OUTDATED, Not replying here will make us assume things....
Today is  :   July 26, 2015, 08:51:14 PM   , while i am writing here .

The content of the file https://ruggedinbox.com/canary.txt was that moment :


*********************************************************************************************
We do not know about any seizures, warrants or searches of the following
servers:

 - ALL public servers
 - ALL hidden servers

We do not know about any seizures, warrants or searches of staff hardware.
We never placed any backdoors in our servers or network and never received any requests to do so.

Today is 2015-07-16

We can't guarantee no secret searches have been performed.
We can't guarantee the private key wasn't secretly compromised.
We can't guarantee the staff won't give in to force.

Be extremely careful if this file disappears or is outdated.

Public Key: https://ruggedinbox.com/rib.pub.txt (or http://s4bysmmsnraf7eut.onion/rib.pub.txt)

This message expires in 14 days.

*********************************************************************************************

Check again your math
(we updated the canary exactly on the 'expiration' day, first rule: don't panic)

[djdjdj]

Hello everyone, fresh new service: https://ruggedinbox.com
Still in BETA, currently completely free and ad-free, Tor friendly, offshore (Europe, Bulgaria), no personal details needed, no question asked, session expiration friendly (10 hours), limited number of accounts available.

If you prefer a self-signed ssl certificate, here you are: https://ruggedinbox.com:444

Also available as a Tor hidden service: s4bysmmsnraf7eut.onion

Feedback is welcome!

SENT an email to support team a few hrs ago. I actuallly forgot my password andis there i way i can reset it. Plus i can answer verification questions so as to help me reset it.
Expecting to her from ya

[ruggedinbox.com]

Hello everyone, fresh new service: https://ruggedinbox.com
Still in BETA, currently completely free and ad-free, Tor friendly, offshore (Europe, Bulgaria), no personal details needed, no question asked, session expiration friendly (10 hours), limited number of accounts available.

If you prefer a self-signed ssl certificate, here you are: https://ruggedinbox.com:444

Also available as a Tor hidden service: s4bysmmsnraf7eut.onion

Feedback is welcome!

SENT an email to support team a few hrs ago. I actuallly forgot my password andis there i way i can reset it. Plus i can answer verification questions so as to help me reset it.
Expecting to her from ya

Answered, sry can't do.

[sah1376]

Hi,
Running claws mail and having issues setting up ruggedinbox account.
Can receive OK but get error on send.
Have followed instructions for settings in this thread.
Compared my accountrc file to the example given too but not seeing my problem.
Any help greatfuly received.

Code:

send:
generated message-id: yes
send account mail address in Message-ID: no
generate x-mailer header: no

SMTP authentication (SMTP AUTH): yes
Authentication method: Automatic
User ID: empty
Password: empty
Authenticate with POP3 before sending: no

SSL:
POP3: 
Use SSL for POP3 connection

Send (SMTP):
Use STARTTLS command to start SSL session

Use non-blocking SSL: yes

Advanced:
SMTP port: no
POP3 port: no
Domain name: no

Code:

* Account 'XXXXX@ruggedinbox.com': Connecting to POP3 server: mail.ruggedinbox.com...
[19:44:20] POP3< +OK Welcome to ruggedinbox.com
[19:44:20] POP3> USER XXXXX@ruggedinbox.com
[19:44:21] POP3< +OK
[19:44:21] POP3> PASS ********
[19:44:21] POP3< +OK Logged in.
[19:44:21] POP3> STAT
[19:44:21] POP3< +OK 2 1969
[19:44:21] POP3> UIDL
[19:44:22] POP3< +OK
[19:44:22] POP3> LIST
[19:44:22] POP3< +OK 2 messages:
[19:44:22] POP3> QUIT
[19:44:22] POP3< +OK Logging out.
* Account 'XXXXXX@ruggedinbox.com': Connecting to SMTP server: mail.ruggedinbox.com ...
[19:44:52] SMTP< 220 csds.local ESMTP
[19:44:52] ESMTP> EHLO localhost
[19:44:52] ESMTP< 250-csds.local
[19:44:52] ESMTP< 250-8BITMIME
[19:44:52] ESMTP< 250-AUTH PLAIN LOGIN
[19:44:52] ESMTP< 250-XCLIENT NAME HELO
[19:44:52] ESMTP< 250-XFORWARD NAME ADDR PROTO HELO
[19:44:52] ESMTP< 250-ENHANCEDSTATUSCODES
[19:44:52] ESMTP< 250 
[19:44:52] ESMTP> STARTTLS
[19:44:52] ESMTP< 500 5.5.1 Error: unknown command
** error occurred on SMTP session
*** Error occurred while sending the message:
500 5.5.1 Error: unknown command