Due to Stefano Bagnara rapidly fixing the broken entry http://wiki.apache.org/james/SmartOrSecondaryHost, it is now back with full details.
Thanks Stefano. -- Steve Steve Brewin wrote: > > > Ivan Jouikov wrote: > > Read my responses below followed by >>>> > > Responses embedded in the conventional manner. > > > > -----Original Message----- > > From: Steve Brewin [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, September 27, 2006 2:25 PM > > To: 'James Users List' > > Subject: RE: Question about fetchmail configuration - > > alllocal - Passwrod? > > huh? > > > > Ivan > > > > If you want a conventional backup server I would recommend deploying > > multiple instances of James in a conventional manner using MX record > > priorities to route traffic between the instances as > > specified by the RFCs. > > > > >>>> Yeah that's exactly what I did. But if the main server > > goes down, and > > all the mail is stored on the secondary server, and then the > > main server > > comes back up - how do the users get their mail from > > secondary server? This > > is what I need the fetchmail for. > > Well http://wiki.apache.org/james/SmartOrSecondaryHost should > explain it, but the entry seems a little broken. Basically, > two (or more) mail servers are configured using MX records in > DNS with the primary server given higher priority than the > the secondary server(s). The secondary server is configured > to relay all mail to the primary server, no mail is delivered > locally. When the primary server is down, mail is delivered > to the secondary server which attempts to deliver it to the > primary server. Of course this fails while the primary server > is down, so the secondary server queues the mail until the > primary server comes back up, at which point the secondary > server starts delivering queued mail to the primary server. > > Other than the configuration of the processor chain of the > secondary server, none of this is James specific. It uses > standard DNS and SMTP mechanisms. There are cooler solutions, > such as the one posted by Norman Maurer in this thread. A > quick Google will find others. > > The good ones are a layer or more down than relying on the > POP3 and IMAP protocols used by fetchmail. As each layer > introduces another potential point of failure I would > recommend using a lower layer solution than the your wished > for fetchmail solution. > > > > Fetchmail fetches mail already successfully delivered to a > > mail server using > > supported client protocols such as POP3 and IMAP and injects > > into the James > > mail server spool. It is used when conventional RFC mandated > > solutions are > > not an option, such as an ISP not supporting SMTP > > connections. As it relies > > on mail being successfully delivered to the mail server, it > > isn't really a > > backup solution. > > > > >>>> Fetchmail isn't a backup solution? What's the > "conventional RFC > > mandated solutions"? I thought Fetchmail was THE backup solution? > > See above. Fetchmail was never intended for this. If there > anywhere in the documentation which suggests it is, please > raise a JIRA issue to have us resolve it. > > > Maybe I misunderstand your intentions? > > > > >>>> Maybe >>I<< misunderstand how mail fail-over is done? > > It seems so. > > > Regarding the alllocal passwords question, you should have > > read on in the > > page, see > > http://james.apache.org/server/2.2.0/fetchmail_configuration.h > > tml#fetchmail% > > 20Caveats. > > > > >>>> I did read this and I didn't find any "potential > > solutions". It simply > > says "currently all user accounts must have the same > > password," which is the > > most ridiculous thing I've ever heard. Why even implement > > this feature if > > it can't be used? > > It can be used. This is how I received your email :) > > > > > Both the problem and a potential solution are discussed. None the > > less, some ISPs do support a one domain, one password model, > > and in these > > circumstances allocal works just fine. > > > > Cheers > > > > -- Steve > > > > Ivan Jouikov [mailto:[EMAIL PROTECTED] wrote: > > > Ok I want to set up a backup mail server, and I want my main > > > server to fetch > > > any mail that goes to it. > > > > > > > > > > > > I’ll have both servers connected to the same DB with my user > > > accounts. In > > > fetchmail configuration there’s an option to use “alllocal” > > > for all local > > > accounts, which’s perfect for me. > > > > > > > > > > > > However, that section specifies a “password” field. What > > > exactly is that > > > field? Are all my accounts supposed to have the same > > > password? Or how does > > > this work? > > > > > > > > > > > > Besides, all passwords are stored as hash, so how is this > > > fetching possible? > > > > > > > > > > > > > > > > > > ……… I just read this: HYPERLINK > > > "http://james.apache.org/server/fetchmail_configuration_2_2.ht > > ml#alllocal"ht > > > tp://james.apache.org/server/fetchmail_configuration_2_2.html#alllocal > > > > > > > > So all accounts must have the same password, huh? Not very > > secure, why even > > implement this sort of thing? > > > > > > Does anybody have a setup with a backup mail server? How do > > you do it? > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > -- > > No virus found in this incoming message. > > Checked by AVG Free Edition. > > Version: 7.1.405 / Virus Database: 268.12.9/457 - Release > > Date: 9/26/2006 > > > > > > -- > > No virus found in this outgoing message. > > Checked by AVG Free Edition. > > Version: 7.1.405 / Virus Database: 268.12.9/457 - Release > > Date: 9/26/2006 > > > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
