Correct Fetchmail with SSL? - Networking

This is a discussion on Correct Fetchmail with SSL? - Networking ; Hi, I have _almost_ successfully setup fetchmail with ssl to gmail. But a few small error messages. I post a trial run below: andrew@ilium:~$ fetchmail -v fetchmail: 6.3.8 querying pop.gmail.com (protocol POP3) at Wed 20 Jun 2007 23:24 :19 EST: ...

+ Reply to Thread
Results 1 to 2 of 2

Thread: Correct Fetchmail with SSL?

  1. Correct Fetchmail with SSL?

    Hi,

    I have _almost_ successfully setup fetchmail with ssl to gmail. But a
    few small error messages. I post a trial run below:

    andrew@ilium:~$ fetchmail -v
    fetchmail: 6.3.8 querying pop.gmail.com (protocol POP3) at Wed 20 Jun
    2007 23:24 :19 EST: poll started
    Trying to connect to 209.85.147.111/995...connected.
    fetchmail: Issuer Organization: Equifax
    fetchmail: Unknown Issuer CommonName
    fetchmail: Server CommonName: pop.gmail.com
    fetchmail: pop.gmail.com key fingerprint:
    59:51:61:89:CDD[.........]:97:A0 :395:B4
    fetchmail: pop.gmail.com fingerprints match.
    fetchmail: POP3< +OK Gpop ready for requests from 210.10.170.80
    m34pf139925waf
    fetchmail: POP3> CAPA
    fetchmail: POP3< +OK Capability list follows
    fetchmail: POP3< USER
    fetchmail: POP3< RESP-CODES
    fetchmail: POP3< EXPIRE 0
    fetchmail: POP3< LOGIN-DELAY 300
    fetchmail: POP3< X-GOOGLE-VERHOEVEN
    fetchmail: POP3< UIDL
    fetchmail: POP3< .
    fetchmail: POP3> USER andre[.........]5@gmail.com
    fetchmail: POP3< +OK send PASS
    fetchmail: POP3> PASS *
    fetchmail: POP3< +OK Welcome.
    fetchmail: POP3> STAT
    fetchmail: POP3< +OK 1 551
    fetchmail: POP3> LAST
    fetchmail: POP3< -ERR Not supported
    fetchmail: Not supported
    fetchmail: POP3> UIDL
    fetchmail: POP3< +OK
    fetchmail: POP3< 1 GmailId113494dd210f810d
    fetchmail: POP3< .
    1 message for andr[.......]@gmail.com at pop.gmail.com (551 octets).
    fetchmail: POP3> LIST 1
    fetchmail: POP3< +OK 1 551
    fetchmail: POP3> RETR 1
    fetchmail: POP3< +OK message follows
    reading message and[.....]@gmail.com@gmail-pop.l.google.com:1 of
    1 (551 oct ets)
    #***** not flushed
    fetchmail: POP3> QUIT
    fetchmail: POP3< +OK Farewell.
    fetchmail: 6.3.8 querying pop.gmail.com (protocol POP3) at Wed 20 Jun
    2007 23:24 :24 EST: poll completed
    fetchmail: normal termination, status 0

    I suspect the 'notflushed' message relates to me not having procmail
    setup properly yet. (I think fetchmail will not delete the remote
    messages until messages have been successfully delivered?)

    But I am puzzled about:

    fetchmail: POP3< +OK 1 551
    fetchmail: POP3> LAST
    fetchmail: POP3< -ERR Not supported
    fetchmail: Not supported

    And I would love to know if I have set the ssl connection up
    properly: can this be told from here??

    Thanks for your patience with this long post!

    Andrew
    --
    Andrew's Corner
    http://people.aapt.net.au/~adjlstrong/homer.html

  2. Re: Correct Fetchmail with SSL?

    andrew wrote:
    > Hi,
    >
    > I have _almost_ successfully setup fetchmail with ssl to gmail. But a
    > few small error messages. I post a trial run below:
    >
    > andrew@ilium:~$ fetchmail -v
    > fetchmail: 6.3.8 querying pop.gmail.com (protocol POP3) at Wed 20 Jun
    > 2007 23:24 :19 EST: poll started
    > Trying to connect to 209.85.147.111/995...connected.
    > fetchmail: Issuer Organization: Equifax
    > fetchmail: Unknown Issuer CommonName
    > fetchmail: Server CommonName: pop.gmail.com
    > fetchmail: pop.gmail.com key fingerprint:
    > 59:51:61:89:CDD[.........]:97:A0 :395:B4
    > fetchmail: pop.gmail.com fingerprints match.
    > fetchmail: POP3< +OK Gpop ready for requests from 210.10.170.80
    > m34pf139925waf
    > fetchmail: POP3> CAPA
    > fetchmail: POP3< +OK Capability list follows
    > fetchmail: POP3< USER
    > fetchmail: POP3< RESP-CODES
    > fetchmail: POP3< EXPIRE 0
    > fetchmail: POP3< LOGIN-DELAY 300
    > fetchmail: POP3< X-GOOGLE-VERHOEVEN
    > fetchmail: POP3< UIDL
    > fetchmail: POP3< .
    > fetchmail: POP3> USER andre[.........]5@gmail.com
    > fetchmail: POP3< +OK send PASS
    > fetchmail: POP3> PASS *
    > fetchmail: POP3< +OK Welcome.
    > fetchmail: POP3> STAT
    > fetchmail: POP3< +OK 1 551
    > fetchmail: POP3> LAST
    > fetchmail: POP3< -ERR Not supported
    > fetchmail: Not supported
    > fetchmail: POP3> UIDL
    > fetchmail: POP3< +OK
    > fetchmail: POP3< 1 GmailId113494dd210f810d
    > fetchmail: POP3< .
    > 1 message for andr[.......]@gmail.com at pop.gmail.com (551 octets).
    > fetchmail: POP3> LIST 1
    > fetchmail: POP3< +OK 1 551
    > fetchmail: POP3> RETR 1
    > fetchmail: POP3< +OK message follows
    > reading message and[.....]@gmail.com@gmail-pop.l.google.com:1 of
    > 1 (551 oct ets)
    > #***** not flushed
    > fetchmail: POP3> QUIT
    > fetchmail: POP3< +OK Farewell.
    > fetchmail: 6.3.8 querying pop.gmail.com (protocol POP3) at Wed 20 Jun
    > 2007 23:24 :24 EST: poll completed
    > fetchmail: normal termination, status 0
    >
    > I suspect the 'notflushed' message relates to me not having procmail
    > setup properly yet. (I think fetchmail will not delete the remote
    > messages until messages have been successfully delivered?)
    >


    non flushed meansthey havent been removed from the Gmail server. this is
    controlled by the "options keep" in fetchmailrc.


    > But I am puzzled about:
    >
    > fetchmail: POP3< +OK 1 551
    > fetchmail: POP3> LAST
    > fetchmail: POP3< -ERR Not supported
    > fetchmail: Not supported
    >
    > And I would love to know if I have set the ssl connection up
    > properly: can this be told from here??


    peer at your packets with ethereal/wireshark.


    >
    > Thanks for your patience with this long post!
    >
    > Andrew



    This sorted it out for me.


    poll pop.googlemail.com with proto POP3 and options uidl
    user 'USER@gmail.com' there with password 'put password here' is
    'LOCAL USER GOES HERE' here
    options keep ssl sslcertck sslcertpath /etc/ssl/certs/

    Debian handily has a package called ca-certificates so they were all
    handily there as (I believe) open-ssl recomends them.

    good luck on your mission but be careful with procmail

    --
    dave

+ Reply to Thread