Version 2.0 to 2.1 upgrade
Hi All I just updated from 2.0 to 2.1. Everything went smoothly except for the sendmail installation. Sendmail found my existing install and asked me whether I wanted to keep it or not, I said keep. Unfortunately there seem to be a few side effects with this. 1) sendmail.cf has been moved from /etc to /etc/mail, but the script /etc/init.d/sendmail checks for the existence if the /etc/sendmail.cf command before it executes anything. 2) I found that submitting mail from the Linux box worked but submitting it from a workstation did not, giving an error about relaying. The only way I could get round this was to add domain names for all my clients into the /etc/mail/relay-domains file. This seems to work, but it is a real drag. Thank God I did the upgrade over the weekend. Are there any better ways to address these problems? Am I the only one to have seen these problems? TIA --- | Simon Martin | By definition, all software is faulty. | | Project Manager | It is just a mere coincidence if it| | Isys | ever seems to work ;-)| --- mailto: [EMAIL PROTECTED] Powered by Debian Linux
Re: Version 2.0 to 2.1 upgrade
On Sun, 14 Mar 1999, Simon Martin wrote: 1) sendmail.cf has been moved from /etc to /etc/mail, but the script /etc/init.d/sendmail checks for the existence if the /etc/sendmail.cf command before it executes anything. There should be a file /etc/init.d/sendmail.dpkg-new -- you might want to replace the /etc/init.d/sendmail file with this one so that it looks in the right place. 2) I found that submitting mail from the Linux box worked but submitting it from a workstation did not, giving an error about relaying. The only way I could get round this was to add domain names for all my clients into the /etc/mail/relay-domains file. This seems to work, but it is a real drag. Thank God I did the upgrade over the weekend. This relaying protection is actually something that you definitely DO want. If you're running sendmail open to all relaying on the Internet, before long some spammer will discover it and happily steal your bandwidth and cpu to send their crap all over the Internet, possibly resulting in the blacklisting of your mailhost stopping you from mailing about 30% of the net. You should be able to use appropriate wildcards in the relay-domains file so you don't have to do it by host, but by IP ranges (172.16.*) or whole domains (*.example.com). Yes it's more of a pain than unrestricted access, but having your mailer exploited by spammers is more of a pain than anything (and many people will dislike you for it.) hope this helps, -thomas .. please forgive my abrupt ending hre - but my conection is xtrememleyyhiclmelyey BAD hiccuppy etc must sign off - EF D8 33 68 B3 E3 E9 D2 C1 3E 51 22 8A AA 7B 98 umbra (!)
RE: Version 2.0 to 2.1 upgrade
Thanks Thomas, Works like a dream and it even makes sense! -Original Message- From: thomas lakofski [mailto:[EMAIL PROTECTED] Sent: 14 March 1999 11:19 To: Simon Martin Cc: Debian-user list Subject: Re: Version 2.0 to 2.1 upgrade On Sun, 14 Mar 1999, Simon Martin wrote: 1) sendmail.cf has been moved from /etc to /etc/mail, but the script /etc/init.d/sendmail checks for the existence if the /etc/sendmail.cf command before it executes anything. There should be a file /etc/init.d/sendmail.dpkg-new -- you might want to replace the /etc/init.d/sendmail file with this one so that it looks in the right place. 2) I found that submitting mail from the Linux box worked but submitting it from a workstation did not, giving an error about relaying. The only way I could get round this was to add domain names for all my clients into the /etc/mail/relay-domains file. This seems to work, but it is a real drag. Thank God I did the upgrade over the weekend. This relaying protection is actually something that you definitely DO want. If you're running sendmail open to all relaying on the Internet, before long some spammer will discover it and happily steal your bandwidth and cpu to send their crap all over the Internet, possibly resulting in the blacklisting of your mailhost stopping you from mailing about 30% of the net. You should be able to use appropriate wildcards in the relay-domains file so you don't have to do it by host, but by IP ranges (172.16.*) or whole domains (*.example.com). Yes it's more of a pain than unrestricted access, but having your mailer exploited by spammers is more of a pain than anything (and many people will dislike you for it.) hope this helps, -thomas .. please forgive my abrupt ending hre - but my conection is xtrememleyyhiclmelyey BAD hiccuppy etc must sign off - EF D8 33 68 B3 E3 E9 D2 C1 3E 51 22 8A AA 7B 98 umbra (!) --- | Simon Martin | By definition, all software is faulty. | | Project Manager | It is just a mere coincidence if it| | Isys | ever seems to work ;-)| --- mailto: [EMAIL PROTECTED] Powered by Debian Linux
