Re: Yahoo's DMARC policy sucks

[Bryan O'Neal]

Worked for a home building. Our servers probably did not push more the 10k
emails a month and I had to write scripts to fill out and submit the Yahoo
"I promise this is not spam" forms. For crying out laud the spf records
(which Yahoo refuses to recognize unless it is a txt record) never changed,
etc, etc, etc. And Lord help you if your mail server ip changes!
:/
On Apr 12, 2014 11:11 PM, "der.hans"  wrote:

> Am 12. Apr, 2014 schwätzte Brian Cluff so:
>
> moin moin,
>
> yeah, tryіng to send legitimate email to Yahoo is a pain.
>
> At a previous company we were regularly sending email to our users ( tens
> of millions of customers ). Yahoo mail servers caused at least half our
> refusals even though no where near half our customers were using Yahoo
> accounts.
>
> Yahoo was also the hardest company of the biggest providers to work with.
> Granted, some companies were easy because my boss knew mail administrators
> at the company. Yahoo was still a pain.
>
> ciao,
>
> der.hans
>
>  Thanks to some changes at yahoo, people that were subscribed to the plug
>> mailing lists and probably wanted to continue to receive PLUG email are
>> dropping off the list like flies due to their messages from the list being
>> rejected.
>>
>> Obviously this message won't reach the people who are being dropped from
>> the list, but if anyone runs into someone that says that haven't been
>> getting new emails, you can tell them that they need to switch providers
>> because yahoo and any other domain that is hosted by yahoo will no longer
>> accept plug emails.
>>
>> I'll try to archive the bounce notifications and if yahoo changes their
>> policy, I'll manually resubscribe anyone that gets dropped.  Until then we
>> have to assume that this change is permanent.
>>
>> Brian Cluff
>> ---
>> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
>> To subscribe, unsubscribe, or to change your mail settings:
>> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>>
>>
> --
> #  http://www.LuftHans.com/http://www.LuftHans.com/Classes/
> #  "Science is like sex: sometimes something useful comes out, but
> #  that is not the reason we are doing it." -- Richard Feynman
> ---
> PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
> To subscribe, unsubscribe, or to change your mail settings:
> http://lists.phxlinux.org/mailman/listinfo/plug-discuss
>
---
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss

Re: Yahoo's DMARC policy sucks

[der.hans]

Am 12. Apr, 2014 schwätzte Brian Cluff so:

moin moin,

yeah, tryіng to send legitimate email to Yahoo is a pain.

At a previous company we were regularly sending email to our users ( tens
of millions of customers ). Yahoo mail servers caused at least half our
refusals even though no where near half our customers were using Yahoo
accounts.

Yahoo was also the hardest company of the biggest providers to work with.
Granted, some companies were easy because my boss knew mail administrators
at the company. Yahoo was still a pain.

ciao,

der.hans

Thanks to some changes at yahoo, people that were subscribed to the plug 
mailing lists and probably wanted to continue to receive PLUG email are 
dropping off the list like flies due to their messages from the list being 
rejected.


Obviously this message won't reach the people who are being dropped from the 
list, but if anyone runs into someone that says that haven't been getting new 
emails, you can tell them that they need to switch providers because yahoo 
and any other domain that is hosted by yahoo will no longer accept plug 
emails.


I'll try to archive the bounce notifications and if yahoo changes their 
policy, I'll manually resubscribe anyone that gets dropped.  Until then we 
have to assume that this change is permanent.


Brian Cluff
---
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss



--
#  http://www.LuftHans.com/http://www.LuftHans.com/Classes/
#  "Science is like sex: sometimes something useful comes out, but
#  that is not the reason we are doing it." -- Richard Feynman---
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss

Re: Is my hard drive hosed?

[Stephen Partington]

spin right is awesome, but i would clone the drive asap an run some
hardware diagnostics.
On Apr 12, 2014 7:27 PM, "Sean Brown"  wrote:

> I would check out a product called Spin Right by Steve Gibson.
>
> Thanks,
>
> Sean Brown
>
> > On Apr 12, 2014, at 7:14 PM, Mark Phillips 
> wrote:
> >
> > I have been having some issues lately on an older server.just found
> this in dmesg with I realized the file system was read only
> >
> > [ 1295.874963] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > [ 1295.875032] ata4.00: BMDMA stat 0x5
> > [ 1295.875084] ata4.00: failed command: READ DMA
> > [ 1295.875139] ata4.00: cmd c8/00:08:08:0b:98/00:00:00:00:00/e3 tag 0
> dma 4096 in
> > [ 1295.875141]  res 51/40:00:0e:0b:98/00:00:00:00:00/e3 Emask
> 0x9 (media error)
> > [ 1295.875266] ata4.00: status: { DRDY ERR }
> > [ 1295.875315] ata4.00: error: { UNC }
> > [ 1295.896422] ata4.00: configured for UDMA/100
> > [ 1295.912627] ata4.01: configured for UDMA/133
> > [ 1295.912645] ata4: EH complete
> > [ 1299.838082] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > [ 1299.838142] ata4.00: BMDMA stat 0x5
> > [ 1299.838192] ata4.00: failed command: READ DMA
> > [ 1299.838248] ata4.00: cmd c8/00:08:08:0b:98/00:00:00:00:00/e3 tag 0
> dma 4096 in
> > [ 1299.838250]  res 51/40:00:0e:0b:98/00:00:00:00:00/e3 Emask
> 0x9 (media error)
> > [ 1299.838375] ata4.00: status: { DRDY ERR }
> > [ 1299.838424] ata4.00: error: { UNC }
> > [ 1299.860448] ata4.00: configured for UDMA/100
> > [ 1299.876673] ata4.01: configured for UDMA/133
> > [ 1299.876696] ata4: EH complete
> > [ 1303.856909] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > [ 1303.856967] ata4.00: BMDMA stat 0x5
> > [ 1303.857018] ata4.00: failed command: READ DMA
> > [ 1303.857074] ata4.00: cmd c8/00:08:08:0b:98/00:00:00:00:00/e3 tag 0
> dma 4096 in
> > [ 1303.857076]  res 51/40:00:0e:0b:98/00:00:00:00:00/e3 Emask
> 0x9 (media error)
> > [ 1303.857201] ata4.00: status: { DRDY ERR }
> > [ 1303.857250] ata4.00: error: { UNC }
> > [ 1303.880448] ata4.00: configured for UDMA/100
> > [ 1303.896764] ata4.01: configured for UDMA/133
> > [ 1303.896786] ata4: EH complete
> > [ 1307.865671] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > [ 1307.865730] ata4.00: BMDMA stat 0x5
> > [ 1307.865781] ata4.00: failed command: READ DMA
> > [ 1307.865836] ata4.00: cmd c8/00:08:08:0b:98/00:00:00:00:00/e3 tag 0
> dma 4096 in
> > [ 1307.865838]  res 51/40:00:0e:0b:98/00:00:00:00:00/e3 Emask
> 0x9 (media error)
> > [ 1307.865962] ata4.00: status: { DRDY ERR }
> > [ 1307.866011] ata4.00: error: { UNC }
> > [ 1307.888427] ata4.00: configured for UDMA/100
> > [ 1307.904843] ata4.01: configured for UDMA/133
> > [ 1307.904866] ata4: EH complete
> > [ 1311.791898] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > [ 1311.791957] ata4.00: BMDMA stat 0x5
> > [ 1311.792018] ata4.00: failed command: READ DMA
> > [ 1311.792074] ata4.00: cmd c8/00:08:08:0b:98/00:00:00:00:00/e3 tag 0
> dma 4096 in
> > [ 1311.792075]  res 51/40:00:0e:0b:98/00:00:00:00:00/e3 Emask
> 0x9 (media error)
> > [ 1311.792198] ata4.00: status: { DRDY ERR }
> > [ 1311.792247] ata4.00: error: { UNC }
> > [ 1311.816427] ata4.00: configured for UDMA/100
> > [ 1311.832872] ata4.01: configured for UDMA/133
> > [ 1311.832893] ata4: EH complete
> > [ 1315.745297] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> > [ 1315.745356] ata4.00: BMDMA stat 0x5
> > [ 1315.745407] ata4.00: failed command: READ DMA
> > [ 1315.745462] ata4.00: cmd c8/00:08:08:0b:98/00:00:00:00:00/e3 tag 0
> dma 4096 in
> > [ 1315.745464]  res 51/40:00:0e:0b:98/00:00:00:00:00/e3 Emask
> 0x9 (media error)
> > [ 1315.745588] ata4.00: status: { DRDY ERR }
> > [ 1315.745637] ata4.00: error: { UNC }
> > [ 1315.768422] ata4.00: configured for UDMA/100
> > [ 1315.784891] ata4.01: configured for UDMA/133
> > [ 1315.784914] sd 3:0:0:0: [sda] Unhandled sense code
> > [ 1315.784917] sd 3:0:0:0: [sda] Result: hostbyte=DID_OK
> driverbyte=DRIVER_SENSE
> > [ 1315.784921] sd 3:0:0:0: [sda] Sense Key : Medium Error [current]
> [descriptor]
> > [ 1315.784928] Descriptor sense data with sense descriptors (in hex):
> > [ 1315.784930] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
> > [ 1315.784941] 03 98 0b 0e
> > [ 1315.784946] sd 3:0:0:0: [sda] Add. Sense: Unrecovered read error -
> auto reallocate failed
> > [ 1315.784954] sd 3:0:0:0: [sda] CDB: Read(10): 28 00 03 98 0b 08 00 00
> 08 00
> > [ 1315.784965] end_request: I/O error, dev sda, sector 60295950
> > [ 1315.785044] ata4: EH complete
> > [ 1315.785068] EXT3-fs error (device sda1): ext3_get_inode_loc: unable
> to read inode block - inode=1885681, block=7536737
> > [ 1315.785203] Aborting journal on device sda1.
> > [ 1315.785860] Remounting filesystem read-only
> > [ 1315.895542] EXT3-fs error (device sda1) in ext3_new_blocks: Journal
> has aborted
> > [ 1315.895634] EXT3-fs error (device s

Re: Yahoo's DMARC policy sucks

[Brian Cluff]

We run our own mailing list servers so it definitely can't be blamed on 
a for profit entity.  Our mailing list should happy send you emails 
forever whether or not you read them until you unsubscribe or get kicked 
off the list due to excessive messages bouncing due to your email 
provider rejecting them.


This is what is happening:
http://www.ietf.org/mail-archive/web/ietf/current/msg87153.html

Brian Cluff

On 04/12/2014 03:46 PM, keith smith wrote:

I have a Yahoo email account and I got this several hours ago.

Your membership in the mailing list PLUG-discuss has been disabled due
to excessive bounces The last bounce received from you was dated
12-Apr-2014.  You will not get any more messages from this list until
you re-enable your membership.  You will receive 3 more reminders like
this before your membership in the list is deleted.

I guess Yahoo is treating PLUG as spam.

The newsletter folks like iContact are having to deal with Yahoo, Gmail,
HotMail. etc bouncing emails if the recipient does not open a
certain number of emails they signed up to get.  Must be a profit thing.

I do not read every plug post so maybe that is what happened to me.

Keith Smith
On Saturday, April 12, 2014 1:56 PM, Brian Cluff  wrote:
Thanks to some changes at yahoo, people that were subscribed to the plug
mailing lists and probably wanted to continue to receive PLUG email are
dropping off the list like flies due to their messages from the list
being rejected.

Obviously this message won't reach the people who are being dropped from
the list, but if anyone runs into someone that says that haven't been
getting new emails, you can tell them that they need to switch providers
because yahoo and any other domain that is hosted by yahoo will no
longer accept plug emails.

I'll try to archive the bounce notifications and if yahoo changes their
policy, I'll manually resubscribe anyone that gets dropped.  Until then
we have to assume that this change is permanent.

Brian Cluff
---
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org

To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss




---
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss



---
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss

Re: Is my hard drive hosed?

[Sean Brown]

I would check out a product called Spin Right by Steve Gibson. 

Thanks,

Sean Brown

> On Apr 12, 2014, at 7:14 PM, Mark Phillips  wrote:
> 
> I have been having some issues lately on an older server.just found this 
> in dmesg with I realized the file system was read only
> 
> [ 1295.874963] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> [ 1295.875032] ata4.00: BMDMA stat 0x5
> [ 1295.875084] ata4.00: failed command: READ DMA
> [ 1295.875139] ata4.00: cmd c8/00:08:08:0b:98/00:00:00:00:00/e3 tag 0 dma 
> 4096 in
> [ 1295.875141]  res 51/40:00:0e:0b:98/00:00:00:00:00/e3 Emask 0x9 
> (media error)
> [ 1295.875266] ata4.00: status: { DRDY ERR }
> [ 1295.875315] ata4.00: error: { UNC }
> [ 1295.896422] ata4.00: configured for UDMA/100
> [ 1295.912627] ata4.01: configured for UDMA/133
> [ 1295.912645] ata4: EH complete
> [ 1299.838082] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> [ 1299.838142] ata4.00: BMDMA stat 0x5
> [ 1299.838192] ata4.00: failed command: READ DMA
> [ 1299.838248] ata4.00: cmd c8/00:08:08:0b:98/00:00:00:00:00/e3 tag 0 dma 
> 4096 in
> [ 1299.838250]  res 51/40:00:0e:0b:98/00:00:00:00:00/e3 Emask 0x9 
> (media error)
> [ 1299.838375] ata4.00: status: { DRDY ERR }
> [ 1299.838424] ata4.00: error: { UNC }
> [ 1299.860448] ata4.00: configured for UDMA/100
> [ 1299.876673] ata4.01: configured for UDMA/133
> [ 1299.876696] ata4: EH complete
> [ 1303.856909] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> [ 1303.856967] ata4.00: BMDMA stat 0x5
> [ 1303.857018] ata4.00: failed command: READ DMA
> [ 1303.857074] ata4.00: cmd c8/00:08:08:0b:98/00:00:00:00:00/e3 tag 0 dma 
> 4096 in
> [ 1303.857076]  res 51/40:00:0e:0b:98/00:00:00:00:00/e3 Emask 0x9 
> (media error)
> [ 1303.857201] ata4.00: status: { DRDY ERR }
> [ 1303.857250] ata4.00: error: { UNC }
> [ 1303.880448] ata4.00: configured for UDMA/100
> [ 1303.896764] ata4.01: configured for UDMA/133
> [ 1303.896786] ata4: EH complete
> [ 1307.865671] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> [ 1307.865730] ata4.00: BMDMA stat 0x5
> [ 1307.865781] ata4.00: failed command: READ DMA
> [ 1307.865836] ata4.00: cmd c8/00:08:08:0b:98/00:00:00:00:00/e3 tag 0 dma 
> 4096 in
> [ 1307.865838]  res 51/40:00:0e:0b:98/00:00:00:00:00/e3 Emask 0x9 
> (media error)
> [ 1307.865962] ata4.00: status: { DRDY ERR }
> [ 1307.866011] ata4.00: error: { UNC }
> [ 1307.888427] ata4.00: configured for UDMA/100
> [ 1307.904843] ata4.01: configured for UDMA/133
> [ 1307.904866] ata4: EH complete
> [ 1311.791898] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> [ 1311.791957] ata4.00: BMDMA stat 0x5
> [ 1311.792018] ata4.00: failed command: READ DMA
> [ 1311.792074] ata4.00: cmd c8/00:08:08:0b:98/00:00:00:00:00/e3 tag 0 dma 
> 4096 in
> [ 1311.792075]  res 51/40:00:0e:0b:98/00:00:00:00:00/e3 Emask 0x9 
> (media error)
> [ 1311.792198] ata4.00: status: { DRDY ERR }
> [ 1311.792247] ata4.00: error: { UNC }
> [ 1311.816427] ata4.00: configured for UDMA/100
> [ 1311.832872] ata4.01: configured for UDMA/133
> [ 1311.832893] ata4: EH complete
> [ 1315.745297] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
> [ 1315.745356] ata4.00: BMDMA stat 0x5
> [ 1315.745407] ata4.00: failed command: READ DMA
> [ 1315.745462] ata4.00: cmd c8/00:08:08:0b:98/00:00:00:00:00/e3 tag 0 dma 
> 4096 in
> [ 1315.745464]  res 51/40:00:0e:0b:98/00:00:00:00:00/e3 Emask 0x9 
> (media error)
> [ 1315.745588] ata4.00: status: { DRDY ERR }
> [ 1315.745637] ata4.00: error: { UNC }
> [ 1315.768422] ata4.00: configured for UDMA/100
> [ 1315.784891] ata4.01: configured for UDMA/133
> [ 1315.784914] sd 3:0:0:0: [sda] Unhandled sense code
> [ 1315.784917] sd 3:0:0:0: [sda] Result: hostbyte=DID_OK 
> driverbyte=DRIVER_SENSE
> [ 1315.784921] sd 3:0:0:0: [sda] Sense Key : Medium Error [current] 
> [descriptor]
> [ 1315.784928] Descriptor sense data with sense descriptors (in hex):
> [ 1315.784930] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00 
> [ 1315.784941] 03 98 0b 0e 
> [ 1315.784946] sd 3:0:0:0: [sda] Add. Sense: Unrecovered read error - auto 
> reallocate failed
> [ 1315.784954] sd 3:0:0:0: [sda] CDB: Read(10): 28 00 03 98 0b 08 00 00 08 00
> [ 1315.784965] end_request: I/O error, dev sda, sector 60295950
> [ 1315.785044] ata4: EH complete
> [ 1315.785068] EXT3-fs error (device sda1): ext3_get_inode_loc: unable to 
> read inode block - inode=1885681, block=7536737
> [ 1315.785203] Aborting journal on device sda1.
> [ 1315.785860] Remounting filesystem read-only
> [ 1315.895542] EXT3-fs error (device sda1) in ext3_new_blocks: Journal has 
> aborted
> [ 1315.895634] EXT3-fs error (device sda1) in ext3_orphan_add: Journal has 
> aborted
> [ 1316.207259] EXT3-fs error (device sda1) in ext3_reserve_inode_write: IO 
> failure
> [ 1316.207328] EXT3-fs error (device sda1) in ext3_new_inode: IO failure
> [ 1316.207386] EXT3-fs error (device sda1) in start_transaction: Journ

Is my hard drive hosed?

[Mark Phillips]

I have been having some issues lately on an older server.just found
this in dmesg with I realized the file system was read only

[ 1295.874963] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 1295.875032] ata4.00: BMDMA stat 0x5
[ 1295.875084] ata4.00: failed command: READ DMA
[ 1295.875139] ata4.00: cmd c8/00:08:08:0b:98/00:00:00:00:00/e3 tag 0 dma
4096 in
[ 1295.875141]  res 51/40:00:0e:0b:98/00:00:00:00:00/e3 Emask 0x9
(media error)
[ 1295.875266] ata4.00: status: { DRDY ERR }
[ 1295.875315] ata4.00: error: { UNC }
[ 1295.896422] ata4.00: configured for UDMA/100
[ 1295.912627] ata4.01: configured for UDMA/133
[ 1295.912645] ata4: EH complete
[ 1299.838082] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 1299.838142] ata4.00: BMDMA stat 0x5
[ 1299.838192] ata4.00: failed command: READ DMA
[ 1299.838248] ata4.00: cmd c8/00:08:08:0b:98/00:00:00:00:00/e3 tag 0 dma
4096 in
[ 1299.838250]  res 51/40:00:0e:0b:98/00:00:00:00:00/e3 Emask 0x9
(media error)
[ 1299.838375] ata4.00: status: { DRDY ERR }
[ 1299.838424] ata4.00: error: { UNC }
[ 1299.860448] ata4.00: configured for UDMA/100
[ 1299.876673] ata4.01: configured for UDMA/133
[ 1299.876696] ata4: EH complete
[ 1303.856909] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 1303.856967] ata4.00: BMDMA stat 0x5
[ 1303.857018] ata4.00: failed command: READ DMA
[ 1303.857074] ata4.00: cmd c8/00:08:08:0b:98/00:00:00:00:00/e3 tag 0 dma
4096 in
[ 1303.857076]  res 51/40:00:0e:0b:98/00:00:00:00:00/e3 Emask 0x9
(media error)
[ 1303.857201] ata4.00: status: { DRDY ERR }
[ 1303.857250] ata4.00: error: { UNC }
[ 1303.880448] ata4.00: configured for UDMA/100
[ 1303.896764] ata4.01: configured for UDMA/133
[ 1303.896786] ata4: EH complete
[ 1307.865671] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 1307.865730] ata4.00: BMDMA stat 0x5
[ 1307.865781] ata4.00: failed command: READ DMA
[ 1307.865836] ata4.00: cmd c8/00:08:08:0b:98/00:00:00:00:00/e3 tag 0 dma
4096 in
[ 1307.865838]  res 51/40:00:0e:0b:98/00:00:00:00:00/e3 Emask 0x9
(media error)
[ 1307.865962] ata4.00: status: { DRDY ERR }
[ 1307.866011] ata4.00: error: { UNC }
[ 1307.888427] ata4.00: configured for UDMA/100
[ 1307.904843] ata4.01: configured for UDMA/133
[ 1307.904866] ata4: EH complete
[ 1311.791898] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 1311.791957] ata4.00: BMDMA stat 0x5
[ 1311.792018] ata4.00: failed command: READ DMA
[ 1311.792074] ata4.00: cmd c8/00:08:08:0b:98/00:00:00:00:00/e3 tag 0 dma
4096 in
[ 1311.792075]  res 51/40:00:0e:0b:98/00:00:00:00:00/e3 Emask 0x9
(media error)
[ 1311.792198] ata4.00: status: { DRDY ERR }
[ 1311.792247] ata4.00: error: { UNC }
[ 1311.816427] ata4.00: configured for UDMA/100
[ 1311.832872] ata4.01: configured for UDMA/133
[ 1311.832893] ata4: EH complete
[ 1315.745297] ata4.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x0
[ 1315.745356] ata4.00: BMDMA stat 0x5
[ 1315.745407] ata4.00: failed command: READ DMA
[ 1315.745462] ata4.00: cmd c8/00:08:08:0b:98/00:00:00:00:00/e3 tag 0 dma
4096 in
[ 1315.745464]  res 51/40:00:0e:0b:98/00:00:00:00:00/e3 Emask 0x9
(media error)
[ 1315.745588] ata4.00: status: { DRDY ERR }
[ 1315.745637] ata4.00: error: { UNC }
[ 1315.768422] ata4.00: configured for UDMA/100
[ 1315.784891] ata4.01: configured for UDMA/133
[ 1315.784914] sd 3:0:0:0: [sda] Unhandled sense code
[ 1315.784917] sd 3:0:0:0: [sda] Result: hostbyte=DID_OK
driverbyte=DRIVER_SENSE
[ 1315.784921] sd 3:0:0:0: [sda] Sense Key : Medium Error [current]
[descriptor]
[ 1315.784928] Descriptor sense data with sense descriptors (in hex):
[ 1315.784930] 72 03 11 04 00 00 00 0c 00 0a 80 00 00 00 00 00
[ 1315.784941] 03 98 0b 0e
[ 1315.784946] sd 3:0:0:0: [sda] Add. Sense: Unrecovered read error - auto
reallocate failed
[ 1315.784954] sd 3:0:0:0: [sda] CDB: Read(10): 28 00 03 98 0b 08 00 00 08
00
[ 1315.784965] end_request: I/O error, dev sda, sector 60295950
[ 1315.785044] ata4: EH complete
[ 1315.785068] EXT3-fs error (device sda1): ext3_get_inode_loc: unable to
read inode block - inode=1885681, block=7536737
[ 1315.785203] Aborting journal on device sda1.
[ 1315.785860] Remounting filesystem read-only
[ 1315.895542] EXT3-fs error (device sda1) in ext3_new_blocks: Journal has
aborted
[ 1315.895634] EXT3-fs error (device sda1) in ext3_orphan_add: Journal has
aborted
[ 1316.207259] EXT3-fs error (device sda1) in ext3_reserve_inode_write: IO
failure
[ 1316.207328] EXT3-fs error (device sda1) in ext3_new_inode: IO failure
[ 1316.207386] EXT3-fs error (device sda1) in start_transaction: Journal
has aborted
[ 1316.207460] EXT3-fs error (device sda1) in ext3_create: IO failure


Any suggestions on how to pull off the important data before too late?

Thanks,

Mark
---
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxl

Re: Yahoo's DMARC policy sucks

[keith smith]

I have a Yahoo email account and I got this several hours ago.

Your membership in the mailing list PLUG-discuss has been disabled due
to excessive bounces The last bounce received from you was dated
12-Apr-2014.  You will not get any more messages from this list until
you re-enable your membership.  You will receive 3 more reminders like
this before your membership in the list is deleted.


I guess Yahoo is treating PLUG as spam.

The newsletter folks like iContact are having to deal with Yahoo, Gmail, 
HotMail. etc bouncing emails if the recipient does not open a certain 
number of emails they signed up to get.  Must be a profit thing.

I do not read every plug post so maybe that is what happened to me.  

 

Keith Smith
On Saturday, April 12, 2014 1:56 PM, Brian Cluff  wrote:
 
Thanks to some changes at yahoo, people that were subscribed to the plug 
mailing lists and probably wanted to continue to receive PLUG email are 
dropping off the list like flies due to their messages from the list 
being rejected.

Obviously this message won't reach the people who are being dropped from 
the list, but if anyone runs into someone that says that haven't been 
getting new emails, you can tell them that they need to switch providers 
because yahoo and any other domain that is hosted by yahoo will no 
longer accept plug emails.

I'll try to archive the bounce notifications and if yahoo changes their 
policy, I'll manually resubscribe anyone that gets dropped.  Until then 
we have to assume that this change is permanent.

Brian Cluff
---
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss---
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss

Yahoo's DMARC policy sucks

[Brian Cluff]

Thanks to some changes at yahoo, people that were subscribed to the plug 
mailing lists and probably wanted to continue to receive PLUG email are 
dropping off the list like flies due to their messages from the list 
being rejected.


Obviously this message won't reach the people who are being dropped from 
the list, but if anyone runs into someone that says that haven't been 
getting new emails, you can tell them that they need to switch providers 
because yahoo and any other domain that is hosted by yahoo will no 
longer accept plug emails.


I'll try to archive the bounce notifications and if yahoo changes their 
policy, I'll manually resubscribe anyone that gets dropped.  Until then 
we have to assume that this change is permanent.


Brian Cluff
---
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss

RE: PLUG-discuss Digest, Vol 106, Issue 12

[Daniel Montagnese]

Those are good.

-Original Message-
From: plug-discuss-boun...@lists.phxlinux.org
[mailto:plug-discuss-boun...@lists.phxlinux.org] On Behalf Of
plug-discuss-requ...@lists.phxlinux.org
Sent: Saturday, April 12, 2014 12:00 PM
To: plug-discuss@lists.phxlinux.org
Subject: PLUG-discuss Digest, Vol 106, Issue 12

Send PLUG-discuss mailing list submissions to
plug-discuss@lists.phxlinux.org

To subscribe or unsubscribe via the World Wide Web, visit
http://lists.phxlinux.org/mailman/listinfo/plug-discuss
or, via email, send a message with subject or body 'help' to
plug-discuss-requ...@lists.phxlinux.org

You can reach the person managing the list at
plug-discuss-ow...@lists.phxlinux.org

When replying, please edit your Subject line so it is more specific than
"Re: Contents of PLUG-discuss digest..."

---
PLUG-discuss mailing list - PLUG-discuss@lists.phxlinux.org
To subscribe, unsubscribe, or to change your mail settings:
http://lists.phxlinux.org/mailman/listinfo/plug-discuss