aboutsummaryrefslogtreecommitdiffstats
path: root/dist-tools/test/test-request
blob: 56c31be7b4cf080ddcfe81ddedc635f2d29f31af (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
I maintain an open-source POP and IMAP client called fetchmail.  It is
widely used in the Linux and open-source community, and is probably
the single most popular remote-mail client in that world.  You can
find out more about this project at
<http://fetchmail.berlios.de/>.

In order to be able to do thorough regression testing before each release,
I collect test accounts on as many different kinds of POP3, IMAP, and
ODMR servers as possible.  Because fetchmail is strictly conformant to the 
remote-mail RFCs, many server developers have found fetchmail a useful
standards-conformance test.

I'm writing to request test accounts on your server.  I support all flavors 
of POP2, POP3, IMAP and ODMR with either plain-password, CRAM-MD5, NTLM, 
GSSAPI, or Kerberos authentication.  I also support SSL/TLS.

It would be very helpful if I could have a separate test account for
each protocol you support (that is, separate POP3, IMAP, and ODMR
accounts) so I can do automated regression testing without worrying
about mailbox race conditions.
CTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN"> <HTML> <HEAD> <TITLE> [fetchmail] Patch for IMAP idling where idling is unsupported </TITLE> <LINK REL="Index" HREF="index.html" > <LINK REL="made" HREF="mailto:esr%40thyrsus.com"> <META NAME="robots" CONTENT="index,nofollow"> <LINK REL="Previous" HREF="007705.html"> <LINK REL="Next" HREF="007706.html"> </HEAD> <BODY BGCOLOR="#ffffff"> <H1>[fetchmail] Patch for IMAP idling where idling is unsupported </H1> <B>Eric S. Raymond </B> <A HREF="mailto:esr%40thyrsus.com" TITLE="[fetchmail] Patch for IMAP idling where idling is unsupported">esr@thyrsus.com </A><BR> <I>Mon, 21 Jul 2003 22:32:31 -0400</I> <P><UL> <LI> Previous message: <A HREF="007705.html">[fetchmail] Patch for IMAP idling where idling is unsupported </A></li> <LI> Next message: <A HREF="007706.html">[fetchmail] [PATCH] Debian bug #156592 again + update </A></li> <LI> <B>Messages sorted by:</B> <a href="date.html#7713">[ date ]</a> <a href="thread.html#7713">[ thread ]</a> <a href="subject.html#7713">[ subject ]</a> <a href="author.html#7713">[ author ]</a> </LI> </UL> <HR> <!--beginarticle--> <PRE>Chris Boyle &lt;<A HREF="mailto:fetchmail-friends@cmb.is-a-geek.org">fetchmail-friends@cmb.is-a-geek.org</A>&gt;: &gt;<i> Here's a patch I've written: where IDLE is unavailable, it uses periodic </I>&gt;<i> NOOP commands instead (every 28 seconds). Important behavioural change: </I>&gt;<i> the option &quot;idle&quot; will now always result in *some* form of idle. I think </I>&gt;<i> I read somewhere that some servers will unilaterally send status updates </I>&gt;<i> if you just hold the connection open, i.e. NOOPs would be unnecessary, </I>&gt;<i> but that doesn't seem to be the case anywhere I've tried. In any case, </I>&gt;<i> this patch copes with updates both as a response to the NOOPs and </I>&gt;<i> unilaterally sent between them. It functions exactly like normal idling </I>&gt;<i> (N.B. like normal idling, it is single-folder only), and hopefully </I>&gt;<i> includes all the appropriate changes to the documentation. Enjoy. :-) </I>&gt;<i> </I>&gt;<i> <A HREF="http://cmb.is-a-geek.org/downloads/fetchmail-6.2.2+noopidle.diff.gz">http://cmb.is-a-geek.org/downloads/fetchmail-6.2.2+noopidle.diff.gz</A> </I> Nice work. This will be in 6.2.4. -- &lt;a href=&quot;<A HREF="http://www.catb.org/~esr/"">http://www.catb.org/~esr/&quot;</A>&gt;Eric S. Raymond&lt;/a&gt; </PRE> <!--endarticle--> <HR> <P><UL> <!--threads--> <LI> Previous message: <A HREF="007705.html">[fetchmail] Patch for IMAP idling where idling is unsupported </A></li> <LI> Next message: <A HREF="007706.html">[fetchmail] [PATCH] Debian bug #156592 again + update </A></li> <LI> <B>Messages sorted by:</B> <a href="date.html#7713">[ date ]</a> <a href="thread.html#7713">[ thread ]</a> <a href="subject.html#7713">[ subject ]</a> <a href="author.html#7713">[ author ]</a> </LI> </UL> </body></html>