Incoming from Jamieson Becker: > > As you have guessed, this actually does not also appear to be a postfix > bug at all. It appears that your upstream provider is having issues and > you don't have enough information to resolve it, short of helpful tech > support at your provider.
This (from my ISP): http://postfix.state-of-mind.de/patrick.koetter/smtpauth/smtp_auth_mailservers.html was suggested, but didn't help. However, mentioning POP before SMTP gave me a clue. I run fetchmail in a script run by my user crontab, and recently, I'd changed it to run every 10 min., where it was previously running every 5 min. Perhaps that's why this raised its ugly head in the first place. Question for you: does "/etc/init.d/postfix restart" do a "postfix reload"? I don't think so and think it should, perhaps testing whether /etc/postfix/sasl_password is newer than /etc/postfix/sasl_password.db first. I also noticed /etc/postfix/sasl_password.db didn't exist when I looked into this, so "postmap hash:/etc/postfix/sasl_passwd" hadn't been done. You might consider adding that based on the same test above. Still looking into it. Thanks Jamieson. -- Any technology distinguishable from magic is insufficiently advanced. (*) Please don't Cc: me. - - -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
