Re: configuring fetchmail, exim and mutt for remote access
On Wed, 28 Feb 2007 17:21:33 -0500 Roberto C. Sanchez [EMAIL PROTECTED] wrote: On Wed, Feb 28, 2007 at 01:20:06PM -0800, Peter Easthope wrote: On Wed, Feb 28, 2007 at 03:48:09PM -0500, Roberto C. Sanchez wrote: [snip] fetchmail sends messages to port 25 via SMTP whereas mutt wants to read messages in /var/mail/peter. Isn't exim needed to send the port 25 stream into the spool file? I don't think so. I think fetchmail can be configured to deliver directly. If not, seting up for local delivery in exim is a simple dpkg-reconfigure away. Getmail can deliver directly. As I said, exim is probably overkill. Messages need to be sent also. Isn't exim needed to send messages to P via SMTP? Possibly. You can use ssmtp. For exim, however, you will need to wait for someone else on the list to help you out. I don't know a thing about it, as I use postfix on all my machines. Check out the (virtual) package 'mail-transport-agent' and you'll see lots and lots of MTA's (see the list of packages that provide 'm-t-a' and the list of those that conflict with it). Celejar -- ssuds.sourceforge.net - Home of Ssuds and Ssudg A Simple Sudoku Solver and Generator -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: configuring fetchmail, exim and mutt for remote access
On Wed, Feb 28, 2007 at 12:01:43PM -0800, Easthope wrote: Roberto Sanchez others, At Thu, 25 Jan 2007 12:45:38 -050, Roberto Sanchez said, Setup mutt on the machine and ssh in when you are travelling. It works as you outline. POP3 server, is on machine P. fetchmail, exim, mutt and ssh are on home machine, H. ssh is on mobile machine M. You can setup mutt on machine M and have it just pull messages directly from machine P via POP. If you always want most of your messages waiting there for you, then you can use fetchmail. I think that exim is not necessary for your needs. Also, thanks for explaining why the MAC address can not not identify H to the world. I wonder about streamlining even further. Ie., run exim and mutt, or other MUA, on M with M-exim communicating with H-exim by SMTP tunnelled in TLS. A message would travel thusly. SMTP POP3in TLS P = H == M-exim === M-MUA Any chance of this working? Any tips on configuring it before I waste too many hours ... or days? As I said, exim is probably overkill. You can do what you want with mutt+fetchmail. Regards, -Roberto -- Roberto C. Sanchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature
Re: configuring fetchmail, exim and mutt for remote access
On Wed, Feb 28, 2007 at 12:01:43PM -0800, Easthope wrote: Roberto Sanchez others, At Thu, 25 Jan 2007 12:45:38 -050, Roberto Sanchez said, Setup mutt on the machine and ssh in when you are travelling. It works as you outline. POP3 server, is on machine P. fetchmail, exim, mutt and ssh are on home machine, H. ssh is on mobile machine M. Also, thanks for explaining why the MAC address can not not identify H to the world. I wonder about streamlining even further. Ie., run exim and mutt, or other MUA, on M with M-exim communicating with H-exim by SMTP tunnelled in TLS. A message would travel thusly. SMTP POP3in TLS P = H == M-exim === M-MUA Any chance of this working? Any tips on configuring it before I waste too many hours ... or days? smtp is a push system. it has to go out and find the machine where you want to send mail. this doesn't really work with a laptop or other mobile situation as the destination keeps changing. I don't remember the exact situation you were in, but what you have going now is probably the most efficient one you could have. next step up for convenience would be to setup IMAP and/or webmail. A signature.asc Description: Digital signature
Re: configuring fetchmail, exim and mutt for remote access
On Wed, Feb 28, 2007 at 03:48:09PM -0500, Roberto C. Sanchez wrote: You can setup mutt on machine M and have it just pull messages directly from machine P via POP. Two factors against that. - P belongs to an ISP which refuses POP access from a machine not on his WAN. - M is inside a firewall which passes ssh but not POP. I think that exim is not necessary for your needs. fetchmail sends messages to port 25 via SMTP whereas mutt wants to read messages in /var/mail/peter. Isn't exim needed to send the port 25 stream into the spool file? As I said, exim is probably overkill. Messages need to be sent also. Isn't exim needed to send messages to P via SMTP? Thanks again, ... Peter E. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: configuring fetchmail, exim and mutt for remote access
On Wed, Feb 28, 2007 at 01:20:06PM -0800, Peter Easthope wrote: On Wed, Feb 28, 2007 at 03:48:09PM -0500, Roberto C. Sanchez wrote: You can setup mutt on machine M and have it just pull messages directly from machine P via POP. Two factors against that. - P belongs to an ISP which refuses POP access from a machine not on his WAN. Uggh. - M is inside a firewall which passes ssh but not POP. I see. Do you have ssh access to P? Were you planning on tunneling? If so, you can have fetchmail go over the tunnel. Alternatively, does the machine have IMAP access? I think that exim is not necessary for your needs. fetchmail sends messages to port 25 via SMTP whereas mutt wants to read messages in /var/mail/peter. Isn't exim needed to send the port 25 stream into the spool file? I don't think so. I think fetchmail can be configured to deliver directly. If not, seting up for local delivery in exim is a simple dpkg-reconfigure away. As I said, exim is probably overkill. Messages need to be sent also. Isn't exim needed to send messages to P via SMTP? Possibly. You can use ssmtp. For exim, however, you will need to wait for someone else on the list to help you out. I don't know a thing about it, as I use postfix on all my machines. Thanks again, ... Peter E. np, Regards, -Roberto -- Roberto C. Sanchez http://people.connexer.com/~roberto http://www.connexer.com signature.asc Description: Digital signature