News for hackers. Stuff that matters.
Re:How Gmail’s Image Caching Affects Open Tracking by Goopplesoft on Thursday December 12, 2013 @11:24PM (#6899064)
Are you sure about this? Just tested it out:

    openssl s_client -connect  smtp.gmail.com:465 -crlf

    220 mx.google.com ESMTP u17sm2709629qeb.4 - gsmtp
    helo
    250 mx.google.com at your service
    auth login
    334 VXNlcm5hbWU6
    < BASE_64 USERNAME> 
    334 UGFzc3dvcmQ6
    < BASE_64 PASSWORD> 
    235 2.7.0 Accepted
    MAIL FROM: <my_email>
    250 2.1.0 OK u17sm2709629qeb.4 - gsmtp
    rcpt to: <my_email>
    250 2.1.5 OK u17sm2709629qeb.4 - gsmtp
    rcpt to: <[email protected]>
    250 2.1.5 OK u17sm2709629qeb.4 - gsmtp

I get an OK with BS emails too...
Re:How Gmail’s Image Caching Affects Open Tracking by tedunangst on Thursday December 12, 2013 @11:50PM (#6899128)
You should try telnet to port 25 and don't login. If you're sending what could be an outgoing email, it is more likely to queue it.

    MAIL FROM:<[email protected]>
    250 2.1.0 OK g15si484689qej.92 - gsmtp
    RCPT TO:<[email protected]>
    550-5.1.1 The email account that you tried to reach does not exist. Please try
    550-5.1.1 double-checking the recipient's email address for typos or
    550-5.1.1 unnecessary spaces. Learn more at
    550 5.1.1 http://support.google.com/mail/bin/answer.py?answer=6596 g15si484689qej.92 - gsmtp
Re:How Gmail’s Image Caching Affects Open Tracking by parhamn on Friday December 13, 2013 @01:11AM (#6899326)
Cool, thanks!