CUNY Academic Commons

I can confirm that the email in question went out successfully and was delivered to Hunter's mail system.

[root@commons ~]# grep mfabrica@hunter.cuny.edu /var/log/maillog*
/var/log/maillog-20120923:Sep 18 13:30:04 commons postfix/smtp[19414]: 82539174891: to=<mfabrica@hunter.cuny.edu>, relay=relay.gc.cuny.edu[172.29.28.89]:25, delay=0.39, delays=0.19/0.01/0.01/0.18, dsn=2.6.0, status=sent (250 2.6.0 <54e30734e25c28d1b7ef7feab3c11b0d@commons.gc.cuny.edu> Queued mail for delivery)
/var/log/maillog-20120923:Sep 20 16:40:33 commons postfix/smtp[11631]: B4BB51744F0: to=<mfabrica@hunter.cuny.edu>, relay=relay.gc.cuny.edu[172.29.28.90]:25, delay=0.22, delays=0.01/0/0/0.21, dsn=2.6.0, status=sent (250 2.6.0 <e637276e62af2cca102f5894398676eb@commons.gc.cuny.edu> Queued mail for delivery)
/var/log/maillog-20120923:Sep 20 17:19:11 commons postfix/smtp[15883]: C8735174548: to=<mfabrica@hunter.cuny.edu>, relay=relay.gc.cuny.edu[172.29.28.89]:25, delay=0.18, delays=0.03/0.01/0/0.13, dsn=2.6.0, status=sent (250 2.6.0 <a447dc26b4f49bb910be7beae7770348@commons.gc.cuny.edu> Queued mail for delivery)
[root@commons ~]# grep C8735174548 $_
Sep 20 17:19:11 commons postfix/pickup[10342]: C8735174548: uid=48 from=<apache>
Sep 20 17:19:11 commons postfix/cleanup[15881]: C8735174548: message-id=<a447dc26b4f49bb910be7beae7770348@commons.gc.cuny.edu>
Sep 20 17:19:11 commons postfix/qmgr[6052]: C8735174548: from=<apache@commons.gc.cuny.edu>, size=1071, nrcpt=1 (queue active)
Sep 20 17:19:11 commons postfix/smtp[15883]: C8735174548: to=<mfabrica@hunter.cuny.edu>, relay=relay.gc.cuny.edu[172.29.28.89]:25, delay=0.18, delays=0.03/0.01/0/0.13, dsn=2.6.0, status=sent (250 2.6.0 <a447dc26b4f49bb910be7beae7770348@commons.gc.cuny.edu> Queued mail for delivery)
Sep 20 17:19:11 commons postfix/qmgr[6052]: C8735174548: removed

Great info -- thanks so much, André. Steve, can you tell Michael that the problem resides with Hunter's email system? Maybe he can contact Hunter IT to ask why this would have happened, inviting them to get in touch with André to suss out the problem (assuming that's okay with André).

Sure, please feel free to share my email and phone number with Hunter's techs to troubleshoot the issue together.

Thanks, André. Steve, the other thing to keep in mind is that registration confirmation emails are only good for a limited time -- they have to be clicked within a few days, or they go inactive and the registration process has to be started anew.

Thus, I would say that Michael should contact Hunter IT as described above to figure out why the email never reached him. Once they figure that out, we'll know that the next email will reach him, but he'll need to register again.