Your message dated Sun, 8 Jul 2007 13:33:31 +0200
with message-id <[EMAIL PROTECTED]>
and subject line fetchmailconf: actually it works (but confused me)
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: fetchmailconf
Version: 6.3.6-1
Severity: normal
I have a service provider which requires my username to be:
[EMAIL PROTECTED]
fetchmailconf warns me that this can cause trouble, but I don't have a
choice since this is what fastmail explicitly requires. The produced
config file then contains the line:
poll mail.messagingengine.com with proto IMAP
user '[EMAIL PROTECTED]' there with password '[EMAIL PROTECTED]' is
'[EMAIL PROTECTED]' here options keep
Which isn't what I want (want just bkerin here). I hand edited it and
it solved my problem. But if major email service providers like
fastmail.fm are going to require usernames like this, I think it would
be worth some sort of configuration help to support it.
Incidently, I first tried to make things go using just fetchmail from
the command line, but using -u [EMAIL PROTECTED] there caused
'[EMAIL PROTECTED]@the.host.they.make.you.use' to get used
elsewhere. I didn't find out how to avoid this problem with command
line options, so I'm still coming out ahead with fetchmailconf. But
something maybe should be done to clarify how to use the command line
options in this case as well. Note that the.host.they.make.you.use is
not 'fastmail.fm', hence the trouble.
Britton
-- System Information:
Debian Release: testing/unstable
APT prefers testing
APT policy: (500, 'testing')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.17.3.emp3
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages fetchmailconf depends on:
ii fetchmail 6.3.6-1 SSL enabled POP3, APOP, IMAP mail
ii python 2.4.4-2 An interactive high-level object-o
ii python-central 0.5.12 register and build utility for Pyt
ii python-tk 2.4.4-1 Tkinter - Writing Tk applications
fetchmailconf recommends no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
closing this bug now if the issue is resolved.
Just for your information fetchmailconf is most likely to be
removed in future releases I think.
Cheers Nico
--
Nico Golde - http://ngolde.de - [EMAIL PROTECTED] - GPG: 0x73647CFF
For security reasons, all text in this mail is double-rot13 encrypted.
pgpiDbzgEKT0M.pgp
Description: PGP signature
--- End Message ---
