- NZNOG - lists.nznog.org

JABL announcement: dynablock & Spamhaus PBL
by Craig Whitmore 08 Mar '07

08 Mar '07

This came from the SPAM-L mailing list. If ppl are using RBL's on their mail servers they might want to read below. ------------------------------------------------------------------------- The following text was sent to list(a)njabl.org on Jan 19, 2007. Judging from the number of DNS queries still being handled for dynablock.njabl.org, the message doesn't seem to have made it to a wide enough audience. If you use or know people who use dynablock.njabl.org, this is important information: With the advent of Spamhaus's PBL (http://spamhaus.org/pbl/), dynablock.njabl.org has become obsolete. Rather than maintain separate similar DNSBL zones, NJABL will be working with Spamhaus on the PBL. Effective immediately, dynablock.njabl.org exists as a copy of the Spamhaus PBL. After dynablock users have had ample time to update their configurations, the dynablock.njabl.org zone will be emptied. Other NJABL zones (i.e. dnsbl, combined, bhnc, and the qw versions) will continue, business as usual, except that combined will eventually lose its dynablock component. If you currently use dynablock.njabl.org we recommend you switch immediately to pbl.spamhaus.org. If you currently use combined.njabl.org, we recommend you add pbl.spamhaus.org to the list of DNSBLs you use. You may also want to consider using zen.spamhaus.org, which is a combination zone consisting of Spamhaus's SBL, XBL, and PBL zones. ---------------- Thanks Craig

1 0

Re: [nznog] RFC822 (Identification of sender in email)
by Stoo Brighting 05 Mar '07

05 Mar '07

Hey, if you're going to quote me, at least quote me correctly. I didn't say it was unmonitored, we do monitor all bounces we get in order to process the NDR's (thousands each day) Like I said on the phone, our emails have completely valid envelope fields, and we update our database to "clean" out the bad email addresses that people often like to sign up with. This doesn't break any RFC that I know of. We'd just prefer that you don't reply to our CRM messages via SMTP, that's all - hence the "please do not reply to this" at the bottom of all our outbound emails, and the auto-responder if you do happen to send mail to these addresses. If this breaks an RFC, point me at the appropriate place, and I'll change things to fit them. As for being cocky, I can handle that, I've been called worse. Cheers, Stoo Misc small online company. -----Original Message----- From: John @ netTRUST [mailto:john(a)nettrust.net.nz] Sent: Tuesday, 6 March 2007 2:39 p.m. To: Craig Whitmore; nznog(a)list.waikato.ac.nz Subject: Re: [nznog] RFC822 (Identification of sender in email) I've just had a call from a rather cocky person at the company. They claim it is allright and common. I disagree, with the exception that it is common among spammers*. Hence why I'm asking other NZNOG members. Reply emails go to an auto responder which the company person says is unmonitored. This issue was bought to my attention when I wrote an email to this company, though as we handle (I estimate) several thousand emails per day from this company, I ahve decided to investigate the matter further. *I am in no way suggesting said company is a spammer, but we're under constant pressure from customers to increase the level of 'protection' and looking at their emails, they could quite possibly score a few bayes points. > > In investigating an issue involving a large online NZ company's outbound > > email - I read RFC822 which I have quoted below. > > > > I note that this company is currently making use of apparently > > unmonitored return addresses which generate an auto reply. > > Are you saying they are sending (MFROM) Addresses which don't exist (ie > cannot be bounced back to etc). Or MFROM a valid email address which no one > reads (ie noreply(a)XXXXX) > > Thanks > Craig _______________________________________________ NZNOG mailing list NZNOG(a)list.waikato.ac.nz http://list.waikato.ac.nz/mailman/listinfo/nznog

2 1

Re: [nznog] RFC822 (Identification of sender in email)
by John ＠ netTRUST 05 Mar '07

05 Mar '07

I've just had a call from a rather cocky person at the company. They claim it is allright and common. I disagree, with the exception that it is common among spammers*. Hence why I'm asking other NZNOG members. Reply emails go to an auto responder which the company person says is unmonitored. This issue was bought to my attention when I wrote an email to this company, though as we handle (I estimate) several thousand emails per day from this company, I ahve decided to investigate the matter further. *I am in no way suggesting said company is a spammer, but we're under constant pressure from customers to increase the level of 'protection' and looking at their emails, they could quite possibly score a few bayes points. > > In investigating an issue involving a large online NZ company's outbound > > email - I read RFC822 which I have quoted below. > > > > I note that this company is currently making use of apparently > > unmonitored return addresses which generate an auto reply. > > Are you saying they are sending (MFROM) Addresses which don't exist (ie > cannot be bounced back to etc). Or MFROM a valid email address which no one > reads (ie noreply(a)XXXXX) > > Thanks > Craig

2 1

RFC822 (Identification of sender in email)
by John ＠ netTRUST 05 Mar '07

05 Mar '07

Hello all- In investigating an issue involving a large online NZ company's outbound email - I read RFC822 which I have quoted below. I note that this company is currently making use of apparently unmonitored return addresses which generate an auto reply. Given that my reading of RFC822 would suggest this is contrary to this (and other relevant sections), and the obvious issues that this can cause for spam filtering mechanisms like TMDA, I would like to know whether others find this practice inappropriate, and if so, what action (if any) do they take against the perpetrators? Standard for ARPA Internet Text Messages Since the critical function served by the "Sender" field is identification of the agent responsible for sending mail and since computer programs cannot be held accountable for their behavior, it is strongly recommended that when a computer pro- gram generates a message, the HUMAN who is responsible for that program be referenced as part of the "Sender" field mail- box specification.

3 2

Notification of NZRR Database changes
by NZRR Database Notifications 05 Mar '07

05 Mar '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS64597 descr: advertised to AS9439 by Araneo Limited - AS64597 members: 210.48.101.64/27^27-29, 210.48.109.224/27^27-29, 210.48.101.112/28^28-29, 210.48.101.240/28^28-29, 202.53.189.128/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: info(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20060612 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS64597 descr: advertised to AS9439 by Araneo Limited - AS64597 members: 202.174.160.0/20^20-29, 210.48.101.64/27^27-29, 210.48.109.224/27^27-29, 210.48.101.112/28^28-29, 210.48.101.240/28^28-29, 202.53.189.128/29 admin-c: RPA1-NZRR tech-c: RPA1-NZRR notify: rpsl-admin(a)nzix.net notify: nznog(a)list.waikato.ac.nz notify: noc(a)araneo.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070306 source: NZRR

1 0

APNIC membership fee discussion
by Elly Tawhai 27 Feb '07

27 Feb '07

Hi, I had some lively discussions about the APNIC membership fees with some of the attendees at the last NZnog in Hamilton. If you are an APNIC member, you may be interested in the APNIC fee discussions taking place at the APNIC 23 meeting in Bali this week. I encourage you all to have your say during the fee discussion working group sessions on Thursday and in the APNIC Member Meeting on Friday. Fee discussion sessions at APNIC 23: APNIC fees discussion Thursday 1 March 2007 9:00 - 12:30 (Bali time) http://www.apnic.net/meetings/23/programme/fees.html Fee discussions at the APNIC member meeting Friday 2 March 2007 14:15 - 15:30 (Bali time) http://www.apnic.net/meetings/23/programme/amm.html You can follow and participate in the fee discussions online via: - Jabber chat rooms - Live transcripts - Streaming video - Streaming audio Archives of the audio, video and transcripts will also be available soon after the fee discussion sessions have ended. For more information on how to participate online, go to: http://www.apnic.net/meetings/remote Kind regards, Elly APNIC

1 0

Remote participation in APNIC 23
by Elly Tawhai 26 Feb '07

26 Feb '07

Hi, You may be aware that APNIC 23 has started. You can participate remotely in discussions, ask the presenter questions, and voice your opinion. For more information on webcast, podcast, Jabber chat, and live transcript services please see: http://www.apnic.net/meetings/remote Some of the exciting topics being covered include: * Working group session to discuss a new membership fee structure * IPv4 count down proposal in the policy SIG * The EC election * Announcement of APNIC member survey results, and a review of the APNIC Secretariat new organisational structure * Review of the APNIC voting system For more information about the agenda please see: http://www.apnic.net/meetings/23/programme Kind regards, Elly APNIC

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 25 Feb '07

25 Feb '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.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: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070212 source: NZRR REPLACED BY: route-set: AS9560:RS-ROUTES:AS9503 descr: advertised to AS9560 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070226 source: NZRR

1 0

Notification of NZRR Database changes
by NZRR Database Notifications 25 Feb '07

25 Feb '07

Dear Colleague, This is to notify you that some object(s) in NZRR database which you either maintain or are listed as to-be-notified have been added, deleted or changed. 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. --- PREVIOUS OBJECT: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.50.247.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: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070212 source: NZRR REPLACED BY: route-set: AS9439:RS-ROUTES:AS9503 descr: advertised to AS9439 by FX Networks - AS9503 members: 131.203.0.0/16^16-29, 161.29.0.0/16^16-29, 161.65.0.0/16^16-29, 202.53.176.0/20^20-29, 202.174.160.0/20^20-29, 202.191.32.0/20^20-29, 210.48.160.0/20^20-29, 123.108.144.0/21^21-29, 202.46.176.0/21^21-29, 202.78.240.0/21^21-29, 203.190.208.0/21^21-29, 202.37.48.0/22^22-29, 202.59.4.0/22^22-29, 202.124.106.0/23^23-29, 192.88.85.0/24^24-29, 192.133.31.0/24^24-29, 202.20.97.0/24^24-29, 202.27.208.0/24^24-29, 202.36.119.0/24^24-29, 202.36.183.0/24^24-29, 202.46.190.0/24^24-29, 202.49.106.0/24^24-29, 202.50.247.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: noc-minor(a)fx.net.nz mnt-by: MAINT-NZRR-NZ changed: rpsl-admin(a)nzix.net 20070226 source: NZRR

1 0

Fwd: Online voting open for APNIC Executive Council election
by Elly Tawhai 22 Feb '07

22 Feb '07

Apologies if you have already received this. Begin forwarded message: > From: secretariat(a)apnic.net > Date: 20 February 2007 6:01:47 PM > Subject: Online voting open for APNIC Executive Council election > > Dear colleagues > > Online voting for the APNIC Executive Council election is now open. > > where: https://my.apnic.net/voting > deadline: 9:00am UTC+8 (Bali time) on Wednesday 28 February 2007 > who: Only registered voting contacts may vote online > > Profiles of the candidates nominated for this election, along with > details for other voting methods are at: > > http://www.apnic.net/meetings/23/ec > > If you have any questions, please contact APNIC Secretariat at > helpdesk(a)apnic.net. > > > Regards, > > --------------------------------------------------------------------- > APNIC Secretariat email: secretariat(a)apnic.net > http://www.apnic.net sip: info(a)voip.apnic.net > phone: +61 7 3858 3100 > --------------------------------------------------------------------- > See you at APNIC 23! Bali, Indonesia, 26 February-2 March 2007 > http://www.apnic.net/meetings > --------------------------------------------------------------------- >

1 0