no ticket confirmation email, but card has been charged

[lessrules]

Is anyone else missing the email? It takes a couple of days for a credit card charge to appear for a lot of online banking customers. So maybe a lot of these stressed out people actually have tickets, but their confirmation email was simply rejected? (or in a spam folder if you have one)

Beforehand, I made sure that "burningman.com" was accepted (whitelisted) in my email, but no one mentioned that I would have to pre-set my email to accept (whitelist) email from "[email protected]"!

For the technically-minded, this the rejected email (from BM or ticket vendor) that I found in the mail server log file:

Jan 31 15:13:34 a postfix/smtpd[26287]: connect from unknown[74.85.131.58]
Jan 31 15:13:34 a postfix/smtpd[26287]: warning: 74.85.131.58: hostname res.tick-fw03.inetu.net verification failed: Name or service not known
Jan 31 15:13:36 a postfix/policyd-weight[5165]: weighted check: NOT_IN_SBL_XBL_SPAMHAUS=-1.5 NOT_IN_SPAMCOP=-1.5 NOT_IN_BL_NJABL=-1.5 CL_IP_NE_HELO=1.5 RESOLVED_IP_IS_NOT_HELO=1.5 (check from: .inetuhosted. - helo: .intic-stage-app1.inetuhosted. - helo-domain: .inetuhosted.) MAIL_SEEMS_FORGED=2.5; <client=74.85.131.58> <helo=intic-stage-app1.inetuhosted.net> <from=[email protected]> <to=[email protected]>; rate: 1
Jan 31 15:13:36 a postfix/policyd-weight[5165]: decided action=550 Mail appeared to be SPAM or forged. Ask your Mail/DNS-Administrator to correct HELO and DNS MX settings or to get removed from DNSBLs; MTA helo: intic-stage-app1.inetuhosted.net, MTA hostname: unknown[74.85.131.58] (helo/hostname mismatch); <client=74.85.131.58> <helo=intic-stage-app1.inetuhosted.net> <from=[email protected]> <to=[email protected]>; delay: 1s
Jan 31 15:13:36 a postfix/smtpd[26287]: NOQUEUE: reject: RCPT from unknown[74.85.131.58]: 550 5.7.1 <[email protected]>: Recipient address rejected: Mail appeared to be SPAM or forged. Ask your Mail/DNS-Administrator to correct HELO and DNS MX settings or to get removed from DNSBLs; MTA helo: intic-stage-app1.inetuhosted.net, MTA hostname: unknown[74.85.131.58] (helo/hostname mismatch); from=<[email protected]> to=<[email protected]> proto=SMTP helo=<intic-stage-app1.inetuhosted.net>
Jan 31 15:13:36 a postfix/smtpd[26287]: disconnect from unknown[74.85.131.58]

And this is the contents of the emails that were accepted 1 second later (from the CC company):

Tue, 31 Jan 2012 15:13:37 -0800 (PST) An authorization for $1.01 at BURNING MAN SAN FRANCISCO CA has been made
Tue, 31 Jan 2012 15:13:37 -0800 (PST) An authorization for $805.00 at BURNING MAN SAN FRANCISCO CA has been made

For the sake of the stressed, maybe you'd like to share with the rest of us if you did/didn't get the ticket confirmation email and what email provider you use? (gmail,yahoo,live,work_email,private_email, etc, etc)

-I did not get a ticket confirmation email, and I use a private email service.

[lemur]

no one mentioned that I would have to pre-set my email to accept (whitelist) email from "[email protected]"!

I AM SHOCKED, I TELL YOU.. SHOCKED!!!!!!!!!!!!!!!!

[lessrules]

I AM SHOCKED, I TELL YOU.. SHOCKED!!!!!!!!!!!!!!!!

[gyre]

It is routine for a certain number of emails to fail.
Fairly high number too.
Don't know why anyone would consider email reliable.

Part of it is called black holes in the net.

Some are fairly repeatable.
Last time I emailed Phil, the emails failed.

A friend has great trouble emailing me.
Most of my emails reach him.

[BBadger]

One tactic in some anti-spam systems is to reject suspicious email and wait for the sending mail server to resend it, as most will if they receive a server-unavailable response. It can take hours at a time to receive the resent email that way. Best thing is to check that you were charged and then just wait on it.

[lessrules]

no one mentioned that I would have to pre-set my email to accept (whitelist) email from "[email protected]"!

I caught myself in a contradiction. I believe that even if I had whitelisted "[email protected]" that the email would still have been rejected mostly because of the hostname mismatch.

[BBadger]

I wonder if the "may be forged" is a problem issue for some spam catchers?

Code: Select all

Received: from intic-stage-app1.inetuhosted.net (res.tick-fw03.inetu.net [74.85.131.58] (may be forged))

[whatup]

posted in ther other thread, but my card was only charged for $1.01? No other charges. I'm so confused!

[lemur]

some email servers are configured to not like receiving email from a different reverse DNS from what that host is claiming to be


how do we know that this is even related to burning man orders ticketing operation ?

it is a nice log, and all..

but correlation is not causation or soemthing liek that that youd see some pedantic dude on slashdot say


edit:

CONFIRMED.

THIS is from a 2011 ticket confirmation:

Code: Select all

Received: from in-utility1.inetu.net (in-utility1.inetu.net [209.235.244.40])
        by mx.google.com with SMTP id c4si638651vbz.19.2011.06.02.12.40.39;
        Thu, 02 Jun 2011 12:40:39 -0700 (PDT)
Received-SPF: pass (google.com: domain of [email protected] designates 209.235.244.40 as permitted sender) client-ip=209.235.244.40;
Received: (qmail 19872 invoked from network); 2 Jun 2011 19:40:39 -0000
Received: from unknown (HELO tickweb2.inetu.net) (192.168.244.5)
  by in-utility1.inetu.net with SMTP; 2 Jun 2011 19:40:39 -0000
Received: (qmail 41938 invoked by uid 80); 2 Jun 2011 19:40:38 -0000
Date: 2 Jun 2011 19:40:38 -0000
Message-ID: <[email protected]>

[lemur]

http://en.wikipedia.org/wiki/Forward_Co ... everse_DNS

[lemur]

I wonder if the "may be forged" is a problem issue for some spam catchers?

Code: Select all

Received: from intic-stage-app1.inetuhosted.net (res.tick-fw03.inetu.net [74.85.131.58] (may be forged))

Code: Select all

~: host 74.85.131.58
58.131.85.74.in-addr.arpa domain name pointer res.tick-fw03.inetu.net.
~: host res.tick-fw03.inetu.net
Host res.tick-fw03.inetu.net not found: 3(NXDOMAIN)
~: host intic-stage-app1.inetuhosted.net
intic-stage-app1.inetuhosted.net has address 209.235.235.202
~: host 209.235.235.202
202.235.235.209.in-addr.arpa domain name pointer res.tick-fw03.inetu.net.

looks like they only have some interesting ways to setup their stuff!!

they have the IP of 74.85.131.58 with a reverse DNS that doesnt match the host its claiming to be (intic-stage-app1.inetuhosted.net)

but.. the reverse DNS host (res.tick-fw03.inetu.net) doesnt even resolve to anything...

duh. oops..

certainly some servers aint gonna like that.

[lemur]

no one mentioned that I would have to pre-set my email to accept (whitelist) email from "[email protected]"!

I caught myself in a contradiction. I believe that even if I had whitelisted "[email protected]" that the email would still have been rejected mostly because of the hostname mismatch.

indeed.

[theCryptofishist]

posted in ther other thread, but my card was only charged for $1.01? No other charges. I'm so confused!

That's a test charge to make sure the card info is alright. YOu have a ticket.

[lemur]

Code: Select all

Jan 31 15:13:34 a postfix/smtpd[26287]: connect from unknown[74.85.131.58]
Jan 31 15:13:34 a postfix/smtpd[26287]: warning: 74.85.131.58: hostname res.tick-fw03.inetu.net verification failed: Name or service not known
<client=74.85.131.58> <helo=intic-stage-app1.inetuhosted.net> <[email protected]> 

if all this crap is confusing to you..

the host sending email claims to be: intic-stage-app1.inetuhosted.net
when the IP belonging to that host is looked up it claims the host ACTUALLY is: res.tick-fw03.inetu.net
when that host is looked up: it doesnt resolve at all. fails.

most email servers dont tend to like this.. unless configured to like it

BIG PICTURE:

the person who setup this stuff should have the IP 74.85.131.58 pointing to intic-stage-app1.inetuhosted.net and NOT res.tick-fw03.inetu.net

(and in addendum, if it isnt pointing to the 'correct' name, the one it is pointing to should resolve to something.. instead of failing)

a normal DNS lookup, like http://www.example.com might point to the IP 10.0.0.1.
if properly setup for email, 10.0.0.1 should point back to http://www.example.com
here, it doesnt give the same name.. it gives a different name, that messes stuff up on some mail servers
when you look up 10.0.0.1 in this example its giving you bong.example.com some servers dont like that

doing this might end up getting some email blocked/dropped on some servers, unless they are configured to allow it

in addendum to the names not matching in both directions.. one of the names they gave resolves to nothing.. not good idea.

MORAL OF THE STORY:

hey email server guy! yer doin it wrong!


(edit: damn you eplaya adding errant HTTP:// all over the place even tho i didnt want them www.dontdothat.com)

[soupman]

posted in ther other thread, but my card was only charged for $1.01? No other charges. I'm so confused!

That's a test charge to make sure the card info is alright. You have a ticket.

Whew thanks for that!! I have the same thing... pending charge for $1.01 but nothing else...yet... oh man this is gonna drive me crazy...

[trilobyte]

Great information, thank you for doing that research and sharing. I've relayed it to the ticket team, who will work with the ticket vendor on their end to help improve the process.

[soupman]

Received pre-authorization, did not get tickets

Here's hoping we can get those Feb. & March tickets! Fingers crossed!