Probably not. You can workaround it by satisfying the recipient's irrational
demands; eg, paying for hosting or relay from a static IP.
Inevitably, though, the "fix" is for said person to get a new mail provider
that isn't unreasonable.
> --
>
> You received this message because you are subscribed to the Google Groups "MOO Talk" group.
> To post to this group, send email to MOO-...@googlegroups.com.
> To unsubscribe from this group, send email to MOO-talk+u...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/MOO-talk?hl=en.
>
Hey, if they want to use a provider that intentionally discards legitimate
email behind their backs, they can:
1. switch to a provider that isn't lame
2. convince their provider to fix their servers
3. accept that they won't be getting all their emails
No getting around that choice. #2 is usually impractical, and presumably #3
isn't acceptable. That leaves #1.
These are two different problems. If you can, check the mail logs on the mail server ($network.maildrop) and see whether the mail was received from the MOO server and whether it was successfully sent out to the recipient's mail server.
--
Tristan B
TrekGames.net
Administrator and Maintainer
Contact information:
Skype: Tristanbussiere
MSN: tri...@acegamesonline.net
follow me on twitter
http://twitter.com/blindtrek/
E-mail: thebli...@gmail.com
or
email TrekGames.net support
trek...@gmail.com
AOL Instant Messenger: Theblinddj360
Klango ID:
Tristan
Connect to cosmos and join the fun. Point your MUD client to the following
address and port:
Address: TrekGames.net
Port: 1234
It depends on how your MOO sends the email. I'm not sure what anyone
else is using for sending mail from within their MOO world, but the
verb used in the MOO I run would just open a connection to the remote
mail host and immediately send all of the lines for the message to the
remote end. Technically that's violating some RFC somewhere, because
a mail client is supposed to wait for the initial "Hello" banner from
the server-side before the client starts sending anything. In my case
I changed the verb to wait for the header line, and only send the
message after that header had been seen.
That fixed the problem I was seeing, but I suspect we had our own home-
grown verb for sending emails, so I don't know what issues would come
up for other MOO sites.