Re: Sendmail Relay Problems
Have you checked the reverse mapping for your IPs? Cheers, Marcel On 15 Aug 2001, at 16:49, Gene Grimm wrote: If anyone can point me in the right direction, it would be appreciated. We recently changed IP addresses in one of our facilities because of changes in upline providers. Even after adding the new IP addresses to the sendmail configurations (both with Linuxconf and manually) we get an error that we cannot relay from the new addresses (in the remote facility). Does anyone know what I may be missing? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sendmail Relay Problems
On Wed, Aug 15, 2001 at 04:49:50PM -0400, Gene Grimm wrote: If anyone can point me in the right direction, it would be appreciated. We recently changed IP addresses in one of our facilities because of changes in upline providers. Even after adding the new IP addresses to the sendmail configurations (both with Linuxconf and manually) we get an error that we cannot relay from the new addresses (in the remote facility). Does anyone know what I may be missing? Have you checked /etc/mail/access? Remember to regenerate /etc/mail/access.db after editing /etc/mail/access. -- Michael Wood [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sendmail Relay Problems
If you are using the latest and greatest, look for a line in your sendmail.cf for DaemonPortOptions This tells sendmail which IP addresses and ports it should run on. Make sure your configuration did not set this for. :-) Larry Sorry Michael, for send just to you the last time. :-( At 04:49 PM 8/15/2001 -0400, Gene Grimm wrote: If anyone can point me in the right direction, it would be appreciated. We recently changed IP addresses in one of our facilities because of changes in upline providers. Even after adding the new IP addresses to the sendmail configurations (both with Linuxconf and manually) we get an error that we cannot relay from the new addresses (in the remote facility). Does anyone know what I may be missing? -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sendmail Relay Problems
This network has been driving me nuts for weeks and this is only making it worse. Here are the extracts from the maillog file coming from my workstation. It makes no difference if I use the HELO protocol, and there is an PTR entry in the in-addr.arpa zone for this address block with my workstation host name/FQDN. I'm not sure how to test reverse IP lookup through Linux just yet, but our DNS is NT-based. The DaemonPortsOption line is commented out in the sendmail.cf file. I regenerated the access.db file manually from the access text file which includes all IP address blocks and domain names we host in both facilities. sendmail[946]: NOQUEUE: Authentication-Warning: mail-pa-networksonline.com: [...] didn't use HELO protocol sendmail[946]: KAA00946: ruleset=check_rcpt, [EMAIL PROTECTED], relay=[...], reject=551 we do not relay sendmail[946]: KAA00946: [EMAIL PROTECTED], size=0, class=0, pri=0, nrcpts=0, proto=SMTP, relay=[...] sendmail[1059]: NOQUEUE: Authentication-Warning: mail-pa-nc.networksonline.com: [...] didn't use HELO protocol sendmail[1059]: KAA01059: ruleset=check_rcpt, [EMAIL PROTECTED], relay=[...], reject=551 we do not relay sendmail[1059]: KAA01059: [EMAIL PROTECTED], size=0, class=0, pri=0, nrcpts=0, proto=SMTP, relay=[...] sendmail[1273]: NOQUEUE: Authentication-Warning: mail-pa-nc.networksonline.com: [...] didn't use HELO protocol sendmail[1273]: KAA01273: ruleset=check_rcpt, [EMAIL PROTECTED], relay=[...], reject=551 we do not relay sendmail[1273]: KAA01273: ruleset=check_rcpt, [EMAIL PROTECTED], relay=[...], reject=551 we do not relay sendmail[1273]: KAA01273: [EMAIL PROTECTED], size=0, class=0, pri=0, nrcpts=0, proto=SMTP, relay=[...] sendmail[1398]: NOQUEUE: Authentication-Warning: mail-pa-nc.networksonline.com: [...] didn't use HELO protocol sendmail[1398]: LAA01398: ruleset=check_rcpt, [EMAIL PROTECTED], relay=[...], reject=551 we do not relay sendmail[1398]: LAA01398: [EMAIL PROTECTED], size=0, class=0, pri=0, nrcpts=0, proto=SMTP, relay=[...] sendmail[1526]: NOQUEUE: Authentication-Warning: mail-pa-nc.networksonline.com: [...] didn't use HELO protocol sendmail[1526]: LAA01526: ruleset=check_rcpt, [EMAIL PROTECTED], relay=[...], reject=551 we do not relay sendmail[1526]: LAA01526: [EMAIL PROTECTED], size=0, class=0, pri=0, nrcpts=0, proto=SMTP, relay=[...] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sendmail Relay Problems
Gene Grimm wrote: This network has been driving me nuts for weeks and this is only making it worse. Here are the extracts from the maillog file coming from my workstation. It makes no difference if I use the HELO protocol, and there is an PTR entry in the in-addr.arpa zone for this address block with my workstation host name/FQDN. I'm not sure how to test reverse IP lookup through Linux just yet, but our DNS is NT-based. type host ipaddress It should return a FQDN if the PTR entry exists and is working properly. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: Sendmail Relay Problems
Well, that does provide the FQDN of the machine locally, but not at the remote mail server. Guess it's time to check the DNS issues. - Original Message - This network has been driving me nuts for weeks and this is only making it worse. Here are the extracts from the maillog file coming from my workstation. It makes no difference if I use the HELO protocol, and there is an PTR entry in the in-addr.arpa zone for this address block with my workstation host name/FQDN. I'm not sure how to test reverse IP lookup through Linux just yet, but our DNS is NT-based. type host ipaddress It should return a FQDN if the PTR entry exists and is working properly. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
