Re: reorder_libs() from /etc/rc when using NFS root FS

[Todd C. Miller]

On Sat, 09 Jul 2016 18:25:08 +0200, Frank Scheiner wrote:

> Running the command substitution alone after the machine has finished 
> booting - which takes a considerable extra amount of time as the 
> SPARCclassic is a slow machine and its root FS is mounted via NFS - 
> gives the following in my case:
> 
> ```
> # stat -L -f '%Sd' /usr/lib
> ??
> # echo $?
> 0
> ```

That makes sense.  What stat(1) actually does is call stat(2) on
/usr/lib and look up the resulting device number using devname(3).
Since it can't be found it returns "??" which is useful for ps but
not much else.

We can simplify the check and simply treat a value of "??" as
non-local and skip the reorder.

 - todd

Index: rc
===
RCS file: /cvs/src/etc/rc,v
retrieving revision 1.485
diff -u -p -u -r1.485 rc
--- rc  29 May 2016 15:36:06 -  1.485
+++ rc  10 Jul 2016 01:35:46 -
@@ -164,8 +164,8 @@ reorder_libs() {
local _dkdev=/dev/$(stat -L -f '%Sd' /usr/lib)
local _mp=$(mount | grep "^$_dkdev")
 
-   # Skip if /usr/lib is on a nfs mounted filesystem.
-   [[ $_mp == *' type nfs '* ]] && return
+   # Skip if /usr/lib is not on a local filesystem.
+   [ $_dkdev == '??' ] && return
 
echo -n 'reordering libraries:'

iwi0 firmware error

[Xianwen Chen]

Hello,

I have not been able to use iwi0 on OpenBSD 5.9 i386 on ThinkPad R52.

The firmware was installed via
# fw_update

When I try to connect to an open wifi network:
# ifconfig iwi0 nwid HUAZHU-Hanting up

I obtain the following error messages when I run 'dmesg':

iwi0: fatal firmware error
iwi0: fatal firmware error
iwi0: timeout waiting for master
iwi0: fatal firmware error
iwi0: timeout waiting for master
iwi0: fatal firmware error
iwi0: timeout waiting for master
iwi0: fatal firmware error
iwi0: timeout waiting for master
iwi0: fatal firmware error
iwi0: fatal firmware error
iwi0: timeout waiting for master
iwi0: fatal firmware error
iwi0: fatal firmware error
iwi0: fatal firmware error

The wireless network adapter worked a few days ago, when the laptop was 
running Windows XP.


What shall I do to make iwi0 working?

Warm regards,

Xianwen

Re: making OpenBSD 5.9 live system on USB key

[Matthias Apitz]

El día Saturday, July 09, 2016 a las 04:16:45PM +0200, Matthias Apitz escribió:

> El día Saturday, July 09, 2016 a las 02:44:39PM +0200, Peter N. M. Hansteen 
> escribió:
> 
> Re/ the touchpad: the imt(4) man page says, it should have support.
> Is there some method in OpenBSD to get verbose or even debug boot
> messages and to verify that the imt(4) driver is in the kernel? I read
> that OpenBSD does not have loadable kernel modules, true?

I compiled a new kernel and booted with verbose, but I do not see any
probing messages for imt or i2c devices, what could I miss?

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Wer übersieht, dass wir uns den anderen weggenommen haben und sie uns 
wiederhaben wollen,
kann von den Kämpfen der letzten Tage keinen verstehen. Und kann natürlich auch 
keinen
dieser Kämpfe bestehen." Hermann Kant in jW 1.10.1989

reorder_libs() from /etc/rc when using NFS root FS

[Frank Scheiner]

Dear folks,

I'm unsure if the following constitutes a bug or if it's due to my local 
configuration, so I mailed to openbsd-misc instead of openbsd-bugs:


I'm running a SPARCclassic (sparc platform) with OpenBSD 6.0-current 
(builddate: 1467664848) served diskless via NFS. To keep things easy I 
don't use different mount points for /usr, /var and others but only one 
for the whole FS plus an extra file for swap space.


The last OpenBSD version I tested with this machine was 5.8-stable. 
During bootup of the mentioned 6.0-current root FS I noticed a long 
delay accompanied by the new (compared to 5.8) message "reordering 
libraries: ". I first assumed this might be done for the first boot only 
(like creating SSH keys), so I rebooted the machine only to recognize 
that it's a persistent action. Searching for the mentioned string I 
found out it originates from the reorder_libs() function in `/etc/rc`.


From the comments in reorder_libs() I see that this is actually not 
intented to run if `/usr/lib` is on a NFS mounted file system - i.e. 
this shouldn't happen in my case. But it looks like the detection does 
not work as intended. The problem seems to be the first of the following 
lines (line 2 and following from reorder_libs() (see [1] for the whole 
`/etc/rc` file)):


```
local _dkdev=/dev/$(stat -L -f '%Sd' /usr/lib)
local _mp=$(mount | grep "^$_dkdev")

# Skip if /usr/lib is on a nfs mounted filesystem.
[[ $_mp == *' type nfs '* ]] && return
```

[1]: 
http://cvsweb.openbsd.org/cgi-bin/cvsweb/src/etc/rc?rev=1.485=text/x-cvsweb-markup


Running the command substitution alone after the machine has finished 
booting - which takes a considerable extra amount of time as the 
SPARCclassic is a slow machine and its root FS is mounted via NFS - 
gives the following in my case:


```
# stat -L -f '%Sd' /usr/lib
??
# echo $?
0
```

The only mounted file systems are:

```
# mount
192.168.178.9:/srv/nfs/sc-1/root on / type nfs (v3, udp, rdirsize=4096, 
timeo=100, retrans=101)
192.168.178.9:/srv/nfs/openbsd/snapshots/1467664848/sparc/sc-1/swap on 
/swap type nfs (v3, udp, timeo=100, retrans=101)

```

So searching for "^/dev/??" in the output of `mount` doesn't succeed and 
the re-linking of the libraries is done anyhow. I'm not sure if the 
output of the `stat` command is due to my local configuration but came 
up with a different solution instead of the line mentioned above:


```
local _dkdev=$(df /usr/lib | tail -1 | cut -d ' ' -f 1)
```

This should give either the device (I cannot check this as I currently 
don't have a machine running OpenBSD from disk, but the first column 
should contain the device in this case AFAIK) or the NFS share where 
`/usr/lib` is located, although it now needs three commands/subshells. 
With the NFS share in the _dkdev variable the _mp variable will get the 
correct line from the output of `mount`, the check if `/usr/lib` is on a 
NFS mounted file system will succeed and the re-linking of the libs will 
be skipped as intended.


Best regards
Frank Scheiner

OpenBSD isakmpd and OS X El Capitan client

[Evgeniy Sudyr]

I'm trying to establish IPSEC tunnel (for future usage with npppd
L2TP) between -snapshot and OS X El Captain 10.11.5 and have issues
when establishing phase1.

I searched in archives and suggestions doesn't work for me. I tried
main/quick combinations from dumps (below), which make sense.

Current config is:

ipsec.conf

ike passive esp proto from x.x.x.x to any port 1701 \
main auth hmac-sha1 enc 3des group modp1024 \
quick auth hmac-sha1 enc 3des \
psk "XXX"


x.x.x.x - openbsd server IP
y.y.y.y - client IP

When connecting in daemon logs:

Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
GROUP_DESCRIPTION: got MODP_2048, expected MODP_3072
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
HASH_ALGORITHM: got SHA2_256, expected SHA
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
ENCRYPTION_ALGORITHM: got AES_CBC, expected 3DES_CBC
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
HASH_ALGORITHM: got SHA2_256, expected SHA
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
HASH_ALGORITHM: got SHA, expected SHA2_256
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
GROUP_DESCRIPTION: got MODP_2048, expected MODP_3072
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
ENCRYPTION_ALGORITHM: got AES_CBC, expected 3DES_CBC
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
GROUP_DESCRIPTION: got MODP_2048, expected MODP_1024
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
HASH_ALGORITHM: got MD5, expected SHA2_256
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
HASH_ALGORITHM: got MD5, expected SHA
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
ENCRYPTION_ALGORITHM: got AES_CBC, expected 3DES_CBC
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
HASH_ALGORITHM: got MD5, expected SHA
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
HASH_ALGORITHM: got SHA2_512, expected SHA2_256
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
HASH_ALGORITHM: got SHA2_512, expected SHA
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
ENCRYPTION_ALGORITHM: got AES_CBC, expected 3DES_CBC
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
HASH_ALGORITHM: got SHA2_512, expected SHA
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
GROUP_DESCRIPTION: got MODP_1536, expected MODP_3072
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
HASH_ALGORITHM: got SHA2_256, expected SHA
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
ENCRYPTION_ALGORITHM: got AES_CBC, expected 3DES_CBC
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
HASH_ALGORITHM: got SHA2_256, expected SHA
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
HASH_ALGORITHM: got SHA, expected SHA2_256
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
GROUP_DESCRIPTION: got MODP_1536, expected MODP_3072
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
ENCRYPTION_ALGORITHM: got AES_CBC, expected 3DES_CBC
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
GROUP_DESCRIPTION: got MODP_1536, expected MODP_1024
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
HASH_ALGORITHM: got MD5, expected SHA2_256
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
HASH_ALGORITHM: got MD5, expected SHA
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
ENCRYPTION_ALGORITHM: got AES_CBC, expected 3DES_CBC
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
HASH_ALGORITHM: got MD5, expected SHA
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
GROUP_DESCRIPTION: got MODP_1024, expected MODP_3072
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
HASH_ALGORITHM: got SHA2_256, expected SHA
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
ENCRYPTION_ALGORITHM: got AES_CBC, expected 3DES_CBC
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
HASH_ALGORITHM: got SHA2_256, expected SHA
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
HASH_ALGORITHM: got SHA, expected SHA2_256
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
GROUP_DESCRIPTION: got MODP_1024, expected MODP_3072
Jul  9 17:25:43 vpn isakmpd[88568]: attribute_unacceptable:
ENCRYPTION_ALGORITHM: got AES_CBC, expected 3DES_CBC
Jul  9 17:25:43 vpn isakmpd[88568]: message_parse_payloads: reserved
field non-zero: 8a
Jul  9 17:25:43 vpn isakmpd[88568]: dropped message from y.y.y.y port
36990 due to notification type PAYLOAD_MALFORMED
Jul  9 17:25:46 vpn isakmpd[88568]: message_parse_payloads: reserved
field non-zero: 8a
Jul  9 17:25:46 vpn isakmpd[88568]: dropped message from y.y.y.y port
36990 due to notification type PAYLOAD_MALFORMED
Jul  9 17:25:49 vpn isakmpd[88568]: message_parse_payloads: reserved
field non-zero: 8a
Jul  9 17:25:49 vpn isakmpd[88568]: dropped message from y.y.y.y port
36990 due to notification type PAYLOAD_MALFORMED
Jul  9 17:25:53 vpn isakmpd[88568]: 

Re: making OpenBSD 5.9 live system on USB key

[Matthias Apitz]

El día Saturday, July 09, 2016 a las 02:44:39PM +0200, Peter N. M. Hansteen 
escribió:

> pci1 at ppb0 bus 1
> "Atheros AR9462" rev 0x01 at pci1 dev 0 function 0 not configured
> 
> - means that for this one at least, you have a variant that 5.9 doesn't
> support. I suspect that's the case with your touchpad as well.

Thanks. I plugged in some other USB Wifi dongle which was seen by
the urtwn(4) driver, learned how to install the firmware and could bring up
the interface associated with my AP.

Re/ the touchpad: the imt(4) man page says, it should have support.
Is there some method in OpenBSD to get verbose or even debug boot
messages and to verify that the imt(4) driver is in the kernel? I read
that OpenBSD does not have loadable kernel modules, true?

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Wer übersieht, dass wir uns den anderen weggenommen haben und sie uns 
wiederhaben wollen,
kann von den Kämpfen der letzten Tage keinen verstehen. Und kann natürlich auch 
keinen
dieser Kämpfe bestehen." Hermann Kant in jW 1.10.1989

Re: making OpenBSD 5.9 live system on USB key

[Peter N. M. Hansteen]

On 07/09/16 14:10, Matthias Apitz wrote:

> Thanks, this did it fine. The system boots fine from the USB key, but I
> do not see anything about the touchpad. As well X11 does not can use the
> mouse. I can imagine that I have to load somehow the driver imt(4), or
> even have to make a custom kernel? I'm attaching the dmesg output.
> 
> Other question is, how I could bring up the ath0 interface. In FreeBSD I
> do use it with the wpa_supplicant methods to associate with my AP. The
> ifconfig does not see the ath0 interface. The netbook has no other NIC.

pci1 at ppb0 bus 1
"Atheros AR9462" rev 0x01 at pci1 dev 0 function 0 not configured

- means that for this one at least, you have a variant that 5.9 doesn't
support. I suspect that's the case with your touchpad as well.

Before trying to build custom kernels, I'd try with a snapshot (they're
6.0-beta at the moment), I remember vaguely some activity on the athn
driver during this cycle.

> Thanks and forgive if this is a FAQ (I do read the FAQ, but could not find
> the answer there).

as long as your hardware is supported, ifconfig is capable of handling
the simpler WPA setups, ie

ifconfig athn0 up nwid foo wpakey foospresharedsecret

but there is a wpa-supplicant package available if you need it.
-- 
Peter N. M. Hansteen, member of the first RFC 1149 implementation team
http://bsdly.blogspot.com/ http://www.bsdly.net/ http://www.nuug.no/
"Remember to set the evil bit on all malicious network traffic"
delilah spamd[29949]: 85.152.224.147: disconnected after 42673 seconds.

Re: making OpenBSD 5.9 live system on USB key

[Matthias Apitz]

El día Friday, July 08, 2016 a las 10:53:56AM -0400, Ted Unangst escribió:

> Matthias Apitz wrote:
> > I'd like to make some bootable USB key which contains an OpenBSD live
> > system, if possible even with X11 included.
> > 
> > Can someone please be so kind and point me to some guide about how to
> > make such live system?
> 
> Just follow the regular install procedure, but install to sd1 or whatever disk
> the USB key is detected as.

Thanks, this did it fine. The system boots fine from the USB key, but I
do not see anything about the touchpad. As well X11 does not can use the
mouse. I can imagine that I have to load somehow the driver imt(4), or
even have to make a custom kernel? I'm attaching the dmesg output.

Other question is, how I could bring up the ath0 interface. In FreeBSD I
do use it with the wpa_supplicant methods to associate with my AP. The
ifconfig does not see the ath0 interface. The netbook has no other NIC.

Thanks and forgive if this is a FAQ (I do read the FAQ, but could not find
the answer there).

matthias

-- 
Matthias Apitz, ✉ g...@unixarea.de, ⌂ http://www.unixarea.de/  ☎ 
+49-176-38902045
"Wer übersieht, dass wir uns den anderen weggenommen haben und sie uns 
wiederhaben wollen,
kann von den Kämpfen der letzten Tage keinen verstehen. Und kann natürlich 
auch keinen
dieser Kämpfe bestehen." Hermann Kant in jW 1.10.1989
OpenBSD 5.9 (GENERIC.MP) #1888: Fri Feb 26 01:20:19 MST 2016
dera...@amd64.openbsd.org:/usr/src/sys/arch/amd64/compile/GENERIC.MP
real mem = 2069331968 (1973MB)
avail mem = 2002411520 (1909MB)
mpath0 at root
scsibus0 at mpath0: 256 targets
mainbus0 at root
bios0 at mainbus0: SMBIOS rev. 2.7 @ 0x7bf82020 (10 entries)
bios0: vendor coreboot version "(null)" date 08/13/2014
bios0: Acer Peppy
acpi0 at bios0: rev 2
acpi0: sleep states S0 S3 S4 S5
acpi0: tables DSDT FACP HPET APIC MCFG SSDT SSDT
acpi0: wakeup devices LID0(S5) TPAD(S3) TSCR(S3) HDEF(S3) EHCI(S3) XHCI(S3)
acpitimer0 at acpi0: 3579545 Hz, 24 bits
acpihpet0 at acpi0: 14318179 Hz
acpimadt0 at acpi0 addr 0xfee0: PC-AT compat
cpu0 at mainbus0: apid 0 (boot processor)
cpu0: Intel(R) Celeron(R) 2955U @ 1.40GHz, 1397.00 MHz
cpu0: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,XSAVE,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,ERMS,INVPCID,SENSOR,ARAT
cpu0: 256KB 64b/line 8-way L2 cache
cpu0: smt 0, core 0, package 0
mtrr: Pentium Pro MTRR support, 10 var ranges, 88 fixed ranges
cpu0: apic clock running at 99MHz
cpu0: mwait min=64, max=64, C-substates=0.2.1.2.4.1.1.1, IBE
cpu1 at mainbus0: apid 2 (application processor)
cpu1: Intel(R) Celeron(R) 2955U @ 1.40GHz, 1396.77 MHz
cpu1: 
FPU,VME,DE,PSE,TSC,MSR,PAE,MCE,CX8,APIC,SEP,MTRR,PGE,MCA,CMOV,PAT,PSE36,CFLUSH,DS,ACPI,MMX,FXSR,SSE,SSE2,SS,HTT,TM,PBE,SSE3,PCLMUL,DTES64,MWAIT,DS-CPL,VMX,EST,TM2,SSSE3,CX16,xTPR,PDCM,PCID,SSE4.1,SSE4.2,MOVBE,POPCNT,DEADLINE,XSAVE,RDRAND,NXE,PAGE1GB,LONG,LAHF,ABM,PERF,ITSC,FSGSBASE,ERMS,INVPCID,SENSOR,ARAT
cpu1: 256KB 64b/line 8-way L2 cache
cpu1: smt 0, core 1, package 0
ioapic0 at mainbus0: apid 2 pa 0xfec0, version 20, 40 pins
acpimcfg0 at acpi0 addr 0xf000, bus 0-63
acpiprt0 at acpi0: bus 0 (PCI0)
acpiprt1 at acpi0: bus 1 (RP01)
acpiprt2 at acpi0: bus -1 (RP02)
acpiprt3 at acpi0: bus -1 (RP03)
acpiprt4 at acpi0: bus -1 (RP04)
acpiprt5 at acpi0: bus -1 (RP05)
acpiprt6 at acpi0: bus -1 (RP06)
acpiprt7 at acpi0: bus -1 (RP07)
acpiprt8 at acpi0: bus -1 (RP08)
acpiec0 at acpi0
acpicpu0 at acpi0: C3(700@148 mwait.1@0x33), C2(900@67 mwait.1@0x10), C1(1000@0 
mwait.1@0x1), PSS
acpicpu1 at acpi0: C3(700@148 mwait.1@0x33), C2(900@67 mwait.1@0x10), C1(1000@0 
mwait.1@0x1), PSS
acpitz0 at acpi0: critical temperature is 99 degC
acpipwrres0 at acpi0: TNP0, resource for TDP0
acpipwrres1 at acpi0: TNP1, resource for TDP1
acpibtn0 at acpi0: LID0
acpibtn1 at acpi0: PWRB
acpibtn2 at acpi0: TPAD
acpibtn3 at acpi0: TSCR
acpiac0 at acpi0: AC unit online
acpibat0 at acpi0: BAT0 model "21168116544393281" serial 943076400 type LION 
oem "32210482396811091"
dwiic at acpi0 not configured
dwiic at acpi0 not configured
acpivideo0 at acpi0: GFX0
cpu0: Enhanced SpeedStep 1397 MHz: speeds: 1400, 1200, 1000, 800 MHz
pci0 at mainbus0 bus 0
pchb0 at pci0 dev 0 function 0 "Intel Core 4G Host" rev 0x09
inteldrm0 at pci0 dev 2 function 0 "Intel HD Graphics" rev 0x09
drm0 at inteldrm0
inteldrm0: msi
inteldrm0: 1366x768
wsdisplay0 at inteldrm0 mux 1: console (std, vt100 emulation)
wsdisplay0: screen 1-5 added (std, vt100 emulation)
azalia0 at pci0 dev 3 function 0 "Intel Core 4G HD Audio" rev 0x09: msi
xhci0 at pci0 dev 20 function 0 "Intel 8 Series xHCI" rev 0x04: msi
usb0 at xhci0: USB revision 3.0
uhub0 at usb0 "Intel xHCI root hub" rev 3.00/1.00 addr 1
vendor "Intel", unknown product 0x9c60 (class system subclass 8237 DMA, rev 
0x04) at pci0 dev 21 

Re: Getting a lot of spam from Gmail,etc. How can I reject those? Can't trap with spamd

[Craig Skinner]

Hi Chris,

On 2016-07-08 Fri 11:10 AM |, Chris Bennett wrote:
> I already have a script with regex's for blacklisting IP's but I am
> getting several repeat spam emails to many of my email addresses, same
> senders, but from Gmail especially.
> 

Is this spam actually coming from Google IP addresses?

Just because a spammer sends with a gmail address,
doesn't mean they are relaying via Gmail's servers.

> I can't blacklist those since gmail has so many MX's, which would
> interfere with good emails too. Gmail probably wouldn't like that
> either.
> 
> Any ideas what I should do?
> 

Report abuse:

$ host 209.85.220.43
43.220.85.209.in-addr.arpa domain name pointer mail-pa0-f43.google.com.
$ nice whois 209.85.220.43 | fgrep -i abuse
OrgAbuseHandle: ABUSE5250-ARIN
OrgAbuseName:   Abuse
OrgAbusePhone:  +1-650-253-
OrgAbuseEmail:  network-ab...@google.com
OrgAbuseRef:https://whois.arin.net/rest/poc/ABUSE5250-ARIN

In this case, foward the full message with full headers to 
network-ab...@google.com

In mutt: hit 'h', then 'f'. Thunderbird & Claws-mail are similar.

The big freemail providers are pretty good at closing crap accounts.

All the best,
-- 
Craig Skinner | http://linkd.in/yGqkv7