I agree - Thank you Whit for your post. This was one link I found that
covered SPF at a high level: http://www.opensp...
Really, my impression is that right now there is no massively deployed
standard way to address this issue. You can mimic IP addresses, email
addresses and even mac addresses. Maybe, just maybe, you can really do
management of email received based on the combination of them, along
with traced routes, etc, but just think about what a pain that would be
for all of us as email clients. The days of having a static ip address
are long gone, people are tired of registering online for everything
under the sun, etc.
I don't have a solution... sorry for that.. but I do want to find out
if someone else has one.
> Good work man! This will be helpful to all of us.
> On 10/24/07, whitneymcn <[address removed]> wrote:
>> Yeah, it'll be interesting to see what Meetup does...though as I note
>> below I think that we might not need them to do anything at all. :)
>> Based on the message that you received it looks like Meetup *does* do
>> SPF checks on incoming mail to the list: because the spammer's message
>> spoofing your email address failed the check for gmail.com, the message
>> wasn't delivered to the list. This is an official Good Thing.
>> My earlier message got through because it turns out that I've been a
>> lameass slacker and forgot to set up an SPF record for absono.us:
>> without a published statement regarding what servers are allowed to send
>> for the domain, Meetup apparently errs on the side of generosity and
>> allows all messages through. [Can someone from Meetup confirm that I'm
>> correct in this analysis, by the way?]
>> The same applies to Dean -- not the "lameass slacker" part, of course,
>> but the part about his domain not having an SPF record set up. No SPF
>> record, no way for Meetup to determine whether a given email is actually
>> coming from you.
>> So here's my suggestion: if you're using one of the big email providers
>> (gmail, yahoo, what-have-you) you don't need to do anything at all. If
>> you're sending your mail from your own domain or a corporate domain, on
>> the other hand, see about getting an SPF record set up if you don't
>> already have one. It's not hard: Google "create SPF record" if this is
>> a new area for you, and (within reason) I'm happy to offer advice or
>> assistance for anyone who needs it.
>> Seems like this is a problem that we can (largely) address ourselves, no
>> Meetup intervention required. I'll have my SPF record in place by this
>> evening. :)
>> W.B. McNamara
>> [address removed]
>> Ilya Z wrote:
>>> Yea - that's the reality of email. Curious how will meetup address this?
>>> For the past 30 minutes all my emails (even [address removed]
>>> <mailto:[address removed]>) were getting rejected. Seems they took
>>> their email servers down (due to spam issue?)
>>> All emails bounced with:
>>> Technical details of permanent failure:
>>> PERM_FAILURE: SMTP Error (state 13):[masked]
>>> <wa-out-1112.google.com[[masked] <http://209.85.146...;:
>>> Client host rejected: Access denied
>> Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
>> This message was sent by whitneymcn ([address removed]) from NY Tech Meetup.
>> To learn more about whitneymcn, visit his/her member profile: http://newtech.me...
>> To unsubscribe or to update your mailing list settings, click here: http://www.meetup...
>> Meetup.com Customer Service: [address removed]
>> 632 Broadway New York NY 10012 USA
> Please Note: If you hit "REPLY", your message will be sent to everyone on this mailing list ([address removed])
> This message was sent by Hank ([address removed]) from NY Tech Meetup.
> To learn more about Hank, visit his/her member profile: http://newtech.me...
> To unsubscribe or to update your mailing list settings, click here: http://www.meetup...
> Meetup.com Customer Service: [address removed]
> 632 Broadway New York NY 10012 USA