Topic: RuggedInbox.com - Free offshore email - page 4. (Read 45068 times)
Is anyone else unable to send or receive messages? I have tried multiple times to send emails with people not getting them. I have had people resend emails and I still never get them. Any help?
anyone who knows these guys from ruggedinbox, can you please tell them the service is not working properly!?
guys, i can't neither receive nor send any mail.
its been like a week already and it's sad
it even does not send from ruggedinbox to ruggedinbox.
please fix this!
its been like a week already and it's sad
it even does not send from ruggedinbox to ruggedinbox.
please fix this!
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.
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 '[email protected]': Connecting to POP3 server: mail.ruggedinbox.com...
[19:44:20] POP3< +OK Welcome to ruggedinbox.com
[19:44:20] POP3> USER [email protected]
[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 '[email protected]': 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
Hi, are you perhaps using Tails ?
If yes, RIB is known to _not_ work with claws-mail on Tails, but icedove/thunderbird + torbirdy works ok.
We are in the process of writing a step-by-step howto on configuring thunderbird on Tails ..
TY
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.
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 '[email protected]': Connecting to POP3 server: mail.ruggedinbox.com...
[19:44:20] POP3< +OK Welcome to ruggedinbox.com
[19:44:20] POP3> USER [email protected]
[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 '[email protected]': 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
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!
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.
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!
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
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.
*********************************************************************************************
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)
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.
*********************************************************************************************
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.
*********************************************************************************************
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.
body of incoming email. Its easy to find IP in MSN, Yahoo, Google emails. But how to find the same in Ruggedinbox?
Thanks.
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
Hello everyone. Yes, it's a nice free offshore email. Does anybody know how to check IP address for incoming emails. Need help. Thanks.
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.
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.
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 '[email protected]': 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!
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 '[email protected]': 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!
I still have problems. However, I decided to try a test and it went through. all is good. Sorry I posted this issue.
This week, we have noticed that we are not able to send email.
Here is the log:
* Account '[email protected]': 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 '[email protected]': Connecting to POP3 server: ruggedinbox.com...
[03:01:44] POP3< +OK Welcome to ruggedinbox.com
[03:01:44] POP3> USER [email protected]
[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.
Here is the log:
* Account '[email protected]': 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 '[email protected]': Connecting to POP3 server: ruggedinbox.com...
[03:01:44] POP3< +OK Welcome to ruggedinbox.com
[03:01:44] POP3> USER [email protected]
[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??
This week, we have noticed that we are not able to send email.
Here is the log:
* Account '[email protected]': 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 '[email protected]': Connecting to POP3 server: ruggedinbox.com...
[03:01:44] POP3< +OK Welcome to ruggedinbox.com
[03:01:44] POP3> USER [email protected]
[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.
Here is the log:
* Account '[email protected]': 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 '[email protected]': Connecting to POP3 server: ruggedinbox.com...
[03:01:44] POP3< +OK Welcome to ruggedinbox.com
[03:01:44] POP3> USER [email protected]
[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 ?
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!
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 !!!
This week, we have noticed that we are not able to send email.
Here is the log:
* Account '[email protected]': 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 '[email protected]': Connecting to POP3 server: ruggedinbox.com...
[03:01:44] POP3< +OK Welcome to ruggedinbox.com
[03:01:44] POP3> USER [email protected]
[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.
Here is the log:
* Account '[email protected]': 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 '[email protected]': Connecting to POP3 server: ruggedinbox.com...
[03:01:44] POP3< +OK Welcome to ruggedinbox.com
[03:01:44] POP3> USER [email protected]
[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 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
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
Jump to: