fetchmail-devel — Development related discussion

[fetchmail-devel] fetchmail 6.2.9-rc5 available (hopefully last before 6.3.0)

[Matthias A. <mat...@gm...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Greetings,

I have just released fetchmail 6.2.9-rc5, the hopefully final release candidate
before 6.3.0, after further fixes to -rc4, mainly with the build
breaking but also some minor bug fixes, became necessary.

- -----------------------------------------------------------------------
Fetchmail needs your support - please consider a donation via:
<https://developer.berlios.de/developer/make_donation.php?user_id=2007>
- -----------------------------------------------------------------------

Changes since -rc4 are:
* Add full support for --service option. Matthias Andree
* Fix Japanese translation of "no other fetchmail is running". Debian
  Bug#329342, Takeshi Hamasaki. (MA)
* When getaddrinfo() fails resolving a service, log getaddrinfo() error. (MA)
* Fix bogus "cannot resolve service * to port number" error. Simon Barner. (MA)
* Failure to set up SSL connections now results in PS_SOCKET. Suggested by
  Thomas Wolff. Matthias Andree.
* Kerberos IV detection fix for FreeBSD 4. Simon Barner. (MA)
* Fix display and documentation of --envelope option. Matthias Andree
* Make "envelope 'Delivered-To'" work with dropdelivered. Timothy Lee. (MA)
* Add -DBIND_8_COMPAT to Darwin (MacOS X) compiles, to fix build problems on
  newer Darwin versions. Matthias Andree.
* fetchmail should now automatically detect if OpenSSL requires -ldl.
  Matthias Andree.
* Fix Solaris build with --disable-nls (blastwave.org). Matthias Andree.

I seek everyone to test it out, report remaining bugs, update outdated
translations (send your translated .po files to the translation
project's robot, it'll forward your translation to the -devel list) or
send patches for documentation or report inconsistencies (including
formatting!) in the documentation.

The software is available from:
<https://developer.berlios.de/project/showfiles.php?group_id=1824&release_id=7373>
<http://home.pages.de/~mandree/fetchmail/>


Regards,

- -- 
Matthias Andree
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)

iD8DBQFDNy5LvmGDOQUufZURAtUnAKCSPWUaeh5MikENnzNf925HeDBjkwCfZ4xm
0he4bws7kMg+19T7y64GH1c=
=X6Qr
-----END PGP SIGNATURE-----

[fetchmail-devel] [rdenis-debian-bts1@simphalempin.com: [pkg-fetchmail-maint] Bug#329975: fetchmail: IPv6 support]

[Nico G. <ni...@ng...>]

tags 329975 + upstream

----- Forwarded message from Rémi Denis-Courmont <rde...@si...> -----

Resent-Date: Sat, 24 Sep 2005 21:48:01 UTC
From: Rémi Denis-Courmont <rde...@si...>
To: Debian Bug Tracking System <su...@bu...>
X-Mailer: reportbug 3.17
Subject: [pkg-fetchmail-maint] Bug#329975: fetchmail: IPv6 support

Package: fetchmail
Version: 6.2.5-18
Severity: wishlist

fetchmail fails to resolve server DNS hostnames as AAAA entries. That's
all the more confusing as the man page mentions IPv6.

-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'stable'), (1, 'experimental')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.13.2
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)

Versions of packages fetchmail depends on:
ii  adduser                       3.67.0     Add and remove users and groups
ii  base-files                    3.1.7      Debian base system miscellaneous f
ii  debianutils                   2.14.3     Miscellaneous utilities specific t
ii  libc6                         2.3.5-6    GNU C Library: Shared libraries an
ii  libssl0.9.7                   0.9.7g-2   SSL shared libraries

Versions of packages fetchmail recommends:
ii  ca-certificates               20050804   Common CA Certificates PEM files

-- debconf information:
* fetchmail/initdefaultswarn:
* fetchmail/runasroot: false
* fetchmail/confwarn:
  fetchmail/fetchidswarn:
* fetchmail/systemwide: true

----- End forwarded message -----

-- 
Nico Golde - JAB: ni...@ja... | GPG: 0x73647CFF
http://www.ngolde.de | http://www.muttng.org | http://grml.org 
VIM has two modes - the one in which it beeps 
and the one in which it doesn't -- encrypted mail preferred

Re: [fetchmail-devel] [PATCH] Allow "Delivered-To" to be used as envelope header

[Matthias A. <mat...@gm...>]

Timothy Lee <tim...@si...> writes:

> I discovered the need for this patch under the follownig circumstances:
>
>    * ISP uses postfix for mail delivery
>    * ISP mail server delivers all e-mails to "catchall" mailbox. 
>      Postfix prepends two "Delivered-To" headers to the e-mail, like so:
>
>          Delivered-To: catchall
>          Delivered-To: actual-recipient
>
>    * In order to use multidrop with fetchmail, the following line in
>      fetchmailrc is used to obtain actual recipient for incoming e-mail:
>
>          envelope 1 "Delivered-To"
>
>    * The original handling of "Delivered-To" in transact.c discards all
>      "Delivered-To" lines, so the actual recipient is never found.

It should only do that if dropdelivered is set.
Nevermind, I have merged your patch for 6.2.9-rc5. Thanks again!

-- 
Matthias Andree

Re: [fetchmail-devel] Re: Fetchmail, NTLM and Exchange

[Rob M. <rob...@gm...>]

On 20/09/05, Yves Boisjoly <yve...@cg...> wrote:
>
> Hello Andree,
>
> You confused me with this latest email...
>
> Do you mean you whant me to delete every lines beginning with the minus sign
> and add every lines with the plus sign or if there is a way to download such a
> patch?

Try the "patch" command :)

--
                 Please keep list traffic on the list.
Rob MacGregor
      Whoever fights monsters should see to it that in the process he
        doesn't become a monster.                  Friedrich Nietzsche

Re: [fetchmail-devel] [PATCH] Allow "Delivered-To" to be used as envelope header

[Timothy L. <tim...@si...>]

Dear Matthias,

I discovered the need for this patch under the follownig circumstances:

    * ISP uses postfix for mail delivery
    * ISP mail server delivers all e-mails to "catchall" mailbox. 
      Postfix prepends two "Delivered-To" headers to the e-mail, like so:

          Delivered-To: catchall
          Delivered-To: actual-recipient

    * In order to use multidrop with fetchmail, the following line in
      fetchmailrc is used to obtain actual recipient for incoming e-mail:

          envelope 1 "Delivered-To"

    * The original handling of "Delivered-To" in transact.c discards all
      "Delivered-To" lines, so the actual recipient is never found.


Regards,
Timothy Lee


Matthias Andree wrote:

>Timothy Lee <tim...@si...> writes:
>  
>
>>Current version of fetchmail fails to extract the recipient address if 
>>"Delivered-To" is used as envelope header.  This patch fixes the
>>problem.
>>    
>>
>Can anyone please demonstrate or describe in detail the problem that is
>supposed to be fixed with this patch?
>  
>
>>diff -Naur fetchmail-6.2.5/transact.c fetchmail-6.2.5.new/transact.c
>>--- fetchmail-6.2.5/transact.c	2003-10-11 04:55:05.000000000 +0800
>>+++ fetchmail-6.2.5.new/transact.c	2005-03-02 16:41:50.000000000 +0800
>>@@ -380,6 +380,7 @@
>>     char		*received_for, *rcv, *cp;
>>     static char		*delivered_to = NULL;
>>     int 		n, linelen, oldlen, ch, remaining, skipcount;
>>+    int			delivered_to_count;
>>     struct idlist 	*idp;
>>     flag		no_local_matches = FALSE;
>>     flag		has_nuls;
>>@@ -416,6 +417,7 @@
>>     oldlen = 0;
>>     msgblk.msglen = 0;
>>     skipcount = 0;
>>+    delivered_to_count = 0;
>>     ctl->mimemsg = 0;
>> 
>>     for (remaining = fetchlen; remaining > 0 || protocol->delimited; )
>>@@ -665,10 +667,15 @@
>> 	 */
>> 	if (ctl->dropdelivered && !strncasecmp(line, "Delivered-To:", 13)) 
>> 	{
>>-	    if (delivered_to)
>>+	    if (delivered_to ||
>>+	    	ctl->server.envelope == STRING_DISABLED ||
>>+		!ctl->server.envelope ||
>>+		strcasecmp(ctl->server.envelope, "Delivered-To") ||
>>+		delivered_to_count != ctl->server.envskip)
>> 		free(line);
>> 	    else 
>> 		delivered_to = line;
>>+	    delivered_to_count++;
>> 	    continue;
>> 	}
>>    
>>

[fetchmail-devel] [PATCH] wrong message in ja.po for return code 8

[Nico G. <ni...@ng...>]

Hi, please include this.
Regards Nico
----- Forwarded message from Takeshi Hamasaki <hm...@sy...> -----

Subject: Bug#329342: fetchmail: wrong message in ja.po for return code 8
Resent-Date: Wed, 21 Sep 2005 09:33:12 UTC
From: Takeshi Hamasaki <hm...@sy...>
To: Debian Bug Tracking System <su...@bu...>
X-Mailer: reportbug 3.17

Package: fetchmail
Version: 6.2.5-18
Severity: minor


I found wrong message in Japanese when fetchmail ends with return code
8.
In fact, this is same as I reported in #233634 and once fixed in 6.2.5-3.
I attach the patch again.

--- po/ja.po.bak	2005-09-21 17:41:34.000000000 +0900
+++ po/ja.po	2005-09-21 17:41:34.000000000 +0900
@@ -675,7 +675,7 @@
 
 #: fetchmail.c:367 fetchmail.c:376
 msgid "fetchmail: no other fetchmail is running\n"
-msgstr "fetchmail: $BB>$N(B fetchmail $B$,<B9TCf$G$9!#(B\n"
+msgstr "fetchmail: $B<B9TCf$N(B fetchmail $B$OB8:_$7$^$;$s!#(B\n"
 
 #: fetchmail.c:382
 #, c-format


----- End forwarded message -----

-- 
Nico Golde - JAB: ni...@ja... | GPG: 0x73647CFF
http://www.ngolde.de | http://www.muttng.org | http://grml.org

Re: [fetchmail-devel] [PATCH] Allow "Delivered-To" to be used as envelope header

[Matthias A. <mat...@gm...>]

Timothy Lee <tim...@si...> writes:

> Current version of fetchmail fails to extract the recipient address if 
> "Delivered-To" is used as envelope header.  This patch fixes the
> problem.

Can anyone please demonstrate or describe in detail the problem that is
supposed to be fixed with this patch?

Thanks in advance,

> diff -Naur fetchmail-6.2.5/transact.c fetchmail-6.2.5.new/transact.c
> --- fetchmail-6.2.5/transact.c	2003-10-11 04:55:05.000000000 +0800
> +++ fetchmail-6.2.5.new/transact.c	2005-03-02 16:41:50.000000000 +0800
> @@ -380,6 +380,7 @@
>      char		*received_for, *rcv, *cp;
>      static char		*delivered_to = NULL;
>      int 		n, linelen, oldlen, ch, remaining, skipcount;
> +    int			delivered_to_count;
>      struct idlist 	*idp;
>      flag		no_local_matches = FALSE;
>      flag		has_nuls;
> @@ -416,6 +417,7 @@
>      oldlen = 0;
>      msgblk.msglen = 0;
>      skipcount = 0;
> +    delivered_to_count = 0;
>      ctl->mimemsg = 0;
>  
>      for (remaining = fetchlen; remaining > 0 || protocol->delimited; )
> @@ -665,10 +667,15 @@
>  	 */
>  	if (ctl->dropdelivered && !strncasecmp(line, "Delivered-To:", 13)) 
>  	{
> -	    if (delivered_to)
> +	    if (delivered_to ||
> +	    	ctl->server.envelope == STRING_DISABLED ||
> +		!ctl->server.envelope ||
> +		strcasecmp(ctl->server.envelope, "Delivered-To") ||
> +		delivered_to_count != ctl->server.envskip)
>  		free(line);
>  	    else 
>  		delivered_to = line;
> +	    delivered_to_count++;
>  	    continue;
>  	}
>  

-- 
Matthias Andree

Re: [fetchmail-devel] [PATCH] imap expunge problems

[Matthias A. <mat...@gm...>]

Sunil Shetye <sh...@bo...> writes:

> The fixes to recentcount and count (r3938) is interpreting the
> response from imap server to EXPUNGE wrongly.
>
> IMAP> A0448 EXPUNGE
> IMAP< * 20 EXPUNGE
> IMAP< * 20 EXPUNGE
> IMAP< * 20 EXPUNGE
> IMAP< A0448 OK EXPUNGE completed
>
> means that just three mails have been deleted, not 60! Of course, in
> the typical response:
>
> IMAP> A0455 EXPUNGE
> IMAP< * 1 EXPUNGE
> IMAP< * 1 EXPUNGE
> IMAP< * 1 EXPUNGE
> IMAP< * 1 EXPUNGE
> IMAP< A0455 OK EXPUNGE completed
>
> the wrong interpretation works out correctly. The attached patch fixes
> this problem.
>
> This patch also fixes another problem related to a missing expunge
> between separate folders. In this configuration:
>
> poll server
>     protocol imap
>     folders "INBOX" "INBOX.test"
>     expunge 100
>
> deleted mails from "INBOX" do not get expunged just before
> "INBOX.test" is selected.
>
> The attached patch fixes both the problems.

I have merged your patch for -rc4, thank you!

-- 
Matthias Andree

[fetchmail-devel] Re: Fetchmail, NTLM and Exchange

[Yves B. <yve...@cg...>]

Hello Andree,

You confused me with this latest email...

Do you mean you whant me to delete every lines beginning with the minus sign
and add every lines with the plus sign or if there is a way to download such a
patch?

I tried to change the line 77 as per your first email. It fixed the ntlm
authentication excepted that now the server complain with a "bad user or
password" message. Same thing as when I tried to telnet the box and play with
it manually...

Yves







On Tue, 20 Sep 2005, Matthias Andree wrote:

MA >On Mon, 19 Sep 2005, Yves Boisjoly wrote:
MA >
MA >> 	fetchmail: POP3< +OK Microsoft Exchange Server 2003 POP3 server version 6.5.7226.0 (<the_server>) ready.
MA >> 	fetchmail: POP3> AUTH MSN
MA >> 	fetchmail: POP3< -ERR The specified authentication package is not supported.
MA >
MA >Please try this patch: (Note you need to have flex or lex installed so
MA >that the configuration parser can be rebuilt.)
MA >
MA >Index: pop3.c
MA >===================================================================
MA >--- pop3.c	(revision 4284)
MA >+++ pop3.c	(working copy)
MA >@@ -69,12 +69,13 @@
MA >  * Much source (ntlm.h, smb*.c smb*.h) was borrowed from Samba.
MA >  */
MA >
MA >-static int do_pop3_ntlm(int sock, struct query *ctl)
MA >+static int do_pop3_ntlm(int sock, struct query *ctl,
MA >+	int msn_instead /** if true, send AUTH MSN, else send AUTH NTLM */)
MA > {
MA >     char msgbuf[2048];
MA >     int result,len;
MA >
MA >-    gen_send(sock, "AUTH MSN");
MA >+    gen_send(sock, msn_instead ? "AUTH MSN" : "AUTH NTLM");
MA >
MA >     if ((result = gen_recv(sock, msgbuf, sizeof msgbuf)))
MA > 	return result;
MA >@@ -318,25 +319,20 @@
MA >     if (!(ctl->server.sdps) && MULTIDROP(ctl) && strstr(greeting, "demon."))
MA >         ctl->server.sdps = TRUE;
MA > #endif /* SDPS_ENABLE */
MA >+
MA > #ifdef NTLM_ENABLE
MA >-	/* MSN servers require the use of NTLM (MSN) authentication */
MA >-	if (!strcasecmp(ctl->server.pollname, "pop3.email.msn.com") ||
MA >-	    ctl->server.authenticate == A_NTLM)
MA >-	{
MA >-	    if (!do_pop3_ntlm(sock, ctl))
MA >-	    {
MA >-		return(PS_SUCCESS);
MA >-	    }
MA >-	    else
MA >-	    {
MA >-		return(PS_AUTHFAIL);
MA >-	    }
MA >-	}
MA >+    /* MSN servers require the use of NTLM (MSN) authentication */
MA >+    if (!strcasecmp(ctl->server.pollname, "pop3.email.msn.com") ||
MA >+	    ctl->server.authenticate == A_MSN)
MA >+	return (do_pop3_ntlm(sock, ctl, 1) == 0) ? PS_SUCCESS : PS_AUTHFAIL;
MA >+    if (ctl->server.authenticate == A_NTLM)
MA >+	return (do_pop3_ntlm(sock, ctl, 0) == 0) ? PS_SUCCESS : PS_AUTHFAIL;
MA > #endif
MA >
MA >     switch (ctl->server.protocol) {
MA >     case P_POP3:
MA > #ifdef RPA_ENABLE
MA >+	/* XXX FIXME: AUTH probing (RFC1734) should become global */
MA > 	/* CompuServe POP3 Servers as of 990730 want AUTH first for RPA */
MA > 	if (strstr(ctl->remotename, "@compuserve.com"))
MA > 	{
MA >Index: conf.c
MA >===================================================================
MA >--- conf.c	(revision 4289)
MA >+++ conf.c	(working copy)
MA >@@ -284,6 +284,8 @@
MA > 		stringdump("auth", "ssh");
MA > 	    else if (ctl->server.authenticate == A_OTP)
MA > 		stringdump("auth", "otp");
MA >+	    else if (ctl->server.authenticate == A_MSN)
MA >+		stringdump("auth", "msn");
MA >
MA > #ifdef HAVE_RES_SEARCH
MA > 	    booldump("dns", ctl->server.dns);
MA >Index: NEWS
MA >===================================================================
MA >--- NEWS	(revision 4296)
MA >+++ NEWS	(working copy)
MA >@@ -197,6 +197,8 @@
MA >   Bug#212240. Sunil Shetye. (MA)
MA > * Fix MacOS X compilation failures in sink.c (ru_*time has incomplete type).
MA >   Berlios Bug #4725. Matthias Andree.
MA >+* Fix "auth ntlm" to send AUTH NTLM (rather than AUTH MSN). Add "auth msn"
MA >+  officially. Matthias Andree
MA >
MA > # INTERNAL CHANGES
MA > * Switched to automake. Matthias Andree.
MA >Index: fetchmail.man
MA >===================================================================
MA >--- fetchmail.man	(revision 4292)
MA >+++ fetchmail.man	(working copy)
MA >@@ -663,19 +663,21 @@
MA > AUTHENTICATION below for details).  The possible values are \fBany\fR,
MA > \&\fBpassword\fR, \fBkerberos_v5\fR, \fBkerberos\fR (or, for
MA > excruciating exactness, \fBkerberos_v4\fR), \fBgssapi\fR,
MA >-\fBcram-md5\fR, \fBotp\fR, \fBntlm\fR, and \fBssh\fR.  When \fBany\fR (the
MA >-default) is specified, fetchmail tries first methods that don't
MA >-require a password (GSSAPI, KERBEROS_IV); then it looks for methods
MA >-that mask your password (CRAM-MD5, X-OTP, NTLM); and only if the server
MA >-doesn't support any of those will it ship your password en clair.
MA >+\fBcram-md5\fR, \fBotp\fR, \fBntlm\fR, \fBmsn\fR and \fBssh\fR.  When
MA >+\fBany\fR (the default) is specified, fetchmail tries first methods that
MA >+don't require a password (GSSAPI, KERBEROS\ IV, KERBEROS\ 5); then it
MA >+looks for methods that mask your password (CRAM-MD5, X-OTP - note that
MA >+NTLM and MSN are not autoprobed); and only if the
MA >+server doesn't support any of those will it ship your password en clair.
MA > Other values may be used to force various authentication methods
MA > (\fBssh\fR suppresses authentication).  Any value other than
MA >-\&\fBpassword\fR, \fBcram-md5\fR, \fBntlm\fR or \fBotp\fR suppresses fetchmail's
MA >-normal inquiry for a password.  Specify \fBssh\fR when you are using
MA >-an end-to-end secure connection such as an ssh tunnel; specify
MA >-\fBgssapi\fR or \fBkerberos_v4\fR if you are using a protocol variant
MA >-that employs GSSAPI or K4.  Choosing KPOP protocol automatically
MA >-selects Kerberos authentication.  This option does not work with ETRN.
MA >+\&\fBpassword\fR, \fBcram-md5\fR, \fBntlm\fR, \fBmsn\fR or \fBotp\fR
MA >+suppresses fetchmail's normal inquiry for a password.  Specify \fBssh\fR
MA >+when you are using an end-to-end secure connection such as an ssh
MA >+tunnel; specify \fBgssapi\fR or \fBkerberos_v4\fR if you are using a
MA >+protocol variant that employs GSSAPI or K4.  Choosing KPOP protocol
MA >+automatically selects Kerberos authentication.  This option does not
MA >+work with ETRN.
MA > .SS Miscellaneous Options
MA > .TP
MA > .B \-f <pathname> | \-\-fetchmailrc <pathname>
MA >Index: fetchmail.c
MA >===================================================================
MA >--- fetchmail.c	(revision 4289)
MA >+++ fetchmail.c	(working copy)
MA >@@ -1536,6 +1536,9 @@
MA > 	case A_PASSWORD:
MA > 	    printf(GT_("  Password authentication will be forced.\n"));
MA > 	    break;
MA >+	case A_MSN:
MA >+	    printf(GT_("  MSN authentication will be forced.\n"));
MA >+	    break;
MA > 	case A_NTLM:
MA > 	    printf(GT_("  NTLM authentication will be forced.\n"));
MA > 	    break;
MA >Index: fetchmail.h
MA >===================================================================
MA >--- fetchmail.h	(revision 4289)
MA >+++ fetchmail.h	(working copy)
MA >@@ -70,9 +70,17 @@
MA > #define		A_KERBEROS_V5	6	/* authenticate w/ Kerberos V5 */
MA > #define 	A_GSSAPI	7	/* authenticate with GSSAPI */
MA > #define		A_SSH		8	/* authentication at session level */
MA >+#define		A_MSN		9	/* same as NTLM with keyword MSN */
MA >
MA >-/* some protocols (KERBEROS, GSSAPI, SSH) don't require a password */
MA >-#define NO_PASSWORD(ctl)	((ctl)->server.authenticate > A_OTP || (ctl)->server.protocol == P_ETRN)
MA >+/* some protocols or authentication types (KERBEROS, GSSAPI, SSH) don't
MA >+ * require a password */
MA >+#define NO_PASSWORD(ctl) \
MA >+    ((ctl)->server.authenticate == A_OTP \
MA >+     || (ctl)->server.authenticate == A_KERBEROS_V4 \
MA >+     || (ctl)->server.authenticate == A_KERBEROS_V5 \
MA >+     || (ctl)->server.authenticate == A_GSSAPI \
MA >+     || (ctl)->server.authenticate == A_SSH \
MA >+     || (ctl)->server.protocol == P_ETRN)
MA >
MA > /*
MA >  * Definitions for buffer sizes.  We get little help on setting maxima
MA >Index: rcfile_l.l
MA >===================================================================
MA >--- rcfile_l.l	(revision 4289)
MA >+++ rcfile_l.l	(working copy)
MA >@@ -100,6 +100,7 @@
MA > ssh		{ SETSTATE(0); yylval.proto = A_SSH; return AUTHTYPE;}
MA > (otp|opie)	{ SETSTATE(0); yylval.proto = A_OTP; return AUTHTYPE;}
MA > cram(-md5)?	{ SETSTATE(0); yylval.proto = A_CRAM_MD5; return AUTHTYPE;}
MA >+msn		{ SETSTATE(0); yylval.proto = A_MSN; return AUTHTYPE;}
MA > ntlm		{ SETSTATE(0); yylval.proto = A_NTLM; return AUTHTYPE;}
MA > <AUTH>password	{ SETSTATE(0); yylval.proto = A_PASSWORD; return AUTHTYPE;}
MA > timeout		{ return TIMEOUT;}
MA >Index: options.c
MA >===================================================================
MA >--- options.c	(revision 4289)
MA >+++ options.c	(working copy)
MA >@@ -418,6 +418,8 @@
MA > 		ctl->server.authenticate = A_GSSAPI;
MA > 	    else if (strcmp(optarg, "any") == 0)
MA > 		ctl->server.authenticate = A_ANY;
MA >+	    else if (strcmp(optarg, "msn") == 0)
MA >+		ctl->server.authenticate = A_MSN;
MA > 	    else {
MA > 		fprintf(stderr,GT_("Invalid authentication `%s' specified.\n"), optarg);
MA > 		errflag++;
MA >

-- 

=================================
Yves Boisjoly
Administrateur IXOS/Ariba
CGI - services à BCE
1350, boul. René-Lévesque,
suite 800 bureau 8.446
Montréal, Québec, H3G 1T4
Téléphone : 514-415-3000 x5510
Urgences  : 514-540-4672
Fax       : 514-415-3987
yve...@cg...
---------------------------------

AVIS DE CONFIDENTIALITÉ :

Ce message peut contenir des renseignements confidentiels appartenant
exclusivement au Groupe CGI Inc. ou à ses filiales. Si vous n'êtes pas le
destinataire indiqué ou prévu dans ce message (ou responsable de livrer ce
message à la personne indiquée ou prévue) ou si vous pensez que ce message
vous a été adressé par erreur, vous ne pouvez pas utiliser ou reproduire ce
message, ni le livrer à quelqu'un d'autre. Dans ce cas, vous devez le détruire
et vous êtes prié d'avertir l'expéditeur en répondant au courriel.

CONFIDENTIALITY NOTICE:

Proprietary/Confidential Information belonging to CGI Group Inc. and its
affiliates may be contained in this message. If you are not a recipient
indicated or intended in this message or responsible for delivery of this
message to such person), or you think for any reason that this message may
have been addressed to you in error, you may not use or copy or deliver this
message to anyone else.  In such case, you should destroy this message and are
asked to notify the sender by reply e-mail.

=================================

[fetchmail-devel] [PATCH] imap expunge problems

[Sunil S. <sh...@bo...>]

Hi,

The fixes to recentcount and count (r3938) is interpreting the
response from imap server to EXPUNGE wrongly.

IMAP> A0448 EXPUNGE
IMAP< * 20 EXPUNGE
IMAP< * 20 EXPUNGE
IMAP< * 20 EXPUNGE
IMAP< A0448 OK EXPUNGE completed

means that just three mails have been deleted, not 60! Of course, in
the typical response:

IMAP> A0455 EXPUNGE
IMAP< * 1 EXPUNGE
IMAP< * 1 EXPUNGE
IMAP< * 1 EXPUNGE
IMAP< * 1 EXPUNGE
IMAP< A0455 OK EXPUNGE completed

the wrong interpretation works out correctly. The attached patch fixes
this problem.

This patch also fixes another problem related to a missing expunge
between separate folders. In this configuration:

poll server
    protocol imap
    folders "INBOX" "INBOX.test"
    expunge 100

deleted mails from "INBOX" do not get expunged just before
"INBOX.test" is selected.

The attached patch fixes both the problems.

-- 
Sunil Shetye.

[fetchmail-devel] New Russian PO file for `fetchmail'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A revised PO file, for programs using the textual domain `fetchmail',
has been submitted by the team of translators taking care of the
Russian language.  This particular file, along with all other PO files
pertaining to the same textual domain, is available as:
>    http://www.iro.umontreal.ca/translation/maint/fetchmail/ru.po

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/maint/fetchmail/ru.po
>    http://translation.sf.net/maint/fetchmail/ru.po
>    ftp://tiger.informatik.hu-berlin.de/pub/po/maint/fetchmail/ru.po

This file has already been sent to you separately on 2005-09-20,
as a MIME invoice unpacking the file `fetchmail-6.2.9-rc3.ru.po'.

The following HTML page should also be updated by tomorrow.

>    http://www.iro.umontreal.ca/translation/HTML/domain-fetchmail.html

Please consider including all PO files, as they stand, in the `po/'
subdirectory of your next release of programs using that textual domain,
whether it is official or pretest.  Whenever you have a distribution ready
which holds a newer PO Template, please send the URL of this distribution
to the address below.  The distribution could be a pretest or a snapshot,
it does not even have to compile.  This is to be used by translators,
when they need to get some translation context from your sources.

Within the Translation Project, each PO Template file should have different
version numbers, but since it is not OK to have two different distributions
using same version numbers, this is not a problem in practice.

Contact me if any question arises.  Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...

[fetchmail-devel] Re: Fetchmail, NTLM and Exchange

[Matthias A. <mat...@gm...>]

On Mon, 19 Sep 2005, Yves Boisjoly wrote:

> 	fetchmail: POP3< +OK Microsoft Exchange Server 2003 POP3 server version 6.5.7226.0 (<the_server>) ready.
> 	fetchmail: POP3> AUTH MSN
> 	fetchmail: POP3< -ERR The specified authentication package is not supported.

Please try this patch: (Note you need to have flex or lex installed so
that the configuration parser can be rebuilt.)

Index: pop3.c
===================================================================
--- pop3.c	(revision 4284)
+++ pop3.c	(working copy)
@@ -69,12 +69,13 @@
  * Much source (ntlm.h, smb*.c smb*.h) was borrowed from Samba.
  */
 
-static int do_pop3_ntlm(int sock, struct query *ctl)
+static int do_pop3_ntlm(int sock, struct query *ctl,
+	int msn_instead /** if true, send AUTH MSN, else send AUTH NTLM */)
 {
     char msgbuf[2048];
     int result,len;
   
-    gen_send(sock, "AUTH MSN");
+    gen_send(sock, msn_instead ? "AUTH MSN" : "AUTH NTLM");
 
     if ((result = gen_recv(sock, msgbuf, sizeof msgbuf)))
 	return result;
@@ -318,25 +319,20 @@
     if (!(ctl->server.sdps) && MULTIDROP(ctl) && strstr(greeting, "demon."))
         ctl->server.sdps = TRUE;
 #endif /* SDPS_ENABLE */
+
 #ifdef NTLM_ENABLE
-	/* MSN servers require the use of NTLM (MSN) authentication */
-	if (!strcasecmp(ctl->server.pollname, "pop3.email.msn.com") ||
-	    ctl->server.authenticate == A_NTLM)
-	{
-	    if (!do_pop3_ntlm(sock, ctl))
-	    {
-		return(PS_SUCCESS);
-	    }
-	    else
-	    {
-		return(PS_AUTHFAIL);
-	    }
-	}
+    /* MSN servers require the use of NTLM (MSN) authentication */
+    if (!strcasecmp(ctl->server.pollname, "pop3.email.msn.com") ||
+	    ctl->server.authenticate == A_MSN)
+	return (do_pop3_ntlm(sock, ctl, 1) == 0) ? PS_SUCCESS : PS_AUTHFAIL;
+    if (ctl->server.authenticate == A_NTLM)
+	return (do_pop3_ntlm(sock, ctl, 0) == 0) ? PS_SUCCESS : PS_AUTHFAIL;
 #endif
 
     switch (ctl->server.protocol) {
     case P_POP3:
 #ifdef RPA_ENABLE
+	/* XXX FIXME: AUTH probing (RFC1734) should become global */
 	/* CompuServe POP3 Servers as of 990730 want AUTH first for RPA */
 	if (strstr(ctl->remotename, "@compuserve.com"))
 	{
Index: conf.c
===================================================================
--- conf.c	(revision 4289)
+++ conf.c	(working copy)
@@ -284,6 +284,8 @@
 		stringdump("auth", "ssh");
 	    else if (ctl->server.authenticate == A_OTP)
 		stringdump("auth", "otp");
+	    else if (ctl->server.authenticate == A_MSN)
+		stringdump("auth", "msn");
 
 #ifdef HAVE_RES_SEARCH
 	    booldump("dns", ctl->server.dns);
Index: NEWS
===================================================================
--- NEWS	(revision 4296)
+++ NEWS	(working copy)
@@ -197,6 +197,8 @@
   Bug#212240. Sunil Shetye. (MA)
 * Fix MacOS X compilation failures in sink.c (ru_*time has incomplete type).
   Berlios Bug #4725. Matthias Andree.
+* Fix "auth ntlm" to send AUTH NTLM (rather than AUTH MSN). Add "auth msn"
+  officially. Matthias Andree
 
 # INTERNAL CHANGES
 * Switched to automake. Matthias Andree.
Index: fetchmail.man
===================================================================
--- fetchmail.man	(revision 4292)
+++ fetchmail.man	(working copy)
@@ -663,19 +663,21 @@
 AUTHENTICATION below for details).  The possible values are \fBany\fR,
 \&\fBpassword\fR, \fBkerberos_v5\fR, \fBkerberos\fR (or, for
 excruciating exactness, \fBkerberos_v4\fR), \fBgssapi\fR,
-\fBcram-md5\fR, \fBotp\fR, \fBntlm\fR, and \fBssh\fR.  When \fBany\fR (the
-default) is specified, fetchmail tries first methods that don't
-require a password (GSSAPI, KERBEROS_IV); then it looks for methods
-that mask your password (CRAM-MD5, X-OTP, NTLM); and only if the server
-doesn't support any of those will it ship your password en clair.
+\fBcram-md5\fR, \fBotp\fR, \fBntlm\fR, \fBmsn\fR and \fBssh\fR.  When
+\fBany\fR (the default) is specified, fetchmail tries first methods that
+don't require a password (GSSAPI, KERBEROS\ IV, KERBEROS\ 5); then it
+looks for methods that mask your password (CRAM-MD5, X-OTP - note that
+NTLM and MSN are not autoprobed); and only if the
+server doesn't support any of those will it ship your password en clair.
 Other values may be used to force various authentication methods
 (\fBssh\fR suppresses authentication).  Any value other than
-\&\fBpassword\fR, \fBcram-md5\fR, \fBntlm\fR or \fBotp\fR suppresses fetchmail's
-normal inquiry for a password.  Specify \fBssh\fR when you are using
-an end-to-end secure connection such as an ssh tunnel; specify
-\fBgssapi\fR or \fBkerberos_v4\fR if you are using a protocol variant
-that employs GSSAPI or K4.  Choosing KPOP protocol automatically
-selects Kerberos authentication.  This option does not work with ETRN.
+\&\fBpassword\fR, \fBcram-md5\fR, \fBntlm\fR, \fBmsn\fR or \fBotp\fR
+suppresses fetchmail's normal inquiry for a password.  Specify \fBssh\fR
+when you are using an end-to-end secure connection such as an ssh
+tunnel; specify \fBgssapi\fR or \fBkerberos_v4\fR if you are using a
+protocol variant that employs GSSAPI or K4.  Choosing KPOP protocol
+automatically selects Kerberos authentication.  This option does not
+work with ETRN.
 .SS Miscellaneous Options
 .TP
 .B \-f <pathname> | \-\-fetchmailrc <pathname>
Index: fetchmail.c
===================================================================
--- fetchmail.c	(revision 4289)
+++ fetchmail.c	(working copy)
@@ -1536,6 +1536,9 @@
 	case A_PASSWORD:
 	    printf(GT_("  Password authentication will be forced.\n"));
 	    break;
+	case A_MSN:
+	    printf(GT_("  MSN authentication will be forced.\n"));
+	    break;
 	case A_NTLM:
 	    printf(GT_("  NTLM authentication will be forced.\n"));
 	    break;
Index: fetchmail.h
===================================================================
--- fetchmail.h	(revision 4289)
+++ fetchmail.h	(working copy)
@@ -70,9 +70,17 @@
 #define		A_KERBEROS_V5	6	/* authenticate w/ Kerberos V5 */
 #define 	A_GSSAPI	7	/* authenticate with GSSAPI */
 #define		A_SSH		8	/* authentication at session level */
+#define		A_MSN		9	/* same as NTLM with keyword MSN */
 
-/* some protocols (KERBEROS, GSSAPI, SSH) don't require a password */
-#define NO_PASSWORD(ctl)	((ctl)->server.authenticate > A_OTP || (ctl)->server.protocol == P_ETRN)
+/* some protocols or authentication types (KERBEROS, GSSAPI, SSH) don't
+ * require a password */
+#define NO_PASSWORD(ctl) \
+    ((ctl)->server.authenticate == A_OTP \
+     || (ctl)->server.authenticate == A_KERBEROS_V4 \
+     || (ctl)->server.authenticate == A_KERBEROS_V5 \
+     || (ctl)->server.authenticate == A_GSSAPI \
+     || (ctl)->server.authenticate == A_SSH \
+     || (ctl)->server.protocol == P_ETRN)
 
 /*
  * Definitions for buffer sizes.  We get little help on setting maxima
Index: rcfile_l.l
===================================================================
--- rcfile_l.l	(revision 4289)
+++ rcfile_l.l	(working copy)
@@ -100,6 +100,7 @@
 ssh		{ SETSTATE(0); yylval.proto = A_SSH; return AUTHTYPE;}
 (otp|opie)	{ SETSTATE(0); yylval.proto = A_OTP; return AUTHTYPE;}
 cram(-md5)?	{ SETSTATE(0); yylval.proto = A_CRAM_MD5; return AUTHTYPE;}
+msn		{ SETSTATE(0); yylval.proto = A_MSN; return AUTHTYPE;}
 ntlm		{ SETSTATE(0); yylval.proto = A_NTLM; return AUTHTYPE;}
 <AUTH>password	{ SETSTATE(0); yylval.proto = A_PASSWORD; return AUTHTYPE;}
 timeout		{ return TIMEOUT;}
Index: options.c
===================================================================
--- options.c	(revision 4289)
+++ options.c	(working copy)
@@ -418,6 +418,8 @@
 		ctl->server.authenticate = A_GSSAPI;
 	    else if (strcmp(optarg, "any") == 0)
 		ctl->server.authenticate = A_ANY;
+	    else if (strcmp(optarg, "msn") == 0)
+		ctl->server.authenticate = A_MSN;
 	    else {
 		fprintf(stderr,GT_("Invalid authentication `%s' specified.\n"), optarg);
 		errflag++;
-- 
Matthias Andree

[fetchmail-devel] Re: Fetchmail, NTLM and Exchange

[Matthias A. <mat...@gm...>]

Le lun, 19 Sep 2005, Yves Boisjoly à écrit:

> 	fetchmail: POP3< +OK Microsoft Exchange Server 2003 POP3 server version 6.5.7226.0 (<the_server>) ready.
> 	fetchmail: POP3> AUTH MSN
> 	fetchmail: POP3< -ERR The specified authentication package is not supported.fetchmail: Échec de l'autorisation sur <the_user>@<the_server>

Merci beaucoup.

Please edit line #77 of pop3.c (it contains "AUTH MSN"), change it to
"AUTH NTLM", then recompile, reinstall and see if it works and share
your findings. It works for me - albeit against a Cyrus server (not
Exch*ng* - I don't have such machines to test against).

Kind regards,

-- 
Matthias Andree

[fetchmail-devel] [Patch #618] try to fix MacOS X compile failure (resource.h related)

[<no...@be...>]

Patch #618 has been updated. 

Project: fetchmail
Category: None
Status: Open
Submitted by: m-a
Assigned to : none
Summary: try to fix MacOS X compile failure (resource.h related)

-------------------------------------------------------
For more info, visit:

http://developer.berlios.de/patch/?func=detailpatch&patch_id=618&group_id=1824

[fetchmail-devel] New Catalan PO file for `fetchmail'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A revised PO file, for programs using the textual domain `fetchmail',
has been submitted by the team of translators taking care of the
Catalan language.  This particular file, along with all other PO files
pertaining to the same textual domain, is available as:
>    http://www.iro.umontreal.ca/translation/maint/fetchmail/ca.po

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/maint/fetchmail/ca.po
>    http://translation.sf.net/maint/fetchmail/ca.po
>    ftp://tiger.informatik.hu-berlin.de/pub/po/maint/fetchmail/ca.po

This file has already been sent to you separately on 2005-09-19,
as a MIME invoice unpacking the file `fetchmail-6.2.9-rc3.ca.po'.

The following HTML page should also be updated by tomorrow.

>    http://www.iro.umontreal.ca/translation/HTML/domain-fetchmail.html

Please consider including all PO files, as they stand, in the `po/'
subdirectory of your next release of programs using that textual domain,
whether it is official or pretest.  Whenever you have a distribution ready
which holds a newer PO Template, please send the URL of this distribution
to the address below.  The distribution could be a pretest or a snapshot,
it does not even have to compile.  This is to be used by translators,
when they need to get some translation context from your sources.

Within the Translation Project, each PO Template file should have different
version numbers, but since it is not OK to have two different distributions
using same version numbers, this is not a problem in practice.

Contact me if any question arises.  Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...

[fetchmail-devel] Re: Fetchmail, NTLM and Exchange

[Yves B. <yve...@sy...>]

On Sat, 17 Sep 2005, Matthias Andree wrote:

MA >fetchmail has code in place to do NTLM auth with POP3, too, although the
MA >manual page doesn't say so. Can you show the "fetchmail --nosyslog -Nvv"
MA >snippet that shows the NTLM negotiation attempt?


Here is the result of the CAPA command (I changed strings for privacy):

	yves@Voyager:/soft/.install/Sources/02-WEB/01-Fetchmail$ telnet <the_server> 110
	Trying <the_server>...
	Connected to <the_server>.
	Escape character is '^]'.
	+OK Microsoft Exchange Server 2003 POP3 server version 6.5.7226.0 (<the_server>) ready.
	CAPA
	+OK Capability list follows
	TOP
	USER
	PIPELINING
	EXPIRE NEVER
	UIDL
	SASL NTLM
	.
	AUTH NTLM
	+OK
	QUIT
	-ERR Logon failure: unknown user name or bad password.
	QUIT
	+OK Microsoft Exchange Server 2003 POP3 server version 6.5.7226.0 signing off.
	Connection closed by foreign host.
	yves@Voyager:/soft/.install/Sources/02-WEB/01-Fetchmail$


Here is the fetchmail configuration file:

	# Configuration created Thu Sep  8 16:40:38 2005 by fetchmailconf
	set postmaster "yves"
	set bouncemail
	set no spambounce
	set properties ""
	set daemon 30

	poll <the_server> with proto POP3 auth ntlm
	       user 'username' there with password '*******' is 'yves' here options pass8bits

The problem seem to be with the authentication. Exchange interpret the
string "auth ntlm" as "auth msn"!

Here is the results of the command you asked:

	yves@Voyager:/soft/.install/Sources/02-WEB/01-Fetchmail$ fetchmail --nosyslog -Nvv -f .fetchmailrc.0
	fetchmail: démarrage de fetchmail 6.2.5 en tâche de fond
	fetchmail: 6.2.5 interroge <the_server> (protocole POP3) à lun 19 sep 2005 13:38:29 EDT : récupération en cours
	fetchmail: POP3< +OK Microsoft Exchange Server 2003 POP3 server version 6.5.7226.0 (<the_server>) ready.
	fetchmail: POP3> AUTH MSN
	fetchmail: POP3< -ERR The specified authentication package is not supported.fetchmail: Échec de l'autorisation sur <the_user>@<the_server>
	fetchmail: POP3> QUIT
	fetchmail: POP3< +OK Microsoft Exchange Server 2003 POP3 server version 6.5.7226.0 signing off.
	fetchmail: 6.2.5 interroge <the_server> (protocole POP3) à lun 19 sep 2005 13:38:30 EDT : interrogation finie
	fetchmail: État de la requête=3 (ECHEC DE L'AUTHENTIFICATION)
	fetchmail: Effacement du fichier fetchids.
	fetchmail: mise en sommeil à lun 19 sep 2005 13:38:30 EDT


Thank you,
Yves

-- 

Yves Boisjoly, Administrateur systèmes UNIX
Yve...@sy...
http://www.lepetittuxervateur.ca

[fetchmail-devel] New Polish PO file for `fetchmail'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A revised PO file, for programs using the textual domain `fetchmail',
has been submitted by the team of translators taking care of the
Polish language.  This particular file, along with all other PO files
pertaining to the same textual domain, is available as:
>    http://www.iro.umontreal.ca/translation/maint/fetchmail/pl.po

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/maint/fetchmail/pl.po
>    http://translation.sf.net/maint/fetchmail/pl.po
>    ftp://tiger.informatik.hu-berlin.de/pub/po/maint/fetchmail/pl.po

This file has already been sent to you separately on 2005-09-19,
as a MIME invoice unpacking the file `fetchmail-6.2.9-rc3.pl.po'.

The following HTML page should also be updated by tomorrow.

>    http://www.iro.umontreal.ca/translation/HTML/domain-fetchmail.html

Please consider including all PO files, as they stand, in the `po/'
subdirectory of your next release of programs using that textual domain,
whether it is official or pretest.  Whenever you have a distribution ready
which holds a newer PO Template, please send the URL of this distribution
to the address below.  The distribution could be a pretest or a snapshot,
it does not even have to compile.  This is to be used by translators,
when they need to get some translation context from your sources.

Within the Translation Project, each PO Template file should have different
version numbers, but since it is not OK to have two different distributions
using same version numbers, this is not a problem in practice.

Contact me if any question arises.  Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...

[fetchmail-devel] New PO Template file for `fetchmail'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A new PO Template file, for programs using the textual domain
`fetchmail', has just been made available to language teams for
translation, and a copy is available as:
>    http://www.iro.umontreal.ca/translation/domains/POT/fetchmail-6.2.9-rc3.pot

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/domains/POT/fetchmail-6.2.9-rc3.pot
>    http://translation.sf.net/domains/POT/fetchmail-6.2.9-rc3.pot
>    ftp://tiger.informatik.hu-berlin.de/pub/po/domains/POT/fetchmail-6.2.9-rc3.pot


In your releases, this file is usually found as `po/fetchmail.pot'.
It is created or updated automatically at `make dist' time, or
whenever you run `make update-po' in the `po/' subdirectory.  Whenever
you have a distribution ready which holds a newer PO Template, please
send the URL of this distribution to the address below.  The
distribution could be a pretest or a snapshot, it does not even have
to compile.  This is to be used by translators, when they need to get
some translation context from your sources.

Within the Translation Project, each PO Template file should have
different version numbers, but since it is not OK to have two
different distributions having same version numbers, this is not a
problem in practice.
Here is the URL information which has just been provided to translators for
your package.  Please inform the translation coordinator, at the address
given below, if the information does not appear to be adequate or current:

>    http://home.pages.de/~mandree/fetchmail/fetchmail-6.2.9-rc3.tar.bz2

Translated PO files will later be automatically e-mailed to you.

Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...

[fetchmail-devel] New Polish PO file for `fetchmail'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A revised PO file, for programs using the textual domain `fetchmail',
has been submitted by the team of translators taking care of the
Polish language.  This particular file, along with all other PO files
pertaining to the same textual domain, is available as:
>    http://www.iro.umontreal.ca/translation/maint/fetchmail/pl.po

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/maint/fetchmail/pl.po
>    http://translation.sf.net/maint/fetchmail/pl.po
>    ftp://tiger.informatik.hu-berlin.de/pub/po/maint/fetchmail/pl.po

This file has already been sent to you separately on 2005-09-18,
as a MIME invoice unpacking the file `fetchmail-6.2.9-rc2.pl.po'.

The following HTML page should also be updated by tomorrow.

>    http://www.iro.umontreal.ca/translation/HTML/domain-fetchmail.html

Please consider including all PO files, as they stand, in the `po/'
subdirectory of your next release of programs using that textual domain,
whether it is official or pretest.  Whenever you have a distribution ready
which holds a newer PO Template, please send the URL of this distribution
to the address below.  The distribution could be a pretest or a snapshot,
it does not even have to compile.  This is to be used by translators,
when they need to get some translation context from your sources.

Within the Translation Project, each PO Template file should have different
version numbers, but since it is not OK to have two different distributions
using same version numbers, this is not a problem in practice.

Contact me if any question arises.  Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...

[fetchmail-devel] Re: Fetchmail, NTLM and Exchange

[Matthias A. <mat...@gm...>]

On Sat, 17 Sep 2005, Yves Boisjoly wrote:

> Unfortunately, my employer decided to move to... Guess what... Exchange!

Eek.

> I was using Linux and Pine with fetchmail for my mail since two years. I
> recently got a Cisco VPN client for Linux and the last thing I have to fix in
> this migration is my mail.
> 
> I tried and tried to telnet on port 110, used fetchmail with the NTLM
> authentication, without any success.
> 
> I read a lot about the NTLM authentication and I do realised that it doesn't
> seem to be so easy to bypass the authentication level.
> 
> I also read that fetchmail can use the NTLM authentication over IMAP with
> Exchange, but the Exchange server I have to use only listen on POP3 (110).

fetchmail has code in place to do NTLM auth with POP3, too, although the
manual page doesn't say so. Can you show the "fetchmail --nosyslog -Nvv"
snippet that shows the NTLM negotiation attempt?

> I even tried with the Evolution client, apparently the better one to
> communicate with Exchange, but again, without good result.
> 
> I also tried to sniff my connection communication with the server, into
> Windows (shame on me!)... Everything is encrypted but I saw the "NTLM" string
> at some point...

Might just have been an advertisement.

Can you telnet to Exchange port 110, type CAPA and see what you get
(this is redundant if the fetchmail command above showed this
information already).

> So here are my two questions:
> 
> 	Is there any development in fetchmail for Exchange?

Not on my part, as I don't have Exchange accounts to test against. If
you could arrange for a test account for the fetchmail project, that
might help - we need a mail address where we can send our test mail and
the POP3 account to pull the mail from.

> 	If not, considering that I am pretty good with Perl, do you thing it
> could be feasible to incorporate a Perl call into fetchmail, that would take
> over the NTLM authentication, and give back the control to fetchmail after
> the authentication transaction?

Such code is already there - the "plugin" option can do what you want.
Your plugin would have to connect (TCP-wise) to the POP3 server, do the
NTLM stuff and then either abort or transparently transport all commands
(bidirectionally, so you'll probably have to delve into select() magic,
it's possible in Perl but looks ugly) until it has had EOF from both
sides.

> I could be interested to develop this part in Perl, but I don't want to go
> into C++, if it's what fetchmail is developed with...

fetchmail is done in C currently, and the best way would probably be to
fix NTLM auth.

-- 
Matthias Andree

Re: [fetchmail-devel] [PATCH] Re: deleting oversized messages

[Matthias A. <mat...@gm...>]

Sunil Shetye <sh...@bo...> writes:

> Hi Matthias,
>
> Quoting from Matthias Andree's mail on Thu, Sep 01, 2005 at 10:24:57AM +0200:
>> Sunil Shetye <sh...@bo...> writes:
>> 
>> > I had created a patch which adds another option to fetchmail. The old
>> > patch (against 6.2.4) along with some discussion can be found at:
>> >
>> > <http://lists.ccil.org/pipermail/fetchmail-friends/2003-October/008017.html>.
>> 
>> I had a very quick glance at this patch - I have two minor nits to pick:
>
> Ok, I have created a simplified patch. Please accept this for 6.3.0.

Done - it will show up in 6.2.9-rc3. I backed out the previous 4172 ->
4173 changes that enabled --flush with --limit outside daemon mode.

Thanks a lot for your patch!

-- 
Matthias Andree

[fetchmail-devel] New Russian PO file for `fetchmail'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A revised PO file, for programs using the textual domain `fetchmail',
has been submitted by the team of translators taking care of the
Russian language.  This particular file, along with all other PO files
pertaining to the same textual domain, is available as:
>    http://www.iro.umontreal.ca/translation/maint/fetchmail/ru.po

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/maint/fetchmail/ru.po
>    http://translation.sf.net/maint/fetchmail/ru.po
>    ftp://tiger.informatik.hu-berlin.de/pub/po/maint/fetchmail/ru.po

This file has already been sent to you separately on 2005-09-15,
as a MIME invoice unpacking the file `fetchmail-6.2.9-rc2.ru.po'.

The following HTML page should also be updated by tomorrow.

>    http://www.iro.umontreal.ca/translation/HTML/domain-fetchmail.html

Please consider including all PO files, as they stand, in the `po/'
subdirectory of your next release of programs using that textual domain,
whether it is official or pretest.  Whenever you have a distribution ready
which holds a newer PO Template, please send the URL of this distribution
to the address below.  The distribution could be a pretest or a snapshot,
it does not even have to compile.  This is to be used by translators,
when they need to get some translation context from your sources.

Within the Translation Project, each PO Template file should have different
version numbers, but since it is not OK to have two different distributions
using same version numbers, this is not a problem in practice.

Contact me if any question arises.  Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...

[fetchmail-devel] New PO Template file for `fetchmail'

[Translation P. R. <tra...@ir...>]

Hello, gentle maintainer. This is a message from the Translation
Project robot.

A new PO Template file, for programs using the textual domain
`fetchmail', has just been made available to language teams for
translation, and a copy is available as:
>    http://www.iro.umontreal.ca/translation/domains/POT/fetchmail-6.2.9-rc2.pot

The file should soon be made available in mirror sites as:

>    ftp://ftp.unex.es/pub/gnu-i18n/po/domains/POT/fetchmail-6.2.9-rc2.pot
>    http://translation.sf.net/domains/POT/fetchmail-6.2.9-rc2.pot
>    ftp://tiger.informatik.hu-berlin.de/pub/po/domains/POT/fetchmail-6.2.9-rc2.pot


In your releases, this file is usually found as `po/fetchmail.pot'.
It is created or updated automatically at `make dist' time, or
whenever you run `make update-po' in the `po/' subdirectory.  Whenever
you have a distribution ready which holds a newer PO Template, please
send the URL of this distribution to the address below.  The
distribution could be a pretest or a snapshot, it does not even have
to compile.  This is to be used by translators, when they need to get
some translation context from your sources.

Within the Translation Project, each PO Template file should have
different version numbers, but since it is not OK to have two
different distributions having same version numbers, this is not a
problem in practice.
Here is the URL information which has just been provided to translators for
your package.  Please inform the translation coordinator, at the address
given below, if the information does not appear to be adequate or current:

>    http://home.pages.de/~mandree/fetchmail/fetchmail-6.2.9-rc2.tar.bz2

Translated PO files will later be automatically e-mailed to you.

Thanks for your collaboration,

                                The Translation Project robot, in the
                                name of your translation coordinator.
                                mailto:tra...@ir...

[fetchmail-devel] [PATCH] minor configure problems

[Sunil S. <sh...@bo...>]

Hi,

When running ./configure --with-hesiod, -I/usr/athena/include gets
added to CPPFLAGS (as well as to CFLAGS) if hesiod.h is in
/usr/include.

This patch should fix the minor search problems.

-- 
Sunil Shetye.

[fetchmail-devel] [PATCH] Re: deleting oversized messages

[Sunil S. <sh...@bo...>]

Hi Matthias,

Quoting from Matthias Andree's mail on Thu, Sep 01, 2005 at 10:24:57AM +0200:
> Sunil Shetye <sh...@bo...> writes:
> 
> > I had created a patch which adds another option to fetchmail. The old
> > patch (against 6.2.4) along with some discussion can be found at:
> >
> > <http://lists.ccil.org/pipermail/fetchmail-friends/2003-October/008017.html>.
> 
> I had a very quick glance at this patch - I have two minor nits to pick:

Ok, I have created a simplified patch. Please accept this for 6.3.0.
Essentially, 'limitflush' is now a boolean option. So, one has to just
use --limitflush instead of --flush.

-- 
Sunil Shetye.