RuggedInbox.com - Free offshore email

[ruggedinbox.com]

Follow up:

we contacted our server farm and after short time they enabled their anti-DDOS filter.

Now our services are up and running!

[1714059782]

1714059782

[1714059782]

1714059782

[1714059782]

1714059782

[1714059782]

1714059782

[Phonon]

thanks for your answer.

i dot not have error 500 anymore, however i can't login onto the webmail.....and this is the only way for me to watch my messages...
hope it should be operational very soon.
thx @ll

Hi, strange we didn't touch the system and we are able to login as usual.
Is this still happening to you ?

Thanks for your feedback!

I have the same error (sm and rc) and this is still happening for me too.

[ruggedinbox.com]

thanks for your answer.

i dot not have error 500 anymore, however i can't login onto the webmail.....and this is the only way for me to watch my messages...
hope it should be operational very soon.
thx @ll

Hi, strange we didn't touch the system and we are able to login as usual.
Is this still happening to you ?

Thanks for your feedback!

I have the same error (sm and rc) and this is still happening for me too.

Argh! Found the issue: when updating roundcube, from version 1.0.2 to 1.0.3, you use a tool that does the job.
But ... the tool failed to keep some setting, including the one that appends the domain (@ruggedinbox.com) to the username.

So .. logging with with just 'username' was resulting in a 'login failed' error,
while trying with 'username@ruggedinbox.com' was working ok.

Now this is fixed, we'll pay more attention in future when we update roundcube
and we'll asap open a discussion on the roundcube mailing list about that.

Thanks to all for your feedback!

[Phonon]

I have another problem with squirrel mail. Login works, but I only get a blank screen with a border left side and nothing more happens

Thanks a lot for the fast support.

[ruggedinbox.com]

I have another problem with squirrel mail. Login works, but I only get a blank screen with a border left side and nothing more happens

Thanks a lot for the fast support.

Hi, tried now with both username@ruggedinbox.com and just 'username',
login, mail sending and receiving works ok.
GUI looks in shape.

Are you still having the issue ?

[Phonon]

still..

http://abload.de/thumb/squirrelmail8rplh.png

With Win7 + Firefox 33 and also Debian sid + Chromium.

Roundcube works, but not perfect. I can open a specific mail and delete it, but the preview (bottom window) won't load nor mass selection and delete of mails. Roundcube tries to load the mail in the preview window but didn't finish. Open the mail with doubleclick works like a charm.

Edit: Option menu in roundcube also won't load. Same effect.

[ruggedinbox.com]

still..

With Win7 + Firefox 33 and also Debian sid + Chromium.

Roundcube works, but not perfect. I can open a specific mail and delete it, but the preview (bottom window) won't load nor mass selection and delete of mails. Roundcube tries to load the mail in the preview window but didn't finish. Open the mail with doubleclick works like a charm.

Edit: Option menu in roundcube also won't load. Same effect.

Mmm what if you use Tor browser bundle to access the onion address ?
http://s4bysmmsnraf7eut.onion/rc
http://s4bysmmsnraf7eut.onion/sm

perhaps we are still under the DDOS of that poor soul

Maybe the 'clearnet traffic' is breaking, while the onion tunnel goes smooth under the attack and the data center filters ..

Thank you very much for your feedback!

[Phonon]

works smooth within tor.

seems odd, but is okay 

[ruggedinbox.com]

works smooth within tor.

seems odd, but is okay 

Good
Is unfortunate but we are not able to tell if the DDOS attack is still going on.
Maybe not, or maybe the server farm is filtering the traffic.
The server traffic is in the norm, logs are ok, number of sockets in the norm, cpu ok, ram low as usual.
Hey DD4BC Team, are you still attacking us ?

[maiste]

"ALSO .. we changed the log rotation policy.
Before it was the Debian default: 1 month.
1 month is too much, we don't need it and privacy-wise, the less the better.
The new policy is 1 week: system logs and web access logs are kept for 1 week.
(this can still be improved, in the near future it will be 48 hours)"

O.K. Guys you keep talking about anonymity, privacy and all those cool thing.

1. When you keep logs there is no anonymity.

2.
"ALSO .. we changed the log rotation policy.
Before it was the Debian default: 1 month.
1 month is too much, we don't need it and privacy-wise, the less the better.
The new policy is 1 week: system logs and web access logs are kept for 1 week.
(this can still be improved, in the near future it will be 48 hours)"

- "this can still be improved..."  Your statement looks like you were sitting at the round table with the system negotiating for how long it should keep the logs if any. You keep logs or you don't! The user is unknown or he isn't.

[ruggedinbox.com]

"ALSO .. we changed the log rotation policy.
Before it was the Debian default: 1 month.
1 month is too much, we don't need it and privacy-wise, the less the better.
The new policy is 1 week: system logs and web access logs are kept for 1 week.
(this can still be improved, in the near future it will be 48 hours)"

O.K. Guys you keep talking about anonymity, privacy and all those cool thing.

1. When you keep logs there is no anonymity.

2.
"ALSO .. we changed the log rotation policy.
Before it was the Debian default: 1 month.
1 month is too much, we don't need it and privacy-wise, the less the better.
The new policy is 1 week: system logs and web access logs are kept for 1 week.
(this can still be improved, in the near future it will be 48 hours)"

- "this can still be improved..."  Your statement looks like you were sitting at the round table with the system negotiating for how long it should keep the logs if any. You keep logs or you don't! The user is unknown or he isn't.

Hi maiste, sorry we'll be very direct about your comments and (lack of) concrete suggestion / solution:
you have no idea what you are talking about
No offense but in short, disabling all logs wouldn't improve users privacy of an inch
and (just as a first example) fail2ban wouldn't work at all.
Fail2ban protects the service against floods and brute force cracking attempts of ssh, smtp, pop, imap, http, ...

Anyway thanks for your interest!

[maiste]

I'm far from getting upset if you beat me with a reasonable reply (which you did).
I'm going to give your service a try.

Salute!

[ruggedinbox.com]

I'm far from getting upset if you beat me with a reasonable reply (which you did).
I'm going to give your service a try.

Salute!

Hi welcome abroad!
Yes sorry for the short and cheap answer, the topic (privacy) is so large that you don't know where to start.
About the logs, consider that if an attacker gains access to the server (by exploit, physical access or vps supervisor), even with no logs,
he would be able to read/copy the emails, get the list of the accounts
and perhaps install a sniffer, which gives much more info than the logs.

The key for your privacy is yourself, use Tor browser bundle and use end-to-end encryption (PGP), use Tails, claws-mail + torsocks if you prefer a mail agent (you can find it in Tails), use https://temp.pm, don't trust us!

Feedback is welcome

[Blis]

Receiving error 500 today and cannot connect. Just a FYI to notify you of the problem.

Thank you for the service.

[zinjo]

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!

down? why??

[ruggedinbox.com]

Hi thanks for the feedback. Strange problem, not sure about the reason, contacting the datacenter ..

[ruggedinbox.com]

Hi, it looks like a DDOS attack (from Tor) to squirrelmail was preventing the other web services to work (web site and roundcube webmail).
We have currently disabled squirrelmail.
We are working on this.
Services are now up.

Thanks for the feedback!

[ruggedinbox.com]

Hi ok we restored squirrelmail ( https://ruggedinbox.com/sm or http://s4bysmmsnraf7eut.onion/sm )

[zinjo]

tnx, have been waiting deem 24 hours

[Blis]

It seems to be slow and unresponsive again at this time. DDOS attack back?

If so you would think people would have enough dignity and respect not to screw with peoples communication with their families on Christmas eve. /rant