Ticket invoice details change

[pyatochkin]

Apologizes, writing to you here as looks like your shop@mail.defcon.org and info@defcon.org info@defcon.org are not working/active
Hiya,

Apologizes for writing here, as looks like your shop@mail.defcon.org and info@defcon.org are not working/active.

I’ve purchased a ticket, but would need add more details in the invoice for the ticket.

Could someone re-direct me to the correct team who may help with this please?
Many thanks in advance.employer is asking to change details (add more) in the invoice for the ticket.

Is it something you may help with or could you re-direct me to the correct team who may help with this please?
Many thanks in advance.

[number6]

Apologizes, writing to you here as looks like your shop@mail.defcon.org and info@defcon.org info@defcon.org are not working/active
Hiya,

Apologizes for writing here, as looks like your shop@mail.defcon.org and info@defcon.org are not working/active.

I’ve purchased a ticket, but would need add more details in the invoice for the ticket.

Could someone re-direct me to the correct team who may help with this please?
Many thanks in advance.employer is asking to change details (add more) in the invoice for the ticket.

Is it something you may help with or could you re-direct me to the correct team who may help with this please?
Many thanks in advance.

Most problems with delivery of email to *@defcon.org are caused by incorrectly configured domains.
* PTR missing or does not match FQDN/domain provided by relay attempting delivery in HELO/EHLO
* DKIM missing or invalid or does not match what is in DNS for given domain
* SPF does not match what it gievn in DNS, especially when DMARC indicates we should not accept mail when connecting IP does not match SPF.

Next most common are mail servers/relays that attempt delivery but do not support STARTTLS.

Next is servers that support STARTTLS but not with modern ciphersuites.

Without recommending any of these, these mail service providers' servers work fine when delivering mail to *@defcon.org:
gmail.com , proton mail, outlook.com

Usually the bounce message from the relay unable to deliver to *@defcon.org provides some hint as to why delivery failed.

I just tested delivery of mail to shop@defcon.org from a properly configured mail server and the message was delivered.

Generic providers used by many domains which are known to support STARTTLS but not support modern ciphersuites include:
pphosted.com
mimecast.com
(There are others, but revealing their domain name would reveal someone / something from those domains are attempting to email *@defcon.org)

You could try to convince your mail service provider to address limits that prevent delivery.

You can try emailing from an email service provider that works to shop@defcon.org, and explain that you tried to email from the email address used when making a purchase, but it bounced, then see what they can do to help you with your questions.

I have zero permission to weaken ciphersuite selection to support older ciphersuites, or disable requirements of use of STARTTLS.
I don't set those policies, only try to work within them.

Last, I do not work shop.defcon.org so please don't send me details about your order or PII used in order or provided in order: I do not have access to the information about orders at shop.defcon.org .

The only contact information I have found for https://shop.defcon.org/ is printed on their website, lower left corner:

Contact

shop@mail.defcon.org

1100 bellevue way ne, 8A85
Bellevue Washington
98004 United States