- NZNOG - lists.nznog.org

Of interest - Yahoo mail issues
by Michael J. Densem 22 Oct '07

22 Oct '07

Hi, This is simply some information that may be of interest to those who have had/are having issues with Xtra email since the change over to Yahoo! I had problems with their servers rejecting email from my servers back in August (when Xtra changed to Yahoo for email services). I filled out all the suggested documents and requests to have my server(s) white-listed. Today (23 Oct) I finally had a response (see email below). No further comment! - just FYI -----Original Message----- From: Yahoo! Mail [mailto:mail-abuse-review(a)cc.yahoo-inc.com] Sent: Tuesday, 23 October 2007 7:45 a.m. To: Michael J. Densem Subject: Yahoo! Customer Care - monitor results... (KMM59108720V785******) Hello Mike, We appreciate your patience. We have recently concluded the monitoring of your company's mailings. Based on the information we have gathered, it appears that our users deem that the mailings from your IP address(es) are being directed to the correct folder and we cannot systematically exempt your mailings from our SpamGuard technology for: 202.174.***.*** 202.174.***.*** 202.174.***.*** Please keep in mind that our SpamGuard technology will continually monitor user feedback pertaining to emails coming from your mail server(s), and as such, the user feedback we receive will be one of the factors that influence where your emails are most appropriately delivered. Our studies have indicated that when users see messages miscategorized, they notify us within hours of delivery. Note: If you wish to ensure that your users get your emails in their Inbox, you may want to ask your subscribers to set up a filter in Yahoo! Mail specifically for your emails, or have them add your email address(es) to their Yahoo! Address Book. If you implement significant changes to your mailing practices, feel free to contact us again in 6 months and we will send you our most up-to-date application and reevaluate your mailing practices at that time. You may refer to the Help page below for some information and general guidelines that we have found to be effective in maintaining good mailing lists: http://help.yahoo.com/help/us/mail/bulk/bulk-01.html Please let us know if you still experience problems so we may assist you further to resolve your issue. Your patience during this process is greatly appreciated. Thank you again for contacting Yahoo! Mail. Regards, Thomas Immer Yahoo! Customer Care

1 0

Re: [nznog] Citylink problems?
by Tony Wicks 21 Oct '07

21 Oct '07

Ok, I'll run a pool for cause. Propose possible reasons and I'll come up with odds. All betting to be done in the currency of handles to be settled at the next meeting. Well Its been more than a couple of more hours now ! There had better be a good explanation and I really love the - Network Status - No known fault System Status Normal - No major problems

6 7

Re Yahoo and Spam...
by Mark Foster 19 Oct '07

19 Oct '07

Learned NZNOGrs, Some advice, please. Recently an email address that comes to me was sent some Unsolicited Commercial Email from (apparently) a UK based outfit that sells (print) magazine subscriptions. The headers contain this: Received: from smtp107.biz.mail.re2.yahoo.com (smtp107.biz.mail.re2.yahoo.com [206.190.52.176]) by mx.blakjak.net (Postfix) with SMTP id 8C508500D4 for <dest(a)address>; Tue, 16 Oct 2007 12:02:52 +1300 (NZDT) They contain additional Received: headers which would imply that Yahoo themselves received the message via SMTP from an AOL IP address that Traceroute implies is likely in the UK as well. So I took a full-headers copy of the message and forwarded the complaint to the relevant abuse contacts for both Yahoo and AOL. AOL, i've heard nothing (unsuprising). Yahoo, I had a response within 2-3 days which basically absolved them of responsibility, as follows: --8<-- Thank you for writing to Yahoo! Mail. I understand your frustration in receiving unsolicited email. While we investigate all reported violations against the Yahoo! Terms of Service (TOS), in this particular case the message you received was not sent through the Yahoo! Mail system. Yahoo! has no control over activities outside its service, and therefore we cannot take action. You may try contacting the sender's email provider, by identifying the sender's domain and contacting the administrator of that domain. The sender's provider should be in a better position to take appropriate action against the sender's account. The email message itself does contain some information relating to the sender's identity. Yahoo! includes the originating Internet Protocol (IP) address in the full Internet headers of all messages sent through Yahoo! Mail, so that we will have information regarding the origin of messages sent through our system. The originating IP address should be located in the very last "Received" line of the full Internet headers and corresponds to the sender's Internet Service Provider (ISP). Please see the following URL for more assistance: http://help.yahoo.com/help/us/mail/spam/spam-05.html Once you have identified the IP address, you can conduct an IP lookup to determine which ISP provides this person with Internet access. One such lookup tool you may want to try is: http://www.arin.net/whois/ You can then attempt to contact that ISP to report any abuse activities occurring within their service. Please let us know if you still need assistance so I may assist you further. Your patience during this process is greatly appreciated. Thank you again for contacting Yahoo! Mail. Regards, --8<-- I responded back indicating my understanding as being: - That my MTA received it from Yahoo, thus they relayed it... - That headers below the line where my MTA actually is involved, are often untrustworthy... I got a very-slightly-reworded version of exactly the same canned response back. So despite the fact that the sender is very clearly using Yahoo for SMTP (which, one would hope, would establish the sender as a Yahoo! Mail customer), they're pleading ignorance and/or innocence. Any other players had similar dealings with Yahoo (or other free mail providers) ? At what point can the provider realistically abdicate from responsibility when it comes to spam? And the obvious question: Is it fair to expect more from them? Or am I resigned to accept either periodic junk relayed by Yahoo because they can't be held responsible for what individual customers do? (And because in this example, the collateral damage of blackholing them is probably unacceptable? Cheers Mark.

1 0

JobSpam
by Richard Nelson 17 Oct '07

17 Oct '07

If you are tired of the attractions of the real world, burdened by responsibility and overpaid or just need to move to Hamilton before the V8s get here then you will be pleased to learn that WAND are looking for a Research Fellow. see http://www.waikato.ac.nz/hrm/vacancies/270292.shtml Richard.

1 0

Emails to xtra addresses not being delivered
by Vaughan Chetwynd 16 Oct '07

16 Oct '07

My server generates emails for about 150 members of a choir. 30 of these have xtra addresses, and since the change to yahoo, these are not being delivered. All other addresses work OK. The xtra addresses were OK before the yahoo bubble started up. I receive no notification of non delivery. Can anybody tell me what I need to do to get these emails accepted by the xtra servers? Vaughan Chetwynd 968c Tauwhare Road RD4 Hamilton phone 07 824 0983 mobile 0275 657 724

2 1

Re: [nznog] Citylink problems?
by Anton Smith 16 Oct '07

16 Oct '07

Simon wrote: > I'll do a more in depth explanation tomorrow. Essentially, this started > happening, on every interswitch trunk on most switches on the network: > > Oct 6 14:09:07: %ETHCNTR-3-LOOP_BACK_DETECTED: Keepalive packet loop-back > detected on FastEthernet0/24. > Oct 6 14:09:07: %PM-4-ERR_DISABLE: loopback error detected on Fa0/24, > putting Fa0/24 in err-disable state Oct 6 14:09:08: %LINEPROTO-5-UPDOWN: > Line protocol on Interface FastEthernet0/24, changed state to down Oct 6 > 14:09:09: %LINK-3-UPDOWN: Interface FastEthernet0/24, changed state to down > Oct 6 14:09:50: %PM-4-ERR_RECOVER: Attempting to recover from loopback > err-disable state on Fa0/24 Oct 6 14:09:55: %LINK-3-UPDOWN: Interface > FastEthernet0/24, changed state to up Oct 6 14:09:57: %LINEPROTO-5-UPDOWN: > Line protocol on Interface FastEthernet0/24, changed state to up Oct 6 > 14:09:57: %ETHCNTR-3-LOOP_BACK_DETECTED: Keepalive packet loop-back detected > on FastEthernet0/24. Any further word on the more in depth explanation? Interested from both a customer perspective and a technical perspective - good to learn from these things. Regards, Anton

3 2

NZRR Route Registry Update
by NZRR Database Notifications 15 Oct '07

15 Oct '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS24005 descr: advertised to AS9560 by SafeNZ Networks - AS24005 members: 202.56.32.0/20^20-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.167.254.0/23^23-29, 202.50.252.0/24^24-29, 203.97.6.0/24^24-29, 203.98.6.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061026 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS24005 descr: advertised to AS9560 by SafeNZ Networks Limited - AS24005 members: 124.155.224.0/20^20-29, 202.170.160.0/20^20-29, 203.167.254.0/23^23-29, 202.50.252.0/24^24-29, 203.97.6.0/24^24-29, 203.98.6.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071016 source: NZRR ------------------------------------------------------------

1 0

NZRR Route Registry Update
by NZRR Database Notifications 15 Oct '07

15 Oct '07

Dear Colleague, This is to notify you that one or more objects in which you are designated for notification have been modified in the NZRR routing registry database. These objects are used to configure the various NZIX route servers (http://nzix.net/) so you can expect the relevant servers to be reloaded in the near future. The reloading of the servers is staggered over a period of time so that if you are peering with both servers at an exchange, you can maintain at least one BGP session at all times and consequently a full set of routes. Diagnostic output: ------------------------------------------------------------ --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS24005 descr: advertised to AS9439 by SafeNZ Networks - AS24005 members: 202.56.32.0/20^20-29, 202.56.48.0/21^21-29, 202.137.240.0/21^21-29, 202.170.160.0/21^21-29, 203.167.254.0/23^23-29, 202.50.252.0/24^24-29, 203.97.6.0/24^24-29, 203.98.6.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20061026 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS24005 descr: advertised to AS9439 by SafeNZ Networks Limited - AS24005 members: 124.155.224.0/20^20-29, 202.170.160.0/20^20-29, 203.167.254.0/23^23-29, 202.50.252.0/24^24-29, 203.97.6.0/24^24-29, 203.98.6.0/24^24-29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: tonyw(a)tonyw.com mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20071016 source: NZRR ------------------------------------------------------------

1 0

Dunedin 5.8GHz
by Stewart Fleming 13 Oct '07

13 Oct '07

Anyone changed anything in Dunedin in ISM band? We're seeing severe operational problems with interference in North Dunedin facing south on channels 5836 (both H and V) and 5736 (H and V). Issue started this morning around 10am and ongoing. -- -- Tel: 03 474 2100 Cell: 021 993 125 Web: www.wic.co.nz Co-location and Web hosting. Dunedin-wide wireless. Independent Internet Service Provider.

2 1

Linkedin NZNOG group
by Simon Lyall 13 Oct '07

13 Oct '07

Please Ignore if you don't use Linkedin Linkedin is "a business-oriented social networking site, mainly used for professional networking" [1] . See the the website http://www.linkedin.com for more details. Anyway since there seem to be a lot of NZNOG people there and they have recently allowed the creation of groups I have added a "NZNOG" group. To join go to the URL below ( No doubt it complains if you are not a member). http://www.linkedin.com/e/gis/37382/36D4B725B06C It'll send me an email and I can then add you. [1] - I think this means it helps you get cool jobs making lots of money. So far I've just been adding people into my network, however if you *do* have a cool job paying lots of money... ;) -- Simon J. Lyall | Very Busy | Web: http://www.darkmere.gen.nz/ "To stay awake all night adds a day to your life" - Stilgar | eMT.

1 0