Imap Protocol Error 1 Bad Command Error 11
Contents |
Date Sat, 02 May 2015 17:35:17 +0200 Dear Patrick, I don't know, I have no good clue with this. Looking at the FAQ it could also be also quota. Look at the journal log on host2 if possible. ======================================================================= Q.
Imap Login Bad Command Error. 12
From XXX to Exchange 2010/2013 or Office365 I get this error message sometimes: "BAD Command command argument error 11 outlook mac Argument Error 11" R. This error message comes from Exchange IMAP server when it encounters any problem. Most of the time
Imap Login Bad Command Error. 11
it is one of the following: * Some messages are bigger than the size limit. 10 MB by default on Exchange. It can be upped by configuration for Exchange. If you can't configure this limit then command argument error 11 thunderbird use option --maxsize 10000000 for 10 MB, change it if needed) to tell imapsync to skip those messages. This value is 25 MB by default for Office365 --maxsize 25000000 imapsync ... --maxsize 10000000 # 10 MB for Exchange imapsync ... --maxsize 25000000 # 25 MB for Office365 * Quota reached. The whole account is full. It can be upped by configuration. * Some messages have some lines too long. Use option command argument error 11 error code 1026 --maxlinelength to skip messages whose max line length is over a number of bytes. --maxlinelength 1000 is a RFC2822 must but most server support higher values. Exchange supports 9900: imapsync ... --maxlinelength 9900 Have also in mind that Exchange closes the connection after 10 errors encountered so you might also see "BYE Connection closed" errors from Exchange, which means Exchange leaves the session and say goodbye, come back later. Rerun a sync then. ======================================================================= > I'm migrating thousands of mailboxes from Courier-Imap to Office > 365. Everything works fine, except that sometimes some messages are > not transfered and get the error "BAD Command Argument Error. 11". > > Hereis the command line used and some errors from the log: > //usr/bin/imapsync ... --host2 > outlook.office365.com --ssl2 --maxmessagespersecond 4 > --maxlinelength 9900 --tmpdir /mailsync --useuid > --disarmreadreceipts --nofoldersizes --reconnectretry2 0 > > ++++ Looping on each folder > > [INBOX]-> [Ancien systeme/INBOX] > cache directory: /mailsync/imapsync_cache/xxx.xxx.xxx/xxxxx/outlook.office365.com/xxxxx at xxx dot xxx/INBOX/Ancien systeme/INBOX > CACHE h1 h2: 39 files > - msg INBOX/91 {3662} couldn't append(Subject:[Re: Sujet de recherche =?ISO-8859-1?Q?=E0_la_ma=EEtrise?=]) to folder Ancien systeme/INBOX: 12 BAD Command Argument Error. 11 > - msg INBOX/157 {6163} couldn't append(Subject:[=?iso-8859-1?Q?Re:_Mots-cl=E9s?=]) to folder Ancien systeme/INBOX: 13 BAD Command Argument Error. 11 > - msg INBOX/164 {431797} couldn't append (Subject:[Re
BMO. For more details see Persona Deprecated. Last Comment Bug815087
Test-imapconnectivity
- The mail server responded: Command Argument Error 11 ( Non-Gmail IMAP server returns "BAD Command Argument Error. 11" to "UID fetch 1111 (UID X-GM-MSGID X-GM-THRID X-GM-LABELS ... BODY.PEEK[ ... ])" which is produced by is_gmail=true ) Summary: The mail server responded: Command Argument Error 11 ( Non-Gmail IMAP server ... Status: RESOLVED http://www.linux-france.org/prj/imapsync_list/msg02163.html FIXED Whiteboard: [Workaround: is_gmail=false] [gs] Keywords: Product: MailNews Core Classification: Components Component: Networking: IMAP (show other bugs) Version: 17 Platform: All All Importance: -- normal (vote) TargetMilestone: --- Assigned To: Nobody; OK to take it and work on it QA Contact: TriageOwner: Mentors: URL: http://gsfn.us/t/39sqa Duplicates: 815571 (view as bug list) Depends https://bugzilla.mozilla.org/show_bug.cgi?id=815087 on: 798663 Blocks: tb-gmailWIP 721316 Show dependency tree /graph Reported: 2012-11-26 03:21 PST by ace-heart Modified: 2012-12-23 19:34 PST (History) CC List: 6 users (show) ace-heart atuljangra66 david m-wada mozilla rmarko See Also: Crash Signature: (edit) QA Whiteboard: Iteration: --- Points: --- Tracking Flags: Attachments full imap log (189.44 KB, text/plain) 2012-11-28 02:41 PST, ace-heart no flags Details View All Add an attachment (proposed patch, testcase, etc.) Description ace-heart 2012-11-26 03:21:31 PST User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:17.0) Gecko/17.0 Firefox/17.0 Build ID: 20121120062532 Steps to reproduce: Tried to check email after an update from version 16 to 17 Actual results: The IMAP mail server responded: Command Argument Error 11, I checked all the settings, and everything was OK there. After rolling back to older version email was checked correctly. OS: Ubuntu 12.04 x64, mail server runs on M$ Exchange, using IMAP protocol. Expected results: Email should be checked for new messages C
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss http://serverfault.com/questions/334726/verify-imap-pop3-connection-to-microsoft-exchange-server-5-5 the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions http://athensfbc.com/pipermail/imap-tools_athensfbc.com/2012-April/000152.html Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up error 1 Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Verify IMAP/POP3 connection to Microsoft Exchange Server 5.5 up vote 1 down vote favorite I wanted to fully explore IMAP connections from the command line, if I can connect via Thunderbird, then I should be able to bad command error via telnet?! Microsoft detail IMAP login as :- LOGIN NTDOMAIN/NTACCOUNT/ALIAS PASSWORD The settings in my Thunderbird are :-
by: [ date ] [ thread ] [ subject ] [ author ] The problem was that certain standard IMAP commands are rejected by the Exchange 2007 IMAP server. Details are below if anyone is interested. The workaround was to issue a BODY[HEADER] command to retrieve the entire header rather than requesting the individual header fields that are needed. That resolved the problem. -Rick Commands rejected by the Exchange IMAP server: 1 fetch 1 (BODY[HEADER.FIELDS (UID MESSAGE-ID FLAGS) 1 BAD Command Argument Error. 11 1 fetch 1 (BODY[HEADER.FIELDS (MESSAGE-ID)]) 1 BAD Command Argument Error. 11 1 fetch 1 (BODY[HEADER.FIELDS (From)]) 1 BAD Command Argument Error. 11 1 fetch 1 (BODY[HEADER.FIELDS (Date)]) 1 BAD Command Argument Error. 11 I'm told by the IMAP experts on the IMAP-protocol list that the syntax of the commands being sent is legitimate. One person commented "Those commands all work well with my Exchange 2010 system. So maybe it's a problem specific to Exchange 2007?" -Rick Previous message: [IMAP-tools] imaptools empty folder problem Next message: [IMAP-tools] imapcopy feature request Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] More information about the IMAP-tools mailing list