Your message dated Sun, 24 Nov 2013 21:42:28 +0100
with message-id <[email protected]>
and subject line Re: Bug#663915: archivemail: IMAP uri parse failure if 
username has @ sign and option -pwfile supplied
has caused the Debian Bug report #663915,
regarding archivemail: IMAP uri parse failure if username has @ sign and option 
-pwfile supplied
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)


-- 
663915: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=663915
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: archivemail
Version: 0.7.2-9
Severity: normal

If I supply a password file and my username has an @ sign the parser
incorrectly splits the IMAP url.

For example this works (correctly parsing the IMAP url and asking for a
password):

archivemail -d 180 --delete -pwfile -n
imaps://"[email protected]":@mail.example.com/INBOX

This however does not (we receive an IMAP error due to the bad parse):

archivemail -d 180 --delete --pwfile="mypassword.pwd" -n
imaps://"[email protected]":@mail.example.com/INBOX

In this case the username attempted is "bob" and the IMAP server is
"[email protected]".

I've played around a bit with forming the IMAP connection string
differently, but it doesn't make a difference. The offending code is a
little complex with it's regex approach, so I thought it best to leave
it to the author to make a call on the fix.

-- System Information:
Debian Release: 6.0.4
  APT prefers stable-updates
  APT policy: (500, 'stable-updates'), (500, 'stable')
Architecture: amd64 (x86_64)

Kernel: Linux 2.6.32-5-amd64 (SMP w/1 CPU core)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages archivemail depends on:
ii  python                  2.6.6-3+squeeze6 interactive high-level object-orie
ii  python-support          1.0.10           automated rebuilding support for P

archivemail recommends no packages.

archivemail suggests no packages.

-- no debconf information



--- End Message ---
--- Begin Message ---
Closing, this is not a bug.

My reply to the submitter was discarded by the BTS (hi procmail, hi
MAILER_DAEMON regex!), so I'm just re-sending the relevant part to the
BTS, for the public record. --

On Tue, Mar 13, 2012 at 10:50:55PM +0000, Matt Black wrote:
> archivemail -d 180 --delete --pwfile="mypassword.pwd" -n
> imaps://"[email protected]":@mail.example.com/INBOX
> 
> In this case the username attempted is "bob" and the IMAP server is
> "[email protected]".

Your URL looks malformed.

First, you need to escape the quotes for the shell so that archivemail
sees them.  This is even documented in the archivemail manpage.

Second, don't put a colon in the URL, when you are using the --pwfile
option.  "If the --pwfile option is set, archivemail does not look for a
password in the URL, and the colon is not considered a delimiter."

For example, the following URL should work:

  imaps://\"[email protected]\"@mail.example.com/INBOX

Ugly, but that's how the shell works.

I admit that archivemail could be more friendly and flag your URLs as
invalid, but that's another story.

Nikolaus

--- End Message ---

Reply via email to