AlexI am using the Office365 silo, and it always ends up in SPAM there
Ge0rGAlex: you could inspect the mail headers for why
jonas’probably SPF
AlexI did, my assumption maybe SPF or other Email records
Alexits coming from nicolas.verite@nayego.net, not sure if all the records are setup correctly at TinyLetter/Mailchimo
AlexI also think it should come from an XSF domain
emusMe too
jcbrand, Seve
Do you agree that I head for to create an official CommTeam email?
jonas’it won’t solve the problem though
karoshihas left
emusDo you also think I should reach out to tinynewsletter/mailchimp about that SPF?
jonas’they can’t do anything about that
jonas’that’d be useless if they could
MattJThe right thing to do is use an xmpp.org address and for us to add the SPF records
jonas’that might work
Alex👍
jonas’and also allow mailchimp to spam on our behalf \o/
emusMattJ: Thanks
jonas’so the rightest thing to do is to deploy a subdomain for which we do that.
SeveIt was too troublesome to start the newsletter going through an XSF's email address just to try the concept out. But it looks like we are ready for an official address now :)
emusOk. Yes. I am sure jcbrand will support that
emusxsf_commteam@ xmpp.org
Seve jcbrand would that be okay for you as a potential adress?
undefinedhas joined
jcbrandI think newsletter@xmpp.org is nicer, or otherwise comms@xmpp.org
jcbrandNo need to have underscores in an email address 🙂
mihohas joined
mihohas left
eevvoorhas joined
MattJAgree re. underscores, though I think it would be good to use a subdomain as jonas’ suggested
SeveWas about to say exactly those
Seve👍
Andrzejhas joined
karoshihas joined
karoshihas left
karoshihas joined
undefinedhas left
jonas’please no underscores
jonas’news@letter.xmpp.org? :)
emusLets keep the email general and not sticked to a task. Then I think commteam@xmpp.org is good
emusjonas' no please not connected to a topic
jonas’emus, but the address needs special settings because it is used for a newsletter
emusAh okay. And that is such a special setting that it should not be used for other email purposes?
jonas’yes
emusthen make it newsletter@
jonas’@somesubdomain.xmpp.org
emusok
jonas’hence my proposal news@letter.xmpp.org, since it’s fun
emushmm... ok
jonas’but we can also do newsletter@bulk.xmpp.org or something like that
emusno, news@letter.xmpp.org is fine
emusjcbrand seve ?
jcbrandNewsletter is one word, so news@letter seems weird to me. Do we accept replies on that address? Otherwise we can do noreply@newsletter.xmpp.org
jcbrandActually in think the convention is usually no-reply@...
jcbrandActually I think the convention is usually no-reply@...
Sevenewsletter should go altogether in my opinion. Going with the no-reply seems the way to go?
jonas’jcbrand, no-reply sounds like a plan
jonas’since we won’t set up an inbound mailbox actually :)
SeveSuper!
MattJNow if someone can write down on the iteam issue tracker exactly what DNS records need adding, I can look at it later or make sure jonas’ has access if he wants to
neshtaxmpphas joined
emusI'm fine with no-reply
emusbut wait
emusIf this is the registered email in Tinynewsletter ... will that be a problem to access the account?
emusIf there is no inbound?
mimi89999has joined
j.rhas joined
emusBecause in TinyNewsletter, the email you register, is the email you spam the world with
emusAt least it seem to be the case to me
jonas’MattJ, OK, I’ll try to figure out which records we need
emusThere is only one field for Email. Nothing else, so I guess the email you put there is used for "everything"
!XSF_MartinHere are all headers: https://paste.debian.net/1159517/
lovetoxhas joined
emusThanks Martin
Andrzejhas left
Andrzejhas joined
eevvoorhas left
eevvoorhas joined
Holgerhas joined
Guushas left
Guushas joined
mukt2has left
mukt2has joined
karoshihas left
karoshihas joined
karoshihas left
karoshihas joined
karoshihas left
karoshihas joined
undefinedhas joined
krauqhas left
krauqhas joined
AlexHolger: the Q3 application period ends this week, lets go ;-)
https://wiki.xmpp.org/web/Membership_Applications_Q3_2020
jonas’Link Mauve, !!
karoshihas left
mukt2has left
rionhas joined
emusjonas' is that an issue to have this email as the account email then? because in the end they prevent us from using the account?
jonas’emus, I don’t quite get what you mean
karoshihas joined
MattJjonas’, tinyletter sends from the email address you sign up with
jonas’for certain definitions of "from the email address"
jonas’ah, but you want to say the issue is that they’ll try to send transactional/account related email there?
eevvoorhas left
MattJThey verify it, for starters, by sending you an email
Shellhas left
Shellhas joined
emusYes, thanks MattJ
MattJRight now I don't see an obvious reason why it doesn't go to spam ~100% of the time
karoshihas left
emusAlso a point
Kevflow: re: sometimes bare JID and no to not being equivalent - 191 requires that you send stuff with no to, instead of bare JID.
Kev(Although I think it entirely reasonable, and even desirable, to ignore that restriction on the server and process either)
Kev(I think it was you who asked for an example the other days, sorry if I misremember)
karoshihas joined
flowHmm, would we benefit from a standard boilerplate text for such situations? I.e. situations when you can use either no 'to' or put our own bare JID into to in XEPs?
flowKev, I also think it was me who asked btw
karoshihas left
remkohas joined
mukt2has joined
undefinedhas left
lovetoxhas left
karoshihas joined
eevvoorhas joined
Shellhas left
mukt2has left
Marandahas left
Marandahas joined
lovetoxhas joined
lobodelrayohas joined
lobodelrayohas left
lobodelrayohas joined
lovetoxhas left
lobodelrayohas left
mukt2has joined
krauqhas left
krauqhas joined
undefinedhas joined
vanitasvitaeDigging around the EAX XEPs right now. XEP-EAX-CAR (E2E Authentication in XMPP: CA Requirements) is in inbox since february of 2019. The council protocols state that Board has to decide whether or not to accept this specification since it is procedural.
vanitasvitaeHowever, I fail to find any records of this board meeting.