<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>Minor updates to fetchmail for multiple driver flexibility</title> 
  <pubDate>Fri, 10 Apr 2026 17:02:31 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/7761</link> 
  <atom:link rel="self" type="application/rss+xml" title="Minor updates to fetchmail for multiple driver flexibility" href="https://bugs.horde.org/ticket/7761/rss" /> 
  <description>Minor updates to fetchmail for multiple driver flexibility</description> 
 
   
   
  <item> 
   <title>I&#039;ve got a short little patch for handling multiple fetchmai</title> 
   <description>I&#039;ve got a short little patch for handling multiple fetchmail drivers.  

Currently, if you create a new driver in imp/lib/Fetchmail/drivers, it 

becomes available but uses the &#039;fetchmailprefs&#039; template - which may not 

wholly apply.  This patch changes the template file to $driver . 

&quot;prefs.html&quot; so you don&#039;t have to confuse your users :)



Also, this patch will just list the accounts that were created with the default 

&#039;imap&#039; driver for fetching within IMP.

I think it might be better in the long run to add another variable to 

the preference array that says whether or not this particular account 

should be available (or maybe &#039;enabled&#039;?) for IMP to Fetch.



For Example, the drivers I&#039;ve added are for FetchYahoo and GotMail 

(&#039;web&#039; driver), and IMAPSync.   These are all external to IMP, do not 

really conform to the standard account setup template, and don&#039;t run 

within IMP.



</description> 
   <pubDate>Mon, 08 Dec 2008 02:42:52 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7761#t51128</link> 
  </item> 
   
  <item> 
   <title>How is that supposed to work? $driver is always set as soon </title> 
   <description>How is that supposed to work? $driver is always set as soon as a driver is chosen, so fetchmailprefs.html is never loaded. A better patch would be to split up the current template into one for imap and one for pop3 (e.g. without the folder name setting). Then we would *always* load a $driver.&#039;fetchmailprefs.php&#039;. Of course you can&#039;t use $driver exactly this way, because it opens an file-inclusion vulnerability.

Further, the preg_match() stuff is of course not a viable solution. Instead the driver should specify whether it is able to run on-demand.</description> 
   <pubDate>Fri, 12 Dec 2008 17:48:11 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7761#t51213</link> 
  </item> 
   
  <item> 
   <title>I Agree - the driver should say if it should run on demand. </title> 
   <description>I Agree - the driver should say if it should run on demand.  I wasn&#039;t sure if this was something you were interested in, so I just made it work for me.



The &#039;fetchmailprefs.html&#039; is never loaded, because the prefs file is based on the driver name.  $driver.&#039;prefs.html&#039;.    So you&#039;re saying the template should just be $driver . html ?  I don&#039;t really see the difference between that and reading in the driver names in the Fetchmail.php file.

 function &amp;factory($driver, $params = array())

    {

        $driver = basename($driver);

        require_once dirname(__FILE__) . &#039;/Fetchmail/&#039; . $driver . &#039;.php&#039;;

??



IMHO, &#039;imap&#039; is a bad driver name.   It really should be &#039;fetchmail&#039;, or retrieve, or something else.  The protocols IMAP and POP both fall under this driver, so there&#039;s no need for a separate prefs file for each protocol.  Naming the driver one of the protocols is just confusing.

If you want to see the end result, create an account at vfemail.net </description> 
   <pubDate>Fri, 12 Dec 2008 18:03:14 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7761#t51214</link> 
  </item> 
   
  <item> 
   <title>If you are interested in submitting this (along with the oth</title> 
   <description>If you are interested in submitting this (along with the other fetchmail drivers, perhaps?) as a patch that works for Horde instead of just you, please revise. Otherwise, there isn&#039;t a lot of call to re-do this without additional drivers, in my opinion.</description> 
   <pubDate>Mon, 22 Dec 2008 03:29:54 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7761#t51385</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
