It looks like your data files are placed in a different directory than ~/.local/share (which is the usual place on most distros). This command may be of some help:
$ locate geary.ini And if that doesn't work: $ find ~ -name "geary.ini" As for the other information you pastebin'd, your dig command verifies what I said earlier about imap.gmail.com redirecting to 127.0.0.1. Again, this is not something I can help you with; you need to look into your DNS configuration and potentially the configuration of any proxy daemon you have installed. -- Jim On Thu, Jul 26, 2012 at 2:25 PM, Roowe羅立威 <[email protected]> wrote: I don't have geary.ini by default. some infomation is here.http://codepad.org/ZTswXWuV 2012/7/26 Jim Nelson <[email protected]> Check your geary.ini file for address settings. You can find it by looking in: ~/.local/share/geary There's a directory there that matches your email address. The geary.ini file is inside that directory. If you view the file you should see the hostname and port that Geary is using to connect to Gmail. I suspect you will see "imap.gmail.com" and port 993. Your log leads me to believe there's a DNS issue here. Geary is trying to connect to imap.gmail.com and is being redirected to 127.0.0.1, where the connection is denied. There are a number of possibilities why this is happening, but they are not related to Geary. -- Jim On Wed, Jul 25, 2012 at 1:09 PM, Roowe羅立威 <[email protected]> wrote: I know it is not a issue.I don't set proxy for geary, I want to know why the proxy is 127.0.0.1.How I change it? 2012/7/25 Jim Nelson <[email protected]> Hello Roowe, I'm not sure I understand the extent of the problem here. Which IMAP proxy are you using? When you configured your account information with Geary, did you specify your proxy (at 127.0.0.1) or did you specify a GMail account? The key line in your log output is this one: [deb] 16:05:00 imap-client-session-manager.vala:250: [ClientSession:imap.gmail.com/default:993] Connect failure: Could not connect to proxy server 127.0.0.1: Connection refused It appears the proxy is simply denying out connection. We've not done any work on Geary to see how it interoperates with proxies, however, this line leads me to believe it's not an issue with Geary but the proxy itself. -- Jim On Sat, Jul 21, 2012 at 10:28 AM, Roowe羅立威 <[email protected]> wrote: http://pastebin.com/0ZkvzvzK This is my debug log. I knew that there's something wrong with proxy, and I hadn't set proxy for geary yet as I'd just emerged the geary. However, when I try to set it, I could not find any configure docs . So I didn't know how to set proxy eventhough I didn't use it. PS. My OS is Funtoo, and the geary is 'geary 0.1.0+trunk'. thanks. -- Blog:：www.iroowe.com Twitter：twitter.com/roowe -- Blog:：www.iroowe.com Twitter：twitter.com/roowe -- Blog:：www.iroowe.com Twitter：twitter.com/roowe
_______________________________________________ Geary mailing list [email protected] http://lists.yorba.org/cgi-bin/mailman/listinfo/geary
