Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Content-Type: text/plain; charset=us-ascii mark_glassberg at valley.net writes: > But the problem is that the mail server knows my machine when I use telnet, but > not when I use sendmail. Those are two entirely different modes of operation. When you telnet to port 25, the remote sendmail sees you as the direct end-user sending the message, whereas when your sendmail relays your message to the remote sendmail, the remote sendmail sees your sendmail as a middle-man. While such relaying is part of the basic design of sendmail, the fact remains that spammers have taken unscrupulous advantage of it for years, and as a result it's now considered bad practice to allow relaying in any but the most controlled and restricted fashion. The normal approach would be to ask your ISP to modify their server's setup to allow relaying from your address. I wouldn't expect much cooperation from them on this, though. I had a shell account I could use on my external mailserver, so I was able to set up an ssh tunnel to pass messages to the remote sendmail. Without a shell account, though, this approach wouldn't work. - -- John Abreau / Executive Director, Boston Linux & Unix Email jabr at blu.org / WWW http://www.abreau.net / PGP-Key-ID 0xD5C7B5D9 PGP-Key-Fingerprint 72 FB 39 4F 3C 3B D6 5B E0 C8 5A 6E F1 2C BE 99 -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.7 (GNU/Linux) Comment: Exmh version 2.5 07/13/2001 iQCVAwUBPgJ+C1V9A5rVx7XZAQLO0wQAoLUf+YIEOfVjA61+oqKrtk5R0omqRrqf rEh6rfbLepL70KcgoM2p3Z4ooLYYx6sHDBelYxQkdGnvBxdf01pmncvd354FA+ex FbfO/PdBFUNKhszGCyINVt84VOZKUhgI3AvB0GfEVhQzLqZJedk82BaeNFny2K0D xpQmNfb3Apk= =Fr0Q -----END PGP SIGNATURE-----
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |