OfflineIMAP

I'm not sure where the bug is here. OfflineIMAP authenticates fine for me and everyone else. Does your password contain a percent sign?

If not, it would be interesting to compare the LOGIN it sends that yields an error with the one it sends that works.

> I'm not sure where the bug is here. OfflineIMAP authenticates fine for me and everyone else.

But for sure it is.

> Does your password contain a percent sign?

No, only alpha-numeric characters (for both, see below).

> If not, it would be interesting to compare the LOGIN it sends that yields an error with the one it sends that works.

I'm not sure the problem is there. Account information are good.

I just added a new account ("accounts = Test, Epsi") and the authentication problem moves to the /last/ account (with and without the command argument "-1").
The symptom is the same : giving the password by the interactive way is ok (after the authentication problem) but not it doesn't authenticate by the non-interactive way.

I don't know if /last/ is the good term but the sync order is this one :
Account sync main:
Establishing connection to imap.laposte.net:143.
Account sync Epsi:
Establishing connection to imap.googlemail.com:993.

Anyway, just adding a new account made the Test account authentication success (account Test didn't changed). The new Epsi account has now an authentication problem though (password checked in .offlineimaprc).

Cheers.

Forgot the new error message :

Account sync Epsi:
RemoteEpsi: LOGIN command error: BAD ['Failed to parse your command 3if1344813fge.4']

I added a third different account.

The authentication for the first and the second accounts is now ok, but not for the last one :

Account sync progedys:
Remoteprogedys: Error in IMAP command received by server.
Remoteprogedys: Enter password:

Any idea ?

Cheers,

I solved the problem by removing all the commentary (placed after the accounts information).

Please tell me if you can (or not) correct this, I have an open bug at gentoo. Is the parser of the configuration file good ?

##################################################

1. General definitions ##################################################

###[general]

1. This specifies where offlineimap is to store its metadata.
2. This directory will be created if it does not already exist.

###metadata = ~/.offlineimap

1. This variable specifies which accounts are defined. Separate them
2. with commas. Account names should be alphanumeric only.
3. You will need to specify one section per account below. You may
4. not use "general" for an account name. #

###accounts = Test

1. Offlineimap can synchronize more the one account at a time. If you
2. want to enable this feature, set the below value to something
3. greater than 1. To force it to synchronize only one account at a
4. time, set it to 1. #

###maxsyncaccounts = 1

1. You can specify one or more user interface modules for OfflineIMAP
2. to use. OfflineIMAP will try the first in the list, and if it
3. fails, the second, and so forth. #
4. The pre-defined options are:
5. Tk.Blinkenlights -- A graphical interface, shows LEDs and a single log
6. Tk.VerboseUI -- A graphical interface, shows logs per thread
7. Curses.Blinkenlights -- A text-based (terminal) interface similar to
8. Tk.Blinkenlights
9. TTY.TTYUI -- a text-based (terminal) interface
10. Noninteractive.Basic -- Noninteractive interface suitable for cronning
11. Noninteractive.Quiet -- Noninteractive interface, generates no output
12. except for errors. #
13. You can override this with a command-line option -u.

###ui = Tk.Blinkenlights, Tk.VerboseUI, Curses.Blinkenlights, TTY.TTYUI,
###Noninteractive.Basic, Noninteractive.Quiet

1. If you try to synchronize messages to a read-only folder,
2. OfflineIMAP will generate a warning. If you want to suppress these
3. warnings, set ignore-readonly to yes. Read-only IMAP folders allow
4. reading but not modification, so if you try to change messages in
5. the local copy of such a folder, the IMAP server will prevent
6. OfflineIMAP from propogating those changes to the IMAP server.

###ignore-readonly = no

1. Advanced settings

1. You can give a Python source filename here and all config file
2. python snippets will be evaluated in the context of that file.
3. This allows you to e.g. define helper functions in the Python
4. source file and call them from this config file. You can find
5. an example of this in the manual. #
6. pythonfile = ~/.offlineimap.py #

##################################################

1. Mailbox name recorder ##################################################

#[mbnames]

1. offlineimap can record your mailbox names in a format you specify.
2. You can define the header, each mailbox item, the separator,
3. and the footer. Here is an example for Mutt.
4. If enabled is yes, all six setting must be specified, even if they
5. are just the empty string "". #
6. The header, peritem, sep, and footer are all Python expressions passed
7. through eval, so you can (and must) use Python quoting.

#enabled = no
#filename = ~/Mutt/muttrc.mailboxes
#header = "mailboxes "
#peritem = "+%(accountname)s/%(foldername)s"
#sep = " "
#footer = "\n"

1. You can also specify a folderfilter. It will apply to the
2. translated folder name here, and it takes TWO arguments:
3. accountname and foldername. In all other ways, it will
4. behave identically to the folderfilter for accounts. Please see
5. that section for more information and examples. #
6. Note that this filter can be used only to further restrict mbnames
7. to a subset of folders that pass the account's folderfilter.

##################################################

1. Blinkenlights configuration ##################################################

#[ui.Tk.Blinkenlights]

1. Specifies the default number of lines in the log.

###loglines = 5

1. Specifies how many lines are in the scrollback log buffer.

###bufferlines = 500

1. If true, says that the log should be enabled by default.
2. Otherwise, you have to click "Show Log" to enable the log.

###showlog = false

1. Sets the font information.

###fontfamily = Helvetica
###fontsize = 8

##################################################

1. Accounts ##################################################

1. This is an account definition clause. You'll have one of these
2. for each account listed in general/accounts above.

###[Account Test]

1. Basic settings

1. These settings specify the two folders that you will be syncing.
2. You'll need to have a "Repository ..." section for each one.

###localrepository = LocalExample
###remoterepository = RemoteExample

1. Advanced settings

1. You can have offlineimap continue running indefinately, automatically
2. syncing your mail periodically. If you want that, specify how
3. frequently to do that (in minutes) here. You can also specify
4. fractional minutes (ie, 3.25).

1. autorefresh = 5

###[Repository LocalExample]

1. This is one of the two repositories that you'll work with given the
2. above example. Each repository requires a "type" declaration. #
3. The types supported are Maildir and IMAP. #

###type = Maildir

1. Specify local repository. Your IMAP folders will be synchronized
2. to maildirs created under this path. OfflineIMAP will create the
3. maildirs for you as needed.

###localfolders = ~/Mail/ni.s_laposte.net

1. You can specify the "path separator character" used for your Maildir
2. folders. This is inserted in-between the components of the tree.
3. It defaults to ".". If you want your Maildir folders to be nested,
4. set it to "/".

###sep = .

###[Repository RemoteExample]

1. And this is the remote repository. For now, we only support IMAP here.

###type = IMAP

1. Specify the remote hostname.
   ###remotehost = imap.laposte.net

1. Whether or not to use SSL.
   ###ssl = no

1. Specify the port. If not specified, use a default port.
2. remoteport = 993

1. Specify the remote user name.
   ###remoteuser = ni.s

1. There are three ways to specify the password for the remote IMAP
2. server: #
3. 1. No password at all specified in the config file. You will
4. be prompted for the password when OfflineIMAP starts. #
5. 2. The remote password stored in this file with the remotepass
6. option. Example: #
   ###remotepass = *** #
7. 3. The remote password stored as a single line in an external
8. file, which is referenced by the remotefile option. Example: #
9. remotepassfile = ~/Password.IMAP.Account1 #
10. 4. With a preauth tunnel. With this method, you invoke an external
11. program that is guaranteed NOT to ask for a password, but rather
12. to read from stdin and write to stdout an IMAP procotol stream
13. that begins life in the PREAUTH state. When you use a tunnel,
14. you do NOT specify a user or password (if you do, they'll be
15. ignored.) Instead, you specify a preauthtunnel, as this
16. example illustrates for Courier IMAP on Debian: #
17. preauthtunnel = ssh -q imaphost '/usr/bin/imapd ./Maildir' #

1. Advanced settings

1. Some IMAP servers need a "reference" which often refers to the
2. "folder root". This is most commonly needed with UW IMAP, where
3. you might need to specify the directory in which your mail is
4. stored. Most users will not need this. #
5. reference = Mail

1. OfflineIMAP can use multiple connections to the server in order
2. to perform multiple synchronization actions simultaneously.
3. This may place a higher burden on the server. In most cases,
4. setting this value to 2 or 3 will speed up the sync, but in some
5. cases, it may slow things down. The safe answer is 1. You should
6. probably never set it to a value more than 5.

###maxconnections = 1

1. OfflineIMAP normally closes IMAP server connections between refreshes if
2. the global option autorefresh is specified. If you wish it to keep the
3. connection open, set this to true. If not specified, the default is
4. false. Keeping the connection open means a faster sync start the
5. next time and may use fewer server resources on connection, but uses
6. more server memory. This setting has no effect if autorefresh is not set.

#holdconnectionopen = no

1. If you want to have "keepalives" sent while waiting between syncs,
2. specify the amount of time IN SECONDS between keepalives here. Note that
3. sometimes more than this amount of time might pass, so don't make it
4. tight. This setting has no effect if autorefresh and holdconnectionopen
5. are not both set.

1. keepalive = 60

1. Normally, OfflineIMAP will expunge deleted messages from the server.
2. You can disable that if you wish. This means that OfflineIMAP will
3. mark them deleted on the server, but not actually delete them.
4. You must use some other IMAP client to delete them if you use this
5. setting; otherwise, the messgaes will just pile up there forever.
6. Therefore, this setting is definately NOT recommended. #
7. expunge = no
8. You can specify a folder translator. This must be a eval-able
9. Python expression that takes a foldername arg and returns the new
10. value. I suggest a lambda. This example below will remove "INBOX." from
11. the leading edge of folders (great for Courier IMAP users) #
12. WARNING: you MUST construct this such that it NEVER returns
13. the same value for two folders, UNLESS the second values are
14. filtered out by folderfilter below. Failure to follow this rule
15. will result in undefined behavior #
16. nametrans = lambda foldername: re.sub('^INBOX\.', '', foldername)

1. Using Courier remotely and want to duplicate its mailbox naming
2. locally? Try this: #
3. nametrans = lambda foldername: re.sub('^INBOX\.*', '.', foldername)

1. You can specify which folders to sync. You can do it several ways.
2. I'll provide some examples. The folderfilter operates on the
3. UNTRANSLATED name, if you specify nametrans. It should return
4. true if the folder is to be included; false otherwise. #
5. Example 1: synchronizing only INBOX and Sent. #
6. folderfilter = lambda foldername: foldername in ['INBOX', 'Sent'] #
7. Example 2: synchronizing everything except Trash. #
8. folderfilter = lambda foldername: foldername not in ['Trash'] #
9. Example 3: Using a regular expression to exclude Trash and all folders
10. containing the characters "Del". #
11. folderfilter = lambda foldername: not re.search('(^Trash$|Del)', foldername) #
12. If folderfilter is not specified, ALL remote folders will be
13. synchronized. #
14. You can span multiple lines by indenting the others. (Use backslashes
15. at the end when required by Python syntax) For instance: #
16. folderfilter = lambda foldername: foldername in
17. ['INBOX', 'Sent Mail', 'Deleted Items',
18. 'Received'] #
19. FYI, you could also include every folder with: #
20. folderfilter = lambda foldername: 1 #
21. And exclude every folder with: #
22. folderfilter = lambda foldername: 0

1. You can specify folderincludes to include additional folders.
2. It should return a Python list. This might be used to include a
3. folder that was excluded by your folderfilter rule, to include a
4. folder that your server does not specify with its LIST option, or
5. to include a folder that is outside your basic reference. Some examples: #
6. To include debian.user and debian.personal: #
7. folderincludes = ['debian.user', 'debian.personal'] #
8. To include your INBOX (UW IMAPd users will find this useful if they
9. specify a reference): #
10. folderincludes = ['INBOX'] #
11. To specify a long list: #
12. folderincludes = ['box1', 'box2', 'box3', 'box4',
13. 'box5', 'box6']

#folderincludes = ['INBOX', 'INBOX.ABUL' ]

1. You can specify foldersort to determine how folders are sorted.
2. This affects order of synchronization and mbnames. The expression
3. should return -1, 0, or 1, as the default Python cmp() does. The
4. two arguments, x and y, are strings representing the names of the folders
5. to be sorted. The sorting is applied AFTER nametrans, if any. #
6. To reverse the sort: #
7. foldersort = lambda x, y: -cmp(x, y)

I don't quite follow; it looks like you have commented out everything. Can you please post the username and password section of your config file before and after making the fix that you did?

The parser is from Python and I would be quite surprised if it has a bug. Note that comments must go on lines by themselves; if you had a comment after the remoteuser = or remotepass = bit, on the same line, that could account for the problem.

> I don't quite follow; it looks like you have commented out everything.

Probably because I didn't post the entire .offlineimaprc in my original post. I use to remove commentaries.

> Can you please post the username and password section of your config file before and after making the fix that you did?

Sorry, I haven't the diff anymore.

> if you had a comment after the remoteuser = or remotepass = bit, on the same line, that could account for the problem.

It wasn't the case, for sure.

As I can't give more information on the fix (sorry, really), I think we can close this bug here. I would try to reproduce it and I'll give you the steps (if achieved).