I am using the Office365 silo, and it always ends up in SPAM there
Ge0rG
Alex: you could inspect the mail headers for why
jonas’
probably SPF
Alex
I did, my assumption maybe SPF or other Email records
Alex
its coming from nicolas.verite@nayego.net, not sure if all the records are setup correctly at TinyLetter/Mailchimo
Alex
I also think it should come from an XSF domain
emus
Me 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
emus
Do 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
MattJ
The 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/
emus
MattJ: Thanks
jonas’
so the rightest thing to do is to deploy a subdomain for which we do that.
Seve
It 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 :)
emus
Ok. Yes. I am sure jcbrand will support that
emus
xsf_commteam@ xmpp.org
Seve jcbrand would that be okay for you as a potential adress?
undefinedhas joined
jcbrand
I think newsletter@xmpp.org is nicer, or otherwise comms@xmpp.org
jcbrand
No need to have underscores in an email address 🙂
mihohas joined
mihohas left
eevvoorhas joined
MattJ
Agree re. underscores, though I think it would be good to use a subdomain as jonas’ suggested
Seve
Was 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? :)
emus
Lets keep the email general and not sticked to a task. Then I think commteam@xmpp.org is good
emus
jonas' no please not connected to a topic
jonas’
emus, but the address needs special settings because it is used for a newsletter
emus
Ah okay. And that is such a special setting that it should not be used for other email purposes?
jonas’
yes
emus
then make it newsletter@
jonas’
@somesubdomain.xmpp.org
emus
ok
jonas’
hence my proposal news@letter.xmpp.org, since it’s fun
emus
hmm... ok
jonas’
but we can also do newsletter@bulk.xmpp.org or something like that
emus
no, news@letter.xmpp.org is fine
emus
jcbrand seve ?
jcbrand
Newsletter 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
jcbrand
Actually in think the convention is usually no-reply@...✎
jcbrand
Actually I think the convention is usually no-reply@... ✏
Seve
newsletter 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 :)
Seve
Super!
MattJ
Now 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
emus
I'm fine with no-reply
emus
but wait
emus
If this is the registered email in Tinynewsletter ... will that be a problem to access the account?
emus
If there is no inbound?
mimi89999has joined
j.rhas joined
emus
Because in TinyNewsletter, the email you register, is the email you spam the world with
emus
At least it seem to be the case to me
jonas’
MattJ, OK, I’ll try to figure out which records we need
emus
There is only one field for Email. Nothing else, so I guess the email you put there is used for "everything"
Here are all headers: https://paste.debian.net/1159517/
lovetoxhas joined
emus
Thanks 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
Alex
Holger: 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
emus
jonas' 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
MattJ
jonas’, 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
MattJ
They verify it, for starters, by sending you an email
Shellhas left
Shellhas joined
emus
Yes, thanks MattJ
MattJ
Right now I don't see an obvious reason why it doesn't go to spam ~100% of the time
karoshihas left
emus
Also a point
Kev
flow: 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
flow
Hmm, 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?
flow
Kev, 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
vanitasvitae
Digging 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.
vanitasvitae
However, I fail to find any records of this board meeting.