Re: smtp pull
On 12 January, 2005, at 14:54 (-0500) Kris Maglione <[EMAIL PROTECTED]> wrote: > > >Maybe fetchmail is what you need? That is what most of dialup users use > >when they run their own MTA servers. > > > > > > > Fetchmail uses POP. It'll do more than just POP. From the man page: AUTO Tries IMAP, POP3, and POP2 (skipping any of these for which support has not been compiled in). POP2 Post Office Protocol 2 POP3 Post Office Protocol 3 APOP Use POP3 with old-fashioned MD5-challenge authentication. RPOP Use POP3 with RPOP authentication. KPOP Use POP3 with Kerberos V4 authentication on port 1109. SDPS Use POP3 with Demon Internet's SDPS extensions. IMAP IMAP2bis, IMAP4, or IMAP4rev1 (fetchmail autodetects their capabilities). ETRN Use the ESMTP ETRN option. ODMR Use the the On-Demand Mail Relay ESMTP profile. It seems like the ideal solution for the original poster's needs. It can pull mail down from the external machine, using any of the above protocols, and will feed the mail to the internal machine's SMTP server. Brian Clapper, http://www.clapper.org/bmc/ ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: smtp pull
Maybe fetchmail is what you need? That is what most of dialup users use when they run their own MTA servers. Fetchmail uses POP. Obviously I can make smtp1 drop the mail in a mailbox on smtp1 and then get smtp2 to imap or pop the mail out however I'm looking for something that's fast and pop doesn't really excite me.. Maybe rsync or scp? If you use /var/mail, maybe do: scp /var/mail/ ./ then: formail < -s signature.asc Description: OpenPGP digital signature
re: smtp pull
it was said: Hi, Looking for some thoughts on the following scenario. firewall smtp2 | | smtp1 smtp1 is on the DMZ. So smtp1 is the first point of call for incoming mail. Mail ultimately has to end up on smtp2 however I do not want smtp1 to simply forward the mail to smtp2 as I'll have to explicitly allow the setup of port 25 through the firewall to smtp2. I would like smtp2 to connect to smtp1 and pull back the mail so that it's smtp2 that initiating an outgoing connection to smtp1. Is there any smtp type approach I can use? etrn? stheg __ Do you Yahoo!? All your favorites on one personal page Try My Yahoo! http://my.yahoo.com ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: smtp pull
Andrew Thomson wrote: [ ... ] smtp1 is on the DMZ. So smtp1 is the first point of call for incoming mail. Mail ultimately has to end up on smtp2 however I do not want smtp1 to simply forward the mail to smtp2 as I'll have to explicitly allow the setup of port 25 through the firewall to smtp2. I would like smtp2 to connect to smtp1 and pull back the mail so that it's smtp2 that initiating an outgoing connection to smtp1. Is there any smtp type approach I can use? You can configure smtp1 as a standard backup MX for smtp2, and use the ETRN command from smtp2 to convince smtp1 to process it's queue of messages. On the other hand, unless you configure both sides to use a non-standard port, smtp1 is still going to open new connections via port 25 to smtp2. That's what the SMTP protocol does, and your firewall can either permit the mail or it can block the mail. -- -Chuck ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
RE: smtp pull
Someone broke the silence: > Hi, > > Looking for some thoughts on the following scenario. > > firewall smtp2 >> >> > smtp1 > > smtp1 is on the DMZ. So smtp1 is the first point of call for incoming > mail. Mail ultimately has to end up on smtp2 however I do not > want smtp1 > to simply forward the mail to smtp2 as I'll have to > explicitly allow the > setup of port 25 through the firewall to smtp2. > > I would like smtp2 to connect to smtp1 and pull back the mail so that > it's smtp2 that initiating an outgoing connection to smtp1. Maybe fetchmail is what you need? That is what most of dialup users use when they run their own MTA servers. Chris > > Is there any smtp type approach I can use? > > Obviously I can make smtp1 drop the mail in a mailbox on > smtp1 and then > get smtp2 to imap or pop the mail out however I'm looking for > something that's fast and pop doesn't really excite me.. > > Anyone have any other thoughts? > > Thanks, > > ajt. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
smtp pull
Hi, Looking for some thoughts on the following scenario. firewall smtp2 | | smtp1 smtp1 is on the DMZ. So smtp1 is the first point of call for incoming mail. Mail ultimately has to end up on smtp2 however I do not want smtp1 to simply forward the mail to smtp2 as I'll have to explicitly allow the setup of port 25 through the firewall to smtp2. I would like smtp2 to connect to smtp1 and pull back the mail so that it's smtp2 that initiating an outgoing connection to smtp1. Is there any smtp type approach I can use? Obviously I can make smtp1 drop the mail in a mailbox on smtp1 and then get smtp2 to imap or pop the mail out however I'm looking for something that's fast and pop doesn't really excite me.. Anyone have any other thoughts? Thanks, ajt. -- Andrew Thomson <[EMAIL PROTECTED]> ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"