It seems that with every new release, I have to get by one problem with a 'simple' application, before I can go on to explore the new functionality and toys. Today, it's fetchmail that's got me bugged. I'm using the same .fetchmailrc that worked so well in 6.4 and 7.1, yet for every mail retrieve attempt, I'm getting a series of messages resulting in a '250 2.0.0 reset state'. Here's an example: fetchmail: POP3> RETR 22 fetchmail: POP3< +OK 27806 octets reading message 22 of 24 (27806 octets) fetchmail: SMTP> MAIL FROM:<list-bounce@mailer.remote.arrl.org> SIZE=27806 fetchmail: SMTP< 451 4.1.8 <list-bounce@mailer.remote.arrl.org>... Domain of sender address list-bounce@mailer.remote.arrl.org does not resolve fetchmail: SMTP> RSET fetchmail: SMTP< 250 2.0.0 Reset state fetchmail: SMTP error: 250 2.0.0 Reset state .......................... not flushed Name resolution is working. I can 'nslookup' or 'dig' any of the sender domains successfully, so I don't understand the reason for the 451. Can anyone point me in the right direction? -- Rick Green
Well, I got it working. It involved playing with the options in /etc/rc.config.d/sendmail.rc.config. I'm not sure now what optionit was that made the difference, since I've changed them all. Somewhere in the middle of it all, it occurred to me to restart sendmail, and then I finally saw a difference in behaviour! Silly me, I was assuming that SuSEconfig was smart enough to restart services after changing the config files! Now that I am online, and I can send and receive e-mail, I'll promote this box to my main workstation. And get working on some of the new toys, like a CD-RW, LS-120, a sound card, and stateful iptables! Rick Green
participants (1)
-
Rick Green