One of Gmail's spam defenses that I bumped into

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
# sendmail -v *@gmail.com
Subject: Hello World!
This is an email to myself.
.
*@gmail.com... Connecting to [127.0.0.1] via relay...
220 transfusion.vm ESMTP Sendmail 8.14.4/8.14.4/Debian-2.1ubuntu4; Mon, 10 Mar 2014 05:57:40 -0400; (No UCE/UBE ) logging access from: localhost(OK)-localhost [127.0.0.1]
>>> EHLO transfusion.vm
250-transfusion.vm Hello localhost [127.0.0.1], pleased to meet you
250-ENHANCEDSTATUSCODES
250-PIPELINING
250-EXPN
250-VERB
250-8BITMIME
250-SIZE
250-DSN
250-ETRN
250-AUTH DIGEST-MD5 CRAM-MD5
250-DELIVERBY
250 HELP
>>> VERB
250 2.0.0 Verbose mode
>>> MAIL From: SIZE=50 AUTH=root@transfusion.vm
250 2.1.0 ... Sender ok
>>> RCPT To:<*@gmail.com>
>>> DATA
250 2.1.5 <*@gmail.com>... Recipient ok
354 Enter mail, end with "." on a line by itself
>>> .
050 <*@gmail.com>... Connecting to gmail-smtp-in.l.google.com. via esmtp...
050 220 mx.google.com ESMTP t3si9104892qar.125 - gsmtp
050 >>> EHLO transfusion.vm
050 250-mx.google.com at your service, [2a01:**:****:***::*]
050 250-SIZE 35882577
050 250-8BITMIME
050 250-STARTTLS
050 250-ENHANCEDSTATUSCODES
050 250 CHUNKING
050 >>> STARTTLS
050 220 2.0.0 Ready to start TLS
050 >>> EHLO transfusion.vm
050 250-mx.google.com at your service, [2a01:**:****:***::*]
050 250-SIZE 35882577
050 250-8BITMIME
050 250-ENHANCEDSTATUSCODES
050 250 CHUNKING
050 >>> MAIL From: SIZE=331
050 250 2.1.0 OK t3si9104892qar.125 - gsmtp
050 >>> RCPT To:<*@gmail.com>
050 250 2.1.5 OK t3si9104892qar.125 - gsmtp
050 >>> DATA
050 354 Go ahead t3si9104892qar.125 - gsmtp
050 >>> .
050 550-5.7.1 [2a01:**:****:***::*] Our system has detected that this message does
050 550-5.7.1 not meet IPv6 sending guidelines regarding PTR records and
050 550-5.7.1 authentication. Please review
050 550-5.7.1 https://support.google.com/mail/?p=ipv6\_authentication\_error for more
050 550 5.7.1 information. t3si9104892qar.125 - gsmtp
050 ... Connecting to local...
050 ... Sent
250 2.0.0 s2A9ve5k026538 Message accepted for delivery
*@gmail.com... Sent (s2A9ve5k026538 Message accepted for delivery)
Closing connection to [127.0.0.1]
>>> QUIT
221 2.0.0 transfusion.vm closing connection
You have new mail in /var/mail/root

BitMessage on the CLI

https://github.com/Dokument/PyBitmessage-Daemon https://bitmessage.org/wiki/Compiling_instructions#Download_and_run_PyBitmessage

sudo apt-get install python openssl git python-qt4 … Download the source code from github: git clone https://github.com/Bitmessage/PyBitmessage $HOME/PyBitmessage Run PyBitmessage: ~/PyBitmessage/src/bitmessagemain.py If you receive a warning that you need to use python 2.7.5 or greater, and have followed the above instructions to upgrade it, your system may be attemping to run PyBitmessage with python 3. Run: python2 ~/PyBitmessage/src/bitmessagemain.py

You can leave python-qt4 out. After your first run of bitmessagemain.py, it will return this:

1
2
2013-12-31 23:14:08,057 - DEBUG - reloading keys from keys.dat file
2013-12-31 23:14:08,167 - DEBUG - reloading subscriptions...

PyBitmessage requires PyQt unless you want to run it as a daemon and interact with it using the API. You can download PyQt from http://www.riverbankcomputing.com/software/pyqt/download or by searching Google for ‘PyQt Download’. If you want to run in daemon mode, see https://bitmessage.org/wiki/Daemon

Error message: No module named PyQt4

Then follow these instructions: https://bitmessage.org/wiki/Daemon Result: screenshot_142 An interesting POC Vanity address generator (singlethreaded, written in Python, don’t expect much): https://bitmessage.org/forum/index.php?topic=1727.0

Paranoia

https://github.com/n0g/arcane

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
$ torsocks ./arcane --hostname xxxmailserver.onion --username
yourusername --key AAAAAAAA
IMAP4 Password:
IMAP Server: xxxmailserver.onion
IMAP Port: 143
IMAP SSL: False
IMAP Username: yourusername
IMAP Mailbox: "INBOX"
.
IMAP Server: xxxmailserver.onion
IMAP Port: 143
IMAP SSL: False
IMAP Username: yourusername
IMAP Mailbox: "INBOX.Trash"
IMAP Server: xxxmailserver.onion
IMAP Port: 143
IMAP SSL: False
IMAP Username: yourusername
IMAP Mailbox: "INBOX.Sent"
IMAP Server: xxxmailserver.onion
IMAP Port: 143
IMAP SSL: False
IMAP Username: yourusername
IMAP Mailbox: "INBOX.Drafts"

A note: you can compile torsocks in a VM like virtualbox and edit /usr/local/etc/torsocks.conf to point to the tor daemon running on the host. In VBox’s NAT networking mode the host can be accessed through the gateway IP.

Your browser is out-of-date!

Update your browser to view this website correctly. Update my browser now

×