Skip to content

Commit c500184

Browse files
committed
Script to run from cron to send daily messages to IETF Announce showing the email header field change.
This should be run from Jan 6 to Jan 20, after which point we need to deploy analagous changes to the code that constructs last call announcements. This is related to bug ietf-tools#811 Commit ready for merge. - Legacy-Id: 6857
1 parent ac799a9 commit c500184

2 files changed

Lines changed: 70 additions & 0 deletions

File tree

ietf/bin/announce-header-change

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,37 @@
1+
#!/usr/bin/env python
2+
3+
import datetime
4+
5+
from django.core import management
6+
from django.template.loader import render_to_string
7+
8+
from ietf import settings
9+
from ietf.utils.mail import send_mail_preformatted
10+
from ietf.utils.mail import send_mail
11+
12+
management.setup_environ(settings)
13+
14+
target_date=datetime.date(year=2014,month=1,day=20)
15+
16+
send_mail(request = None,
17+
to = "IETF-Announce <ietf-announce@ietf.org>",
18+
frm = "The IESG <iesg-secretary@ietf.org>",
19+
subject = "Upcoming change to announcement email header fields (using old header)",
20+
template = "utils/header_change_content.txt",
21+
context = dict(oldornew='old', target_date=target_date),
22+
extra = {'Reply-To' : 'ietf@ietf.org',
23+
'Sender' : '<iesg-secretary@ietf.org>',
24+
}
25+
)
26+
27+
send_mail(request = None,
28+
to = "IETF-Announce:;",
29+
frm = "The IESG <noreply@ietf.org>",
30+
subject = "Upcoming change to announcement email header fields (using new header)",
31+
template = "utils/header_change_content.txt",
32+
context = dict(oldornew='new', target_date=target_date),
33+
extra = {'Reply-To' : 'IETF Discussion List <ietf@ietf.org>',
34+
'Sender' : '<iesg-secretary@ietf.org>',
35+
},
36+
bcc = '<ietf-announce@ietf.org>',
37+
)
Lines changed: 33 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,33 @@
1+
{% filter wordwrap:73 %}
2+
We will soon be changing the header fields used in IETF Last Call messages sent to the IETF Announce mailing list.
3+
4+
This message is to to inform you of the change and allow you to test that you are properly receiving messages using the new header fields.
5+
6+
We are making this change to make it more likely that replies go to the intended recipients.
7+
8+
This message will be repeated daily using both the old and new header.
9+
This instance of the message was sent using the {{oldornew}} header.
10+
Please ensure you receive both versions.
11+
These messages will cease, and all Last Call messages to this list will switch to using the new header on or shortly after {{target_date}}.
12+
13+
The specific changes are:
14+
15+
{% endfilter %}
16+
Old:
17+
18+
From: The IESG <iesg-secretary@ietf.org>
19+
To: IETF-Announce <ietf-announce@ietf.org>
20+
Reply-To: ietf@ietf.org
21+
22+
New:
23+
24+
From: The IESG <noreply@ietf.org>
25+
To: IETF-Announce:;
26+
Reply-To: IETF Discussion List <ietf@ietf.org>
27+
28+
and the message sent using the New header fields will also be
29+
Bcc-ed to <ietf-announce@ietf.org>
30+
31+
Thanks for your patience as we make this adjustment,
32+
33+
The IESG

0 commit comments

Comments
 (0)