January 2014 - Core-sysadmins - mailman3.cels.anl.gov

sshuttle
by Murphy-Olson, Daniel E. 30 Jan '14

30 Jan '14

FYI, here is the nifty poor mans vpn I spoke about at the sync -- https://github.com/apenwarr/sshuttle ---- Daniel Murphy-Olson Systems Administrator Mathematics & Computer Science Division Argonne National Laboratory 630-252-0055

1 0

pr-2d11-color waste toner container
by John Valdes 29 Jan '14

29 Jan '14

FYI, pr-2d11-color was crying 'cause its diaper was full, so I changed it. I used the last clean one, so more will need to be ordered in advance of the next changing. I left the soiled one on top of the horizontal filing cabinet that's next to the printer. John PS. In case it's not obvious, diaper = waster toner container.

1 0

Undelivered Mail Returned to Sender
by MAILER-DAEMON＠mcs.anl.gov 29 Jan '14

29 Jan '14

This is the mail system at host rt.mcs.anl.gov. I'm sorry to have to inform you that your message could not be delivered to one or more recipients. It's attached below. For further assistance, please send mail to postmaster. If you do so, please include this problem report. You can delete your own text from the attached returned message. The mail system <dneslon(a)alcf.anl.gov>: host 140.221.7.6[140.221.7.6] said: 550 5.1.1 <dneslon(a)alcf.anl.gov>: Recipient address rejected: User unknown in relay recipient table (in reply to RCPT TO command)

1 0

Where's Dan?
by Murphy-Olson, Daniel E. 29 Jan '14

29 Jan '14

My daughter apparently found a way to do something awful to her ankle, even though we were stuck inside all day yesterday. I'm going to try to get her in to see her doctor this morning. Please put me down for 1/2 sick day at this point. ---- Daniel Murphy-Olson Systems Administrator Mathematics & Computer Science Division Argonne National Laboratory 630-252-0055

1 0

Morning Migration Update
by Zaluzec, Christiaan N. 29 Jan '14

29 Jan '14

Good Morning, Nineteen mailboxes were queued for migration last night. Seventeen have completed and two are still running. karpeev(a)mcs.anl.gov<mailto:[email protected]> lusk(a)mcs.anl.gov<mailto:[email protected]> Large mailbox size is the reason that they have yet to complete. Christiaan

1 6

Where's Max?
by Trefonides, Adam A. 29 Jan '14

29 Jan '14

The kids have school, but Freya doesn't start until 9, considering the wind chills are still ridiculous I'm not going to make her walk. I'll miss the sync. Today mire of the same, hoping to get silver clear of all individual account shares this week. Making rt4-Dev move mail and learning puppet workflow. Sent from my iPhone using TouchDown (www.nitrodesk.com)

1 0

Article on monitoring
by Stacey, Craig J. 28 Jan '14

28 Jan '14

Not all applicable to us, but things like monitoring SSL expiration are neat ideas. http://word.bitly.com/post/74839060954/ten-things-to-monitor

1 0

REMINDER: Your mailbox will be migrated from Zimbra to Exchange after 9:00pm on Tuesday January 28th
by Argonne Service Desk 28 Jan '14

28 Jan '14

Hello, This message is to inform you that your mailbox will be migrated to Exchange after 9:00pm on the evening of Tuesday January 28th. If you already have an Exchange account, very little will change for you. Your Zimbra mailbox will be merged into your existing Exchange mailbox, and it will continue working as usual. You can access important information and detailed configuration documentation at http://inside.anl.gov/services/zimbra-e-mail Quick configuration information for IMAP and POP mail clients can be found at https://wiki.anl.gov/public/CIS_Email_Services/Zimbra_to_Exchange_Migration… E-mail folders and messages, Calendar items, Contacts (excluding Personal Distribution Lists), and Tasks will be migrated from Zimbra to Exchange. Important changes to note include: 1. Briefcase Data will not migrate - There is no equivalent feature to the Briefcase within Microsoft Exchange 2. Mailbox rules and filters, as well as message forwarding will need to be recreated on the new mailbox 3. Signatures will need to be recreated on the new mailbox 4. Personal Distribution Lists will need to be recreated on the new mailbox 5. Calendar and mailbox sharing permissions will need to be recreated on the new mailbox 6. Your mobile device will now require a 4 character passcode screen lock in order to synchronize your mailbox via ActiveSync 7. If you send mail with a "From" address that is not your usual e-mail address, please let us know so we can configure that for you 8. If you synchronize your email to a mobile device via the IMAP protocol, your emails may synchronize in the wrong order, listing the oldest emails first. This is only an issue while your mailbox data is being actively migrated. You can circumvent this issue entirely by choosing to synchronize your device via ActiveSync instead of IMAP. Once your migration begins, you will need to log on to your Exchange mailbox in order to read and respond to new mail messages. You can access your Exchange mailbox via the following methods. 1. Using the Outlook Web app by browsing to http://mail.anl.gov and logging in with your ANL domain name and password using the format ANL\username or user(a)anl.gov<mailto:[email protected]>. A quick reference card for navigating through the Outlook Web App has been included as an attachment in this email. Links to training videos for Outlook web App are also available from the login page. 2. Reconfiguring your existing email client or mobile device using the instruction sets found at https://wiki.anl.gov/public/CIS_Email_Services/Zimbra_to_Exchange_Migration… 3. If your Mailbox is over 25gb in size, a mail archive will automatically be configured for you. You will also receive an additional email with more information on archiving. Any mail or calendar items older than two years will automatically be placed into that archive. The archive will automatically appear and be accessible via Outlook Web Access, but not by Outlook for Mac, IMAP clients, or mobile devices. Additional information on mailbox archiving can be found at https://wiki.anl.gov/wiki_public/images/d/df/Archiving_Mail_Using_Outlook_W… You can also find additional instructional resources for Outlook Web App and other clients at https://wiki.anl.gov/public/CIS_Email_Services/Zimbra_to_Exchange_Migration… Technical support will be available the morning after your migration to assist with Email client and mobile device reconfiguration. You will have three options for obtaining support. 1. A transition support technician will be stationed in your area the morning after your migration to assist with E-mail configuration. 2. Divisional IT support will be available as normal and prepared to help. 3. The CIS Helpdesk will be available at 2-9999, option 2, and can assist you with obtaining the necessary support. We hope that the preceding information is sufficient to properly prepare you for your mailbox transition. If at any point in time you have questions, comments or concerns, please bring it to the attention of your division's IT support. Thank you for patience and cooperation during this process, The CIS Email Services Team

1 0

ALCF Absence Calendar and ALCF Events Calendar now available
by Argonne Service Desk 28 Jan '14

28 Jan '14

Hello, This message is to inform you that the migration of the "ALCF Absence Calendar" and "ALCF Events Calendar" has completed. To connect to the calendar via your preferred email client, please reference the appropriate "Connecting to a Shared Calendar With..." link on the How-to wiki page below https://wiki.anl.gov/public/CIS_Email_Services/Exchange_User_Documentation Thank you, CIS Email Services

1 0

PagerDuty config
by Stacey, Craig J. 28 Jan '14

28 Jan '14

Right now, PagerDuty is configured such that our on-call schedule is not in effect during business hours. I'm considering changing that. Here's why. Right now, I have it set up to notify me first, then, if I don't respond in a minute, escalate to the rotation schedule. This is mainly so I can see how high traffic it is, and get a handle on how it's working. But, because the on-call schedule exempts working hours, it immediately escalated to the next level, which is currently Dan. So, questions: 1) Any reason not to have it on all the time? 2) What would be a good escalation policy for things that go unanswered by the on-call person? Right now it's 30 minutes of nothing, assign to Dan. I feel like a fairer method would be a secondary on-call schedule that is one-week staggered from the main one, and if the 30 minute window passes, assign based on that schedule. Then if *that* goes unanswered, assign to me.

4 4