Re: Some minor mail problems w/ Debian 2.2
Glyn Millington wrote: > On Sun, Oct 08, 2000 at 01:29:38PM +0400, thus spake Rino Mardo: > > > > hmm, fetchmail uses ETRN and not SMTP (port 25). debian 2.2 with exim > > works > > > > fine out of the box > > > > so why compound the problem? what is it your trying to accomplish? > > > > yes by default SMTP uses port 25. um, what's the problem anyway? > > Well there appear to be two problems! One is answered here > > #man fetchmail . > >"fetches mail from remote mailservers and forwards it to >your local (client) machine's delivery system. > >The fetchmail program can gather mail from servers sup >porting any of the common mail-retrieval protocols: POP2, >POP3, IMAP2bis, IMAP4, and IMAPrev1. It can also use the >ESMTP ETRN extension. (The RFCs describing all these pro >tocols are listed at the end of this manual page.) > >While fetchmail is primarily intended to be used over on- >demand TCP/IP links (such as SLIP or PPP connections), it >may also be useful as a message transfer agent for sites >which refuse for security reasons to permit (sender-initi >ated) SMTP transactions with sendmail. > >As each message is retrieved fetchmail normally delivers >it via SMTP to port 25 on the machine it is running on >(localhost), just as though it were being passed in over a >normal TCP/IP link. The mail will then be delivered >locally via your system's MDA (Mail Delivery Agent, usu >ally sendmail(8) but your system may use a different one >such as smail, mmdf, exim, or qmail). All the delivery- >control mechanisms (such as .forward files) normally >available through your system MDA and local delivery >agents will therefore work. > > The other problem is with the question - what is he trying to > acheive?? > > A bit like life really.. > > Peace! > > Glyn M > > -- >** >* "The soul is greater than the hum of its parts. " * >* Douglas Hoftstatder* >** > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < /dev/null Well, sorry folks, for being tardy on getting back with you. I found out the hard way that the Debian Install Guide wasn't kidding about /etc (among other things) being pretty much the property of dselect/apt/dpkg, etc. I had been farting around w/ exim, sendmail, masqmail, postfix, etc., and noticed that when I had masqmail installed, there were a _lot_ of files in /etc/ and /var/ that belonged to postfix and exim, even when they weren't installed. Well, I'll just rm those suckers. Whoops. Not a good idea. I later reinstalled postfix, and debconf errored out, cause those files weren't there. Same w/ exim. Well, rather than dink around trying to figure out what package _did_ install those files, since the MTA they went to obviously didn't, and since I didn't have a lot of time and effort sunk into my system yet, I opted to take another tour thru the lovely Debian installation program ;). Except I forgot that I actually had some useful stuff on my /home partition, and wiped it. :( So I am pretty much lost my whole archive of messages from all the mailing lists I follow. Talk about getting your fingers rapped! Ouch!! Well, now that I have my mail kinda sorta operational again, using Communicator, here is some answers to some of the issues/questions you kind folks have asked: I used to use sendmail plus a script called install-sendmail to set up sendmail & fetchmail, to retrieve my mail from Yahoo!, and send new mail w/ the headers written properly as being from [EMAIL PROTECTED] (Netscape by itself, even w/ '[EMAIL PROTECTED]' in the From: field in Preferences, would pop up '[EMAIL PROTECTED]' in one of the mail fields, which would cause someone's spam filter on the SuSE list to kick in, and some other people just plain got irate. So I used the script, sendmail, and fetchmail instead. Quick, simple, painless). Unfortunately, the Debian install of sendmail doesn't seem to jive w/ the install-sendmail script, so that rules out sendmail, as I am _not_ masochistic enough to want to configure that critter otherwise. Exim would work fine, I guess, but I was initially having a bit of trouble (I guess I still am) figuring out _exactly_ what I need to change where, for my situation: essentially a home dialup system, w/ a local username different from the username on my mail account. Postfix does seem to have a fair bit of documentation that addresses that specifically, so I'll probably pursue that next. The problem I think I had w/ fetchmail not being able to deliver to the localhost smtp port was w/ masqmail, not exim. Masqmail is the other finalist fo
Re: Some minor mail problems w/ Debian 2.2
On Sun, Oct 08, 2000 at 01:29:38PM +0400, thus spake Rino Mardo: > > > hmm, fetchmail uses ETRN and not SMTP (port 25). debian 2.2 with exim > works > > > fine out of the box > > > so why compound the problem? what is it your trying to accomplish? > > yes by default SMTP uses port 25. um, what's the problem anyway? Well there appear to be two problems! One is answered here #man fetchmail . "fetches mail from remote mailservers and forwards it to your local (client) machine's delivery system. The fetchmail program can gather mail from servers sup porting any of the common mail-retrieval protocols: POP2, POP3, IMAP2bis, IMAP4, and IMAPrev1. It can also use the ESMTP ETRN extension. (The RFCs describing all these pro tocols are listed at the end of this manual page.) While fetchmail is primarily intended to be used over on- demand TCP/IP links (such as SLIP or PPP connections), it may also be useful as a message transfer agent for sites which refuse for security reasons to permit (sender-initi ated) SMTP transactions with sendmail. As each message is retrieved fetchmail normally delivers it via SMTP to port 25 on the machine it is running on (localhost), just as though it were being passed in over a normal TCP/IP link. The mail will then be delivered locally via your system's MDA (Mail Delivery Agent, usu ally sendmail(8) but your system may use a different one such as smail, mmdf, exim, or qmail). All the delivery- control mechanisms (such as .forward files) normally available through your system MDA and local delivery agents will therefore work. The other problem is with the question - what is he trying to acheive?? A bit like life really.. Peace! Glyn M -- ** * "The soul is greater than the hum of its parts. " * * Douglas Hoftstatder* **
Re: Some minor mail problems w/ Debian 2.2
> > hmm, fetchmail uses ETRN and not SMTP (port 25). debian 2.2 with exim works > > fine out of the box > > so why compound the problem? what is it your trying to accomplish? > > Huh? > > > fetchmail: forwarding to localhost > fetchmail: SMTP> MAIL > FROM:<[EMAIL PROTECTED]> SIZE=2891 > fetchmail: SMTP< 250 <[EMAIL PROTECTED]> > is syntactically correct > fetchmail: SMTP> RCPT TO:<[EMAIL PROTECTED]> > fetchmail: SMTP< 250 <[EMAIL PROTECTED]> is syntactically correct > fetchmail: SMTP> DATA > fetchmail: SMTP< 354 Enter message, ending with "." on a line by itself > > > Fetchmail doesn't *have* to use SMTP for delivery, but I believe that is > the default. > yes by default SMTP uses port 25. um, what's the problem anyway?
Re: Some minor mail problems w/ Debian 2.2
On Sun, Oct 08, 2000 at 10:59:46AM +0400, Rino Mardo wrote: > > > > 2) I have exim installed currently. I tried sendmail, as my previous > > setup had been sendmail + install-sendmail (a perl setup script), which > > had been pretty painless, and had gotten everything delivered w/ the > > right addresses and whatnot, plus setup fetchmail easily. I tried doing > > the same setup on Debian, and it doesn't seem to get along real well w/ > > the install-sendmail script. Since I'm not masochistic enought to want > > to edit sendmail for my simple home setup, I was looking towards > > masqmail, but I need to know what I need to do to get it to accept mails > > >from fetchmail. I read thru the docs, but something wasn't working > > right, because fetchmail couldn't get a response on port 25. > > > > hmm, fetchmail uses ETRN and not SMTP (port 25). debian 2.2 with exim works > fine out of the box > so why compound the problem? what is it your trying to accomplish? Huh? fetchmail: forwarding to localhost fetchmail: SMTP> MAIL FROM:<[EMAIL PROTECTED]> SIZE=2891 fetchmail: SMTP< 250 <[EMAIL PROTECTED]> is syntactically correct fetchmail: SMTP> RCPT TO:<[EMAIL PROTECTED]> fetchmail: SMTP< 250 <[EMAIL PROTECTED]> is syntactically correct fetchmail: SMTP> DATA fetchmail: SMTP< 354 Enter message, ending with "." on a line by itself Fetchmail doesn't *have* to use SMTP for delivery, but I believe that is the default. -- /bin/sh ~/.signature: Command not found
Re: Some minor mail problems w/ Debian 2.2
> > 2) I have exim installed currently. I tried sendmail, as my previous > setup had been sendmail + install-sendmail (a perl setup script), which > had been pretty painless, and had gotten everything delivered w/ the > right addresses and whatnot, plus setup fetchmail easily. I tried doing > the same setup on Debian, and it doesn't seem to get along real well w/ > the install-sendmail script. Since I'm not masochistic enought to want > to edit sendmail for my simple home setup, I was looking towards > masqmail, but I need to know what I need to do to get it to accept mails > >from fetchmail. I read thru the docs, but something wasn't working > right, because fetchmail couldn't get a response on port 25. > hmm, fetchmail uses ETRN and not SMTP (port 25). debian 2.2 with exim works fine out of the box so why compound the problem? what is it your trying to accomplish?
Re: Some minor mail problems w/ Debian 2.2
Monte Milanuk wrote: > > Hello all, > > I've recently started using Debian 2.2, and I'm having a few weird mail > issues popping up. If anyone could provide some assistance, or nudge me > in the direction of some specific spot in the documentation, I'd > appreciate it greatly. > > 1) Added the sources for the online repositories to > /etc/apt/sources.list, did the apt-get upgrade thing, and am happily > using Netscape 4.75 -- w/ one exception. When I enter the information > for the pop/smtp server that I receive/send mail from, I cannot get any > new mail. When I click on the 'Get Messages' icon, it(Netscape) tells > me that I have no new messages. Like heck I don't! At the time I had > something like 200+ messages on my Yahoo! account. I've set this up in > the past on other systems (Mandrake, SuSE, RedHat), and I'd be > interested on why it doesn't seem to be functional on Debian. 200+ messages and 200+ NEW messages are very different. netscape by default wont download read mail. > from fetchmail. I read thru the docs, but something wasn't working > right, because fetchmail couldn't get a response on port 25. can you telnet to your ip/localhost on port 25 ? maybe exim is not runinning..i prefer sendmail for my systems just cuz i know it better then i know the others. > 3) After setting up fetchmail, and running it, I seem to be getting a > bunch of mails (so far over a dozen) which show up in Netscape as having > no title, being from [EMAIL PROTECTED] (me), and the header is displayed > as part of the message. As such, the Netscape filters don't move them > to the appropriate folders correctly. What could be causing this? possible it has something to do with the mail server and how it gives out mail. i have never used any of the free web based emailers(or free emailers in general) but my experience with netscape on almost countless accounts on "real" servers i have never experienced this. nate -- ::: ICQ: 75132336 http://www.aphroland.org/ http://www.linuxpowered.net/ [EMAIL PROTECTED]
Some minor mail problems w/ Debian 2.2
Hello all, I've recently started using Debian 2.2, and I'm having a few weird mail issues popping up. If anyone could provide some assistance, or nudge me in the direction of some specific spot in the documentation, I'd appreciate it greatly. 1) Added the sources for the online repositories to /etc/apt/sources.list, did the apt-get upgrade thing, and am happily using Netscape 4.75 -- w/ one exception. When I enter the information for the pop/smtp server that I receive/send mail from, I cannot get any new mail. When I click on the 'Get Messages' icon, it(Netscape) tells me that I have no new messages. Like heck I don't! At the time I had something like 200+ messages on my Yahoo! account. I've set this up in the past on other systems (Mandrake, SuSE, RedHat), and I'd be interested on why it doesn't seem to be functional on Debian. 2) I have exim installed currently. I tried sendmail, as my previous setup had been sendmail + install-sendmail (a perl setup script), which had been pretty painless, and had gotten everything delivered w/ the right addresses and whatnot, plus setup fetchmail easily. I tried doing the same setup on Debian, and it doesn't seem to get along real well w/ the install-sendmail script. Since I'm not masochistic enought to want to edit sendmail for my simple home setup, I was looking towards masqmail, but I need to know what I need to do to get it to accept mails from fetchmail. I read thru the docs, but something wasn't working right, because fetchmail couldn't get a response on port 25. 3) After setting up fetchmail, and running it, I seem to be getting a bunch of mails (so far over a dozen) which show up in Netscape as having no title, being from [EMAIL PROTECTED] (me), and the header is displayed as part of the message. As such, the Netscape filters don't move them to the appropriate folders correctly. What could be causing this? Thanks for your time, and any help is greatly appreciated, Monte _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
