| TIP: Click on subject to list as thread! | ANSI |
| echo: | |
|---|---|
| to: | |
| from: | |
| date: | |
| subject: | Direct Netmail |
mark lewis wrote in a message to Thom LaCosta: TL> One could use gmail, which is not blocked, one could, as you have, TL> ask how to do it. ml> the robot does gmail? that's a new one on me ;) The robot accepts email....it really doesn't care whether it;s gmail, markmail or tlchostmail. Because the email arrives via my server, it suffers for being blocked if the sending domain/ip address is in one of the many block lists I use. ml> can you say if the robot has figured out how to determine the ml> proper name for *emailed* rules updates that contain the rules in ml> the message instead of attached to the message?? No, I can't. I suppose I could run some tests on one of my echoes.... I use echomod to submit updates, and as far as I know, echomod produces rules update messages that the robot can process. I'll run a few and post the rules message here for your information. The tests may not be conclusive, since none of my echonames are very long. The 8.3 file name contraint may be the real bug-a-boo....and there doesn' seem to be anyway around that. ml> i know there's also rules entries for echos in which the moderator ml> left a long time ago and new moderators, while having update their ml> rules in the echo have not sent rules to the robot... so those ml> really old rules files are still in place instead of having been ml> purged as well... It's the old Damned if you do, Damned if you don't. I once removed rules files that were older than 6 months(the logic being that the echolistings were good for 6 months) There was a hue and cry from moderators that their rules had been purged. I attempted to explain the logic, and suggested that an update of the echolisting might be the logical time to update the rules. The reaction was as if I had pooped in Mom's oatmeal, urinated on the flag and substituted lemons for apples in the pie. So, I finally stopped trying to corral cats and bbaby sit prima donna who were too stubborn work with me. The only thing sillier than that were the folks that couldn;t remember to update their listings every six months...and either could not or would not understand that sending in an update every month might prevent teir listings from expiring. I even remember heated discussions about the --- being the eom marker. That's what the Echolist recognizes...and no amount of whining, Fidonet standards and other stuff changes it. I think maybe I'll simply delete all the rules files and see who resubmits....and if they use ---, or any line that contains that, as part of the rules file text...the rules will be zero length. cya, thom http://www.echolist.net/ --- GEcho 1.20/Pro* Origin: Home of The Other Robot (1:261/1352) SEEN-BY: 10/1 11/200 331 14/400 34/999 90/1 120/228 123/500 128/2 187 140/1 SEEN-BY: 222/2 226/0 236/150 249/303 250/306 261/20 38 100 1381 1404 1406 1418 SEEN-BY: 266/1413 280/1027 320/119 393/68 396/45 633/260 267 285 690/682 SEEN-BY: 712/848 800/432 801/161 189 2222/700 2320/100 105 200 5030/1256 @PATH: 261/1352 123/500 261/38 633/260 267 |
|
| SOURCE: echomail via fidonet.ozzmosis.com | |
Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.