Can't receive email on @maine.edu email address

Sean Edwards avatarSean Edwards created an issue

For some reason I am unable to add email addresses for anything in the Thiago Isaias.edu domain. I have tried sean.edwards@maine.edu and sean.edwards@umit.maine.edu - both are valid emails that I control. I have checked my spam folders on both of these addresses, and the messages are not there either. I've tried multiple times over the past month or two, and the confirmation email never comes through.

I've had problems receiving emails on sean.edwards@maine.edu before. The email bounces with a "Destination Net Unreachable" error. I don't know if this helps at all.

I would like to get sean.edwards@maine.edu added to my bitbucket account so that I can take advantage of the academic program, and use bitbucket for projects at school. I love the service, but I need to be able to add more private users for group projects.

Comments (13)

  1. Charles McLaughlin

    Hi Sean,

    As I mentioned in the support ticket you sent us -- I searched our mail logs and I believe there's a problem with your mail servers. I can't connect to your mx from our office in San Francisco or our data center in St. Louis. Hopefully you'll receive this response.

    Here's an example from our office:

    cmclaughlin@cm:/tmp$ dig mx maine.edu

    <<>> DiG 9.7.0-P1 <<>> mx maine.edu
    ; global options
    +cmd
    ; Got answer:
    ; ->>HEADER<<- opcode
    QUERY, status: NOERROR, id: 4813
    ; flags
    qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0

    ;; QUESTION SECTION:

    maine.edu. IN MX

    ;; ANSWER SECTION: maine.edu. 130 IN MX 10 mx2.maine.edu. maine.edu. 130 IN MX 10 mx3.maine.edu. maine.edu. 130 IN MX 10 mx4.maine.edu. maine.edu. 130 IN MX 10 mail-relay.maine.edu.

    ;; Query time: 55 msec ;; SERVER: 192.168.15.230#53(192.168.15.230) ;; WHEN: Tue Jun 21 13:47:28 2011 ;; MSG SIZE rcvd: 114

    cmclaughlin@cm:/tmp$ ^C cmclaughlin@cm:/tmp$ telnet mx2.maine.edu 22 Trying 130.111.32.19... Trying 130.111.32.61... Trying 2610:48:100:820::13... Trying 2610:48:100:820::3d... telnet: Unable to connect to remote host: Network is unreachable

    And here are excerpts from our server logs:

    Jun 20 08:03:23 bitbucket03 postfix/smtp[360]: connect to mx3.maine.edu[2610:48:100:820::3d]:25: Network is unreachable Jun 20 08:03:23 bitbucket03 postfix/smtp[360]: connect to mail-relay.maine.edu[2610:48:100:820::3d]:25: Network is unreachable Jun 20 08:03:23 bitbucket03 postfix/smtp[360]: connect to mail-relay.maine.edu[2610:48:100:820::e]:25: Network is unreachable Jun 20 08:03:23 bitbucket03 postfix/smtp[360]: connect to mx2.maine.edu[2610:48:100:820::3d]:25: Network is unreachable Jun 20 08:03:23 bitbucket03 postfix/smtp[360]: connect to mx2.maine.edu[2610:48:100:820::13]:25: Network is unreachable Jun 20 08:03:23 bitbucket03 postfix/smtp[360]: 026AD7A120F: to=<sean.edwards@maine.edu>, relay=none, delay=0.07, delays=0.01/0.01/0.06/0, dsn=4.4.1, status=deferred (connect to mx2.maine.edu[2610:48:100:820::13]:25: Network is unreachable) Jun 20 08:09:47 bitbucket03 postfix/smtp[11275]: connect to mx2.maine.edu[2610:48:100:820::3d]:25: Network is unreachable

  2. Sean Edwards

    It's interesting that this is an ongoing problem with certain mail servers on the west coast. I've had emails fail to deliver from other vendors out there too, so I suspect it's not really a problem with your service.

    Is there a way my sean.edwards@maine.edu email address could be manually associated with my account? It's the same one I originally emailed you from. I want this email account on my account so that I can be eligible for the academic license.

    Also, would it be possible for me to get a traceroute from that server to our MX server, so I can forward it along to the university's IT staff? It might be helpful to see exactly where the route fails.

  3. Charles McLaughlin

    Hi Sean,

    I upgraded your account to unlimited repos, so you don't have to worry about validating your .edu email address right now.

    Here's a traceroute:

    [cmclaughlin@bitbucket01 ~]$ traceroute mx2.maine.edu
    traceroute to mx2.maine.edu (130.111.32.61), 30 hops max, 60 byte packets
     1  207-223-240-177.contegix.com (207.223.240.177)  0.433 ms  0.476 ms  0.584 ms
     2  c1-f00.b1-e21.stl1.xiolink.com (63.246.15.1)  0.301 ms  0.311 ms  0.321 ms
     3  vlan706.car1.StLouis1.Level3.net (4.53.160.185)  0.349 ms  0.384 ms  0.437 ms
     4  ae-11-11.car2.StLouis1.Level3.net (4.69.132.186)  0.345 ms  0.389 ms  0.498 ms
     5  4.69.132.190 (4.69.132.190)  5.483 ms  5.481 ms  5.493 ms
     6  ae-5-5.ebr2.Chicago2.Level3.net (4.69.140.194)  5.607 ms  5.621 ms  5.548 ms
     7  ae-6-6.ebr2.Washington12.Level3.net (4.69.148.145)  20.252 ms  20.204 ms  20.305 ms
     8  ae-5-5.ebr2.Washington1.Level3.net (4.69.143.221)  20.819 ms  20.934 ms  20.792 ms
     9  ae-62-62.csw1.Washington1.Level3.net (4.69.134.146)  20.752 ms ae-92-92.csw4.Washington1.Level3.net (4.69.134.158)  20.746 ms ae-82-82.csw3.Washington1.Level3.net (4.69.134.154)  20.831 ms
    10  ae-3-80.edge2.Washington1.Level3.net (4.69.149.142)  20.779 ms  20.641 ms ae-1-60.edge2.Washington1.Level3.net (4.69.149.14)  20.791 ms
    11  ROADRUNNER.edge2.Washington1.Level3.net (4.79.22.50)  20.986 ms ROADRUNNER.edge2.Washington1.Level3.net (4.79.22.54)  21.004 ms ROADRUNNER.edge2.Washington1.Level3.net (4.79.22.6)  20.864 ms
    12  ae-1-0.cr0.dca20.tbone.rr.com (66.109.6.166)  20.907 ms  20.876 ms  41.391 ms
    13  ae-3-0.cr0.nyc30.tbone.rr.com (66.109.6.29)  26.881 ms  26.790 ms  26.613 ms
    14  66.109.6.75 (66.109.6.75)  36.107 ms  53.714 ms 107.14.19.27 (107.14.19.27)  37.208 ms
    15  ae0-0.glflnyaq-rtr000.nyroc.rr.com (24.24.21.214)  38.682 ms  38.987 ms  38.611 ms
    16  rdc-204-210-69-50.ne.northeast.rr.com (204.210.69.50)  43.643 ms  43.809 ms  43.685 ms
    17  rdc-204-210-69-25.ne.northeast.rr.com (204.210.69.25)  60.074 ms  60.150 ms  60.116 ms
    18  rdc-204-210-68-151.ne.northeast.rr.com (204.210.68.151)  58.467 ms  49.388 ms  49.331 ms
    19  rrcs-208-105-165-150.nys.biz.rr.com (208.105.165.150)  49.736 ms  49.203 ms  49.283 ms
    20  gi5-2.gw-orono.net.maine.edu (130.111.2.25)  49.667 ms  49.130 ms  49.066 ms
    21  gi2-3.gw-o-neville.net.maine.edu (130.111.31.130)  50.269 ms  49.993 ms  49.999 ms
    22  * * *
    23  * * *
    24  * * *
    25  * * *
    26  * * *
    27  * * *
    28  * * *
    29  * * *
    30  * * *
    
    

    I'll go ahead and close this issue. Please let us know if you need any other assistance.

  4. Sean Edwards
    • changed status to new

    One more thing - could you try a ping6 and tracert6 (ping -6 and traceroute -6 on Windows) to that same server? My contact in the university's networking group made a good point - your server is actually trying to connect to our mail server via IPv6. I completely missed it in the logs:

    Jun 20 08:03:23 bitbucket03 postfix/smtp[360]: connect to mx3.maine.edu[2610:48:100:820::3d]:25: Network is unreachable

    UMaine's network supports full IPv6, and publishes AAAA records for most (all?) domains it owns. Since DNS prefers AAAA records over A records when available, it would seem that something along the line has broken IPv6 support.

    Thanks again for the help!

  5. Charles McLaughlin

    Hi Sean,

    Sorry, I didn't notice that you had IPv6 setup. Also, there's nothing wrong with your mail servers -- I tried to telnet into port 22 instead of port 25 to test, which mislead me. Our data center does not yet support IPv6, so until we sort that out I set our Postfix servers to only use IPv4. Please reopen this issue if you have any more troubles.

    Regards, Charles

  6. Ed Ropple
    • changed status to open

    Seems there are still issues - like Sean, I just tried to validate with my maine.edu email (edward.ropple@maine.edu) and had no luck as well. I've sent an email to support@bitbucket.org (email ticket #1026) as well.

    Any help you could provide would be awesome. Thanks!

  7. Charles McLaughlin

    Hi Ed,

    From our side it looks like the messages are going through. Here's some excerpts from our logs:

    Jul 12 00:53:52 bitbucket01 postfix/smtp[28826]: 230304C0B79: to=<edward.ropple@maine.edu>, relay=mx3.maine.edu[130.111.32.61]:25, delay=9.8, delays=0/0/5.7/4.1, dsn=2.0.0, status=sent (250 2.0.0 p6C5rhWw020167 Message accepted for delivery) Jul 12 00:55:53 bitbucket01 postfix/smtp[28826]: 826AD4C0B55: to=<err@umcs.maine.edu>, relay=gandalf.umcs.maine.edu[130.111.197.21]:25, delay=0.98, delays=0/0/0.71/0.26, dsn=2.0.0, status=sent (250 BAA09407 Message accepted for delivery)

    I don't want you to be held up by this, so we went ahead and gave your account unlimited repositories.

    Regards, Charles

  8. Charles McLaughlin
    • changed status to open

    Hi guys,

    I sent you some test messages:

    """

    [root@bitbucket01 ]# mailx -s "Test Message 1021" edward.ropple@maine.edu Hello . EOT

    [root@bitbucket01 ]# mailx -s "Test Message 1023" sean.edwards@maine.edu Hello - this is a test message. Please comment on https://bitbucket.org/site/master/issue/2802/cant-receive-email-on-maineedu-email if you get this. . EOT

    """"

    Our logs show they went through:

    """

    [root@bitbucket01 ]# grep maine.edu /var/log/maillog Jul 12 00:53:52 bitbucket01 postfix/smtp[28826]: 230304C0B79: to=<edward.ropple@maine.edu>, relay=mx3.maine.edu[130.111.32.61]:25, delay=9.8, delays=0/0/5.7/4.1, dsn=2.0.0, status=sent (250 2.0.0 p6C5rhWw020167 Message accepted for delivery)

    Jul 12 00:55:53 bitbucket01 postfix/smtp[28826]: 826AD4C0B55: to=<err@umcs.maine.edu>, relay=gandalf.umcs.maine.edu[130.111.197.21]:25, delay=0.98, delays=0/0/0.71/0.26, dsn=2.0.0, status=sent (250 BAA09407 Message accepted for delivery)

    Jul 15 12:22:27 bitbucket01 postfix/smtp[7726]: D43464C0BCF: to=<edward.ropple@maine.edu>, relay=mx4.maine.edu[130.111.32.19]:25, delay=5.6, delays=0.01/0/5.4/0.21, dsn=2.0.0, status=sent (250 2.0.0 p6FHMMlA014526 Message accepted for delivery)

    Jul 15 12:24:48 bitbucket01 postfix/smtp[13899]: EEDE44C0BCF: to=<sean.edwards@maine.edu>, relay=mx3.maine.edu[130.111.32.19]:25, delay=5.4, delays=0.02/0.01/5.2/0.12, dsn=2.0.0, status=sent (250 2.0.0 p6FHOhQ8018626 Message accepted for delivery)

    """"

    Please let me know if you don't receive them and don't forget to check your spam folder :)

    Thanks,

    Charles

  9. Log in to comment
Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.