On 6/21/05, E. Falk <[EMAIL PROTECTED]> wrote: > Jon Dossey wrote: > > (moved to bottom quote for you) > > > > I think I know the document you're referring to... > > http://wiki.apache.org/spamassassin/RemoteImapFolder?highlight=%28imap%2 > > 9 > > > > My problem is I don't like my MX (sitting in DMZ's), to connect back to > > the Exchange server (private network) via IMAP. > > > > My ideal solution would be to find a way to push the e-mail to SA, > > instead > > of letting them reach back inside my network to pull them out. > > > > > > Possibly FTP or SCP to a specific folder on the mail exchangers, and a > > cron job to check for anything, sa-learn it, and then rm it. > > > > > > .jon > > I see your problem. SCP is a very nice solution, since you can use keys > rather than passwords and push just as easily as pull. I use a similar > idea for pulling logs off the MX onto a Windows box with a tape backup. > > The only trick would be automating the export. It looks like a few > options have been posted to the list already... one other would be to > run perl on one of your machines (even your Exchange box, possibly) > inside the network to fetch the messages from the public folder and > create a message file (or files). > > From there, schedule a task to scp and remove the files and have a cron > job on your MX process them periodically as you said. > > Evan >
If your MX already connects back to the exchange server via smtp/25 then what difference does imap/143 make? Simply ACL the access to only your MXs IPs and do it the easy way with shared folders and IMAP access. Ben -- "The Edge ... there is no honest way to explain it because the only people who really know where it is are the ones who have gone over." Hunter S. Thompson (1939-2005)
