[gentoo-user] Re: Bouncing messages

2023-01-28 Thread Nuno Silva
On 2023-01-20, Dr Rainer Woitok wrote:

[...]
> Either these  mail identification numbers  should be somehow visible and
> in particular searchable at
>
>https://archives.gentoo.org/gentoo-user/
>
> or the mail that some mail couldn't be delivered should contain more in-
> formation like author, date and subject.

And Message-ID... at least that one would enable searching for the
specific message in other archives too.

(Also, why is Date different between the actual message and the web
archive under gentoo.org?)

-- 
Nuno Silva




Re: [gentoo-user] Re: Bouncing messages

2023-01-24 Thread Peter Humphrey
On Sunday, 22 January 2023 23:04:43 GMT Michael wrote:

> Or if your ISP offer a webmail front end to their server, it should be
> easier to access the message with a browser.

Useful advice, Michael; thanks.

When I eventually found the right search terms, I went straight to the answer 
I needed [1].

Meanwhile, I used webmail to delete the offending message. I hope the lesson 
has been learnt, but I'll be ready next time if not.   :)

1.  
https://serverfault.com/questions/327416/changing-the-maximum-mail-size-in-postfix

-- 
Regards,
Peter.






Re: [gentoo-user] Re: Bouncing messages

2023-01-22 Thread Michael
On Sunday, 22 January 2023 22:33:50 GMT Peter Humphrey wrote:
> On Thursday, 19 January 2023 09:30:34 GMT I wrote:
> > I'll see it it's my ISP who's bouncing the message.
> 
> It looks as though they did reject the mail. I asked them please to let it
> through just this once, and now it's sitting on their server (my ISP's).
> Unfortunately, my local postfix is rejecting it because it's over "a fixed
> limit". I tried turning up the two likely-looking limits in /etc/postfix/
> bounce.cf.default, but that just removed the error message - the mail
> remained at my ISP.
> 
> What else can I try?
> 
> I use fetchmail to collect the POP3 mail and forward it to postfix for
> dovecot to serve as SMTP. This is the first trouble I've had with it and
> external mail.

If you want to try an old school approach, but with a more modern encryption 
method, you could try 'openssl s_client' and then list messages and retrieve 
the one you're interested in.  Something like this:

openssl s_client -connect pop.some_server.com:995 -crlf -starttls pop3

then use server commands[1] as you would over a telnet connection, e.g.

USER peter

PASS s3cr3tPa77

STAT
LIST
RETR 5
DELE 5
QUIT

The TOP command may also be useful if you wish to only check the top few lines 
of a (large) message to decide if you want to retrieve the rest of it.

TOP 5 10

Or if your ISP offer a webmail front end to their server, it should be easier 
to access the message with a browser.

[1] https://www.ietf.org/rfc/rfc1939.txt

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Re: Bouncing messages

2023-01-22 Thread Peter Humphrey
On Thursday, 19 January 2023 09:30:34 GMT I wrote:

> I'll see it it's my ISP who's bouncing the message.

It looks as though they did reject the mail. I asked them please to let it 
through just this once, and now it's sitting on their server (my ISP's). 
Unfortunately, my local postfix is rejecting it because it's over "a fixed 
limit". I tried turning up the two likely-looking limits in /etc/postfix/
bounce.cf.default, but that just removed the error message - the mail remained 
at my ISP.

What else can I try?

I use fetchmail to collect the POP3 mail and forward it to postfix for dovecot 
to serve as SMTP. This is the first trouble I've had with it and external mail.

-- 
Regards,
Peter.






Re: [gentoo-user] Re: Bouncing messages

2023-01-20 Thread Grant Taylor

On 1/20/23 9:09 AM, Peter Humphrey wrote:

I'm still getting bounce messages the same as all year.


Different meaning of "all the time".

 - Not all sending domains use advanced security.

 - Not all receiving domains use advanced security.

 - Not all mailing lists account for advanced security.

It's the overlap of those three things that suggest if a message will be 
bounced or accepted.




--
Grant. . . .
unix || die



Re: [gentoo-user] Re: Bouncing messages

2023-01-20 Thread Peter Humphrey
On Friday, 20 January 2023 14:44:24 GMT Grant Taylor wrote:
> On 1/20/23 2:07 AM, Dale wrote:

> > It's odd in my opinion.  Maybe someone will figure it out.
> 
> I think it's been figured out.  This is where "this isn't done all the
> time" comes into play.

I'm still getting bounce messages the same as all year.

-- 
Regards,
Peter.






Re: [gentoo-user] Re: Bouncing messages

2023-01-20 Thread Grant Taylor

On 1/20/23 2:07 AM, Dale wrote:
It could be the OP is running into the same problem I have in the 
past, whatever that problems is.


My experience is that this is a combination of advanced email protection 
on the sender /and/ the receiver.


E.g. the sending domain's email configuration specifies very specific 
locations combined with a receiving domain's email configuration 
honoring what the sending domain publishes.  Thus when a message passes 
through a 3rd party, saying a mailing list, the recipient refuses to 
accept the message because it's not from where the sender says the 
message is authorized to come from.


There's a lot of minutia to this and lots of ways that this can fail.

Yes, there are some things that the Gentoo Users mailing list can 
change, but do to various reasons, this isn't done all the time.


I might add, I don't recall seeing anything that leads me to believe 
I actually missed any messages.  I tent to follow most threads and 
I don't recall ever seeing a quoted message that I don't have the 
original of.


My experience is similar.


It's odd in my opinion.  Maybe someone will figure it out.


I think it's been figured out.  This is where "this isn't done all the 
time" comes into play.




--
Grant. . . .
unix || die



Re: [gentoo-user] Re: Bouncing messages

2023-01-20 Thread Dr Rainer Woitok
Grant,

On Thursday, 2023-01-19 22:59:48 -0700, you wrote:

> ...
> I tried it a few times.
> 
> I'd see mail log entries where the re-sent messages would fail the same 
> way that the original sent message failed.  :-/

Me too :-(

But isn't this changeable?   It's a list maintained by Gentoo.Org, after
all.  Gentoo is famous for its customizability,  but the organization of
its mailing lists is not adaptable to new requirements?  Does this mail-
ing software run under Windows?

Either these  mail identification numbers  should be somehow visible and
in particular searchable at

   https://archives.gentoo.org/gentoo-user/

or the mail that some mail couldn't be delivered should contain more in-
formation like author, date and subject.

DOES REALLY NOBODY CARE?

Sincerely,
  Rainer



Re: [gentoo-user] Re: Bouncing messages

2023-01-20 Thread Dale
Grant Taylor wrote:
> On 1/18/23 4:19 PM, Dale wrote:
>> I might add, in the past I followed the instructions to get bounced
>> messages, I've never once had it work.  I don't get a error or
>> anything either, like I do if I do something wrong doing something else.
>
> I tried it a few times.
>
> I'd see mail log entries where the re-sent messages would fail the
> same way that the original sent message failed.  :-/
>
>
>


That could be.  I disabled spam protection on the Google end and I never
have problems with messages from other sites.  As far as I can recall,
the only time I've had bounced messages is from a Gentoo mailing list. 
Anyway, after trying to get missed messages a few times, I finally
figured out it was a waste of time.  I'd like to have them but if I
can't get them, well, no point trying.  It could be the OP is running
into the same problem I have in the past, whatever that problems is.  I
might add, I don't recall seeing anything that leads me to believe I
actually missed any messages.  I tent to follow most threads and I don't
recall ever seeing a quoted message that I don't have the original of. 
The only exception is one person who I have blacklisted.  Those I never
get. 

It's odd in my opinion.  Maybe someone will figure it out. 

Dale

:-)  :-) 



Re: [gentoo-user] Re: Bouncing messages

2023-01-19 Thread Grant Taylor

On 1/18/23 4:19 PM, Dale wrote:
I might add, in the past I followed the instructions to get bounced 
messages, I've never once had it work.  I don't get a error or anything 
either, like I do if I do something wrong doing something else.


I tried it a few times.

I'd see mail log entries where the re-sent messages would fail the same 
way that the original sent message failed.  :-/




--
Grant. . . .
unix || die



Re: [gentoo-user] Re: Bouncing messages

2023-01-19 Thread Peter Humphrey
On Thursday, 19 January 2023 08:56:41 GMT Nuno Silva wrote:

> Did the bounce report you got reproduce any reason/message from the
> system it failed to deliver the message to?

No, just the standard list of message numbers.

> This message was particularly quite large, so it could be simply that...
> 200359 didn't make it to Gmane or marc.info either.
> 
> 200359 is:
> Message-ID: <67f4d690-1005-a4d6-abba-c685fd4af...@youngman.org.uk>
> 
> And is about 20MB big (owing to the attached build.log).
> 
> On the Gentoo website:
> https://archives.gentoo.org/gentoo-user/message/
dd1fc2d5d273f8590d73302748f2cda7

Good detective work - thanks Nuno.

I'll see it it's my ISP who's bouncing the message. After that I don't know 
where to look next.

-- 
Regards,
Peter.






[gentoo-user] Re: Bouncing messages

2023-01-19 Thread Nuno Silva
On 2023-01-13, Peter Humphrey wrote:

> Hello list,
>
> Ever since the new year I've been getting a bounce message from this list - 
> 19 
> of them so far. The first of those listed one message twice, most of the 
> others 
> six times. The message was 200359.
>
> I don't know what that message was, but why is the system Out There having 
> such a hard time with it?

Did the bounce report you got reproduce any reason/message from the
system it failed to deliver the message to? This message was
particularly quite large, so it could be simply that... 200359 didn't
make it to Gmane or marc.info either.

200359 is:
Message-ID: <67f4d690-1005-a4d6-abba-c685fd4af...@youngman.org.uk>

And is about 20MB big (owing to the attached build.log).

On the Gentoo website:
https://archives.gentoo.org/gentoo-user/message/dd1fc2d5d273f8590d73302748f2cda7

(Note that if you request the message and it does get delivered to you,
the Date: field differs between what you get and the archived copy on
the Gentoo website.)

-- 
Nuno Silva




Re: [gentoo-user] Re: Bouncing messages

2023-01-18 Thread David Rosenbaum
Dave

On Wed, Jan 18, 2023, 18:20 Dale  wrote:

> Grant Taylor wrote:
> > On 1/18/23 8:07 AM, Neil Bothwick wrote:
> >> You can also request redelivery of messages based on the internal
> >> numbers if you follow the help advice in all list message headers.
> >
> > The problem is that if the message is rejected because of filtering
> > the first time around, there's a very good chance that it will also be
> > filtered on subsequent re-delivery requests.
> >
> >
> >
>
>
> I might add, in the past I followed the instructions to get bounced
> messages, I've never once had it work.  I don't get a error or anything
> either, like I do if I do something wrong doing something else.
>
> Just a FYI.
>
> Dale
>
> :-)  :-)
>
>


Re: [gentoo-user] Re: Bouncing messages

2023-01-18 Thread Dale
Grant Taylor wrote:
> On 1/18/23 8:07 AM, Neil Bothwick wrote:
>> You can also request redelivery of messages based on the internal
>> numbers if you follow the help advice in all list message headers.
>
> The problem is that if the message is rejected because of filtering
> the first time around, there's a very good chance that it will also be
> filtered on subsequent re-delivery requests.
>
>
>


I might add, in the past I followed the instructions to get bounced
messages, I've never once had it work.  I don't get a error or anything
either, like I do if I do something wrong doing something else. 

Just a FYI. 

Dale

:-)  :-) 



Re: [gentoo-user] Re: Bouncing messages

2023-01-18 Thread Grant Taylor

On 1/18/23 8:07 AM, Neil Bothwick wrote:
You can also request redelivery of messages based on the internal 
numbers if you follow the help advice in all list message headers.


The problem is that if the message is rejected because of filtering the 
first time around, there's a very good chance that it will also be 
filtered on subsequent re-delivery requests.




--
Grant. . . .
unix || die



Re: [gentoo-user] Re: Bouncing messages

2023-01-18 Thread Neil Bothwick
On Wed, 18 Jan 2023 08:51:10 -0500, Jack wrote:

> >> Now was there (I recall asking about this previously, but I forgot
> >> what the answer was) a way to get a message-ID from that internal
> >> number, or at least a way to get the address of the message's
> >> archive copy on the gentoo website?  
> > I haven't found it, if so.  
> 
> Some time back I traded some emails with a sysadmin about this, and I'm 
> pretty sure there is no way to make that translation.  The number is 
> internal to the list software database and is apparently not surfaced 
> anywhere except such messages.  In my case, I was usually able to to to 
> the archive page for the list, and by displaying as messages (instead
> of threads) identify the one I never received.

You can also request redelivery of messages based on the internal numbers
if you follow the help advice in all list message headers.


-- 
Neil Bothwick

Hard work has a future payoff. Laziness pays off NOW!


pgpdEJ9wdop1k.pgp
Description: OpenPGP digital signature


Re: [gentoo-user] Re: Bouncing messages

2023-01-18 Thread Jack

On 1/18/23 06:44, Peter Humphrey wrote:

On Wednesday, 18 January 2023 08:59:21 GMT Nuno Silva wrote:


[  ]



Now was there (I recall asking about this previously, but I forgot what
the answer was) a way to get a message-ID from that internal number, or
at least a way to get the address of the message's archive copy on the
gentoo website?

I haven't found it, if so.


Some time back I traded some emails with a sysadmin about this, and I'm 
pretty sure there is no way to make that translation.  The number is 
internal to the list software database and is apparently not surfaced 
anywhere except such messages.  In my case, I was usually able to to to 
the archive page for the list, and by displaying as messages (instead of 
threads) identify the one I never received.


Jack





Re: [gentoo-user] Re: Bouncing messages

2023-01-18 Thread Peter Humphrey
On Wednesday, 18 January 2023 08:59:21 GMT Nuno Silva wrote:

> And *now* I haven't received one of these messages I was talking about
> (which would usually appear for every post of mine to the list, albeit
> possibly delayed by a few hours), so I guess either the forwarding
> problem was fixed or that person is not subscribed to the list anymore.

I've just had another one.

[...]

> So it is delivery *to* you that's failing? Hm, seeing you mentioned one
> of these message numbers that are internal to the list, I think I now
> understand what kind of bounce message you're talking about, sorry for
> the confusion.
> 
> Now was there (I recall asking about this previously, but I forgot what
> the answer was) a way to get a message-ID from that internal number, or
> at least a way to get the address of the message's archive copy on the
> gentoo website?

I haven't found it, if so.

-- 
Regards,
Peter.






[gentoo-user] Re: Bouncing messages

2023-01-18 Thread Nuno Silva
On 2023-01-14, Peter Humphrey wrote:

> On Saturday, 14 January 2023 07:00:29 GMT Nuno Silva wrote:
>> On 2023-01-13, Peter Humphrey wrote:
>> > Hello list,
>> > 
>> > Ever since the new year I've been getting a bounce message from this list
>> > - 19 of them so far. The first of those listed one message twice, most of
>> > the others six times. The message was 200359.
>> > 
>> > I don't know what that message was, but why is the system Out There 
> having
>> > such a hard time with it?
>> 
>> Was the message from the list software or from a Microsoft system?
>
> I don't know - I haven't received it as far as I know. The only archive 
> entries I've found are of this conversation.

And *now* I haven't received one of these messages I was talking about
(which would usually appear for every post of mine to the list, albeit
possibly delayed by a few hours), so I guess either the forwarding
problem was fixed or that person is not subscribed to the list anymore.

>> There's possibly one subscriber that has configured their
>> Exchange/Outlook account to forward e-mails to a Gmail account, and
>> forwarding as implemented by Microsoft apparently isn't done correctly
>> and so "SPF" checks run by Gmail are failing.
>
> Hmm. Would that cause the message to me to fail, in particular?

No, in the case I was writing about, it'd only cause you to get these
failure messages/reports delivered to you, I think precisely because of
the incorrect Microsoft forwarding implementation that'd present you as
the sender.

So it is delivery *to* you that's failing? Hm, seeing you mentioned one
of these message numbers that are internal to the list, I think I now
understand what kind of bounce message you're talking about, sorry for
the confusion.

Now was there (I recall asking about this previously, but I forgot what
the answer was) a way to get a message-ID from that internal number, or
at least a way to get the address of the message's archive copy on the
gentoo website?

>> I tried to send a message to this list about this topic back in November
>> but it never made through, perhaps it was filtered because it quoted
>> some of the error messages.

-- 
Nuno Silva




Re: [gentoo-user] Re: Bouncing messages

2023-01-16 Thread David Rosenbaum
Send again

David

On Sun, Jan 15, 2023, 19:50 Jigme Datse  wrote:

> On Sat, 14 Jan 2023 10:25:27 +
> Peter Humphrey  wrote:
>
> > On Saturday, 14 January 2023 07:00:29 GMT Nuno Silva wrote:
> > > On 2023-01-13, Peter Humphrey wrote:
> > > > Hello list,
> > > >
> > > > Ever since the new year I've been getting a bounce message from
> > > > this list
> > > > - 19 of them so far. The first of those listed one message twice,
> > > > most of the others six times. The message was 200359.
> > > >
> > > > I don't know what that message was, but why is the system Out
> > > > There
> > having
> > > > such a hard time with it?
> > >
> > > Was the message from the list software or from a Microsoft system?
> >
> > I don't know - I haven't received it as far as I know. The only
> > archive entries I've found are of this conversation.
>
> This seems like it might be a problem.  A lot of the time when I get
> "weird bounces" for messages for a mailing list, it isn't the list, but
> somewhere down the line, which is bouncing because they either aren't
> properly handling mailing lists, or something else (like in this
> example given, failing to properly handle forwarding "bouncing onward"
> sort of as the PINE parlance was used) list messages.
>
> > > There's possibly one subscriber that has configured their
> > > Exchange/Outlook account to forward e-mails to a Gmail account, and
> > > forwarding as implemented by Microsoft apparently isn't done
> > > correctly and so "SPF" checks run by Gmail are failing.
> >
> > Hmm. Would that cause the message to me to fail, in particular?
>
> The message *to* you?  I don't think so.  Or it might be someone
> sending from a server which somehow throws something into the header
> that causes it to be bounced that the list manager doesn't properly
> deal with?
>
> > > I tried to send a message to this list about this topic back in
> > > November but it never made through, perhaps it was filtered because
> > > it quoted some of the error messages.
> >
> >
>
>


Re: [gentoo-user] Re: Bouncing messages

2023-01-15 Thread Jigme Datse
On Sat, 14 Jan 2023 10:25:27 +
Peter Humphrey  wrote:

> On Saturday, 14 January 2023 07:00:29 GMT Nuno Silva wrote:
> > On 2023-01-13, Peter Humphrey wrote:  
> > > Hello list,
> > > 
> > > Ever since the new year I've been getting a bounce message from
> > > this list
> > > - 19 of them so far. The first of those listed one message twice,
> > > most of the others six times. The message was 200359.
> > > 
> > > I don't know what that message was, but why is the system Out
> > > There   
> having
> > > such a hard time with it?  
> > 
> > Was the message from the list software or from a Microsoft system?  
> 
> I don't know - I haven't received it as far as I know. The only
> archive entries I've found are of this conversation.

This seems like it might be a problem.  A lot of the time when I get
"weird bounces" for messages for a mailing list, it isn't the list, but
somewhere down the line, which is bouncing because they either aren't
properly handling mailing lists, or something else (like in this
example given, failing to properly handle forwarding "bouncing onward"
sort of as the PINE parlance was used) list messages.  

> > There's possibly one subscriber that has configured their
> > Exchange/Outlook account to forward e-mails to a Gmail account, and
> > forwarding as implemented by Microsoft apparently isn't done
> > correctly and so "SPF" checks run by Gmail are failing.  
> 
> Hmm. Would that cause the message to me to fail, in particular?

The message *to* you?  I don't think so.  Or it might be someone
sending from a server which somehow throws something into the header
that causes it to be bounced that the list manager doesn't properly
deal with?  

> > I tried to send a message to this list about this topic back in
> > November but it never made through, perhaps it was filtered because
> > it quoted some of the error messages.  
> 
> 



pgpNM2jFPg4pR.pgp
Description: OpenPGP digital signature


Re: [gentoo-user] Re: Bouncing messages

2023-01-14 Thread Peter Humphrey
On Saturday, 14 January 2023 07:00:29 GMT Nuno Silva wrote:
> On 2023-01-13, Peter Humphrey wrote:
> > Hello list,
> > 
> > Ever since the new year I've been getting a bounce message from this list
> > - 19 of them so far. The first of those listed one message twice, most of
> > the others six times. The message was 200359.
> > 
> > I don't know what that message was, but why is the system Out There 
having
> > such a hard time with it?
> 
> Was the message from the list software or from a Microsoft system?

I don't know - I haven't received it as far as I know. The only archive 
entries I've found are of this conversation.

> There's possibly one subscriber that has configured their
> Exchange/Outlook account to forward e-mails to a Gmail account, and
> forwarding as implemented by Microsoft apparently isn't done correctly
> and so "SPF" checks run by Gmail are failing.

Hmm. Would that cause the message to me to fail, in particular?

> I tried to send a message to this list about this topic back in November
> but it never made through, perhaps it was filtered because it quoted
> some of the error messages.


-- 
Regards,
Peter.






[gentoo-user] Re: Bouncing messages

2023-01-13 Thread Nuno Silva
On 2023-01-13, Peter Humphrey wrote:

> Hello list,
>
> Ever since the new year I've been getting a bounce message from this list - 
> 19 
> of them so far. The first of those listed one message twice, most of the 
> others 
> six times. The message was 200359.
>
> I don't know what that message was, but why is the system Out There having 
> such a hard time with it?

Was the message from the list software or from a Microsoft system?

There's possibly one subscriber that has configured their
Exchange/Outlook account to forward e-mails to a Gmail account, and
forwarding as implemented by Microsoft apparently isn't done correctly
and so "SPF" checks run by Gmail are failing.

I tried to send a message to this list about this topic back in November
but it never made through, perhaps it was filtered because it quoted
some of the error messages.

-- 
Nuno Silva




[gentoo-user] Re: Bouncing messages from gentoo-user@lists.gentoo.org

2020-02-04 Thread james

On 1/25/20 12:32 PM, gentoo-user+ow...@lists.gentoo.org wrote:


Some messages to you could not be delivered. If you're seeing this
message it means things are back to normal, and it's merely for your
information.

Here is the list of the bounced messages:
- 189317





Getting these messages again. They 'had disappeared for a while...'

Verizon mail server system is aweful, so I'm still working on a 
permanent solution. Anyway


subject:: maintainer-needed tools?



So,

https://qa-reports.gentoo.org/output/maintainer-needed.html

and

https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers/User_Guide#Proxied_Maintainer_gets


I use lots of these old packages, on old installs, and with minimal 
(some embedded) devices. So I feel like I should help maintain some of 
them; especially the ones I use. Many have (3 zeros) Open bugs:: for 
R-revdeps, D-revdep and P-revdeps. So here are some questions/requests 
for tools or useful scripts that provided some extended functionality.



1. Is there a 'tool/script' that searches (matches) this need-matainer 
list vs what I have installed? That sort of quick tool would allow 
everyone to quickly check to see if what they have/need is on the 
poverty list.

thus encouraging folks to 'adopt' some of these old codes; ymmv.


2. I have many old, james_created, eapi-5 ebuilds locally on my systems. 
I'd like a way to keep them organized separately, but yet have one 
master list to work off of. Ideas/suggestions how to organized this?


I currently place  ebuilds  of others in
/var/lib/layman. My ebuilds and codes are mostly in /usr/local/portage.

I probably should have another dir, just for embedded gentoo (centric) 
devices. but one master gui to easily view what code are where. 
Perhaps distinguish the builds, the ebuilds that do not yet work, and 
the raw C codes?



3. 
https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers/User_Guide#Proxied_Maintainer_gets



Perhaps one of the devs could throw up a quick gentoo doc, on suggested 
tools? Perhaps the proxy-maintainers have organized the tools and howtos 
and other info/intel, so an old, challenged hack like myself can quickly 
become 'literate' with the latest and best methods to maintain some of 
these old codes? I'm not necessarily up on the latest, most-efficient 
ways to organize lots of codes, ebuilds and otherwise.



4. I have not had the time to fully digest git*, so some simple 
examples, centric to helping to maintain these old codes, would be a 
very positive idea, to encourage folks to commit to helping, beyond 
'repoman vs CI'. Perhaps Proxy-maintainers has some examples, I've missed?



5. An additional column to newer codes that supersede these old codes 
would optimize the decisions that helpers make of where to invest their 
time wisely. Perhaps an additional column point to newer/better codes?



6. An additional column that points out the entries that are 
based/depend  on python2_7? Or just a parsed listing of such ebuilds.



Any other ideas/suggestions are most welcome.


James



Re: [gentoo-user] Re: Bouncing messages from gentoo-user@lists.gentoo.org

2020-01-14 Thread Mick
On Tuesday, 14 January 2020 13:39:57 GMT you wrote:
> On 1/13/20 5:24 PM, (Nuno Silva) wrote:
> > On 2020-01-13, james wrote:
> >> On 1/13/20 11:32 AM, gentoo-user+ow...@lists.gentoo.org wrote:
> >>> Some messages to you could not be delivered. If you're seeing this
> >>> message it means things are back to normal, and it's merely for your
> >>> information.
> >>> 
> >>> Here is the list of the bounced messages:
> >>> - 189231
> > 
> > How does one get to the message from that number? 

In order to receive an email of the bounced message you can send an empty 
message to the mailing list server, with the number of the message which was 
bounced in the address, e.g. to receive a copy of the above message number 
"189231", send this to the list:

gentoo-user+get-189...@lists.gentoo.org

HOWEVER ... your mailserver may still bounce the resent message.  I just tried 
to retrieve it manually, only for it to be bounced again silently by Gmail.  
If I hadn't received another notice for the same bounced message number by the 
M/L address 'gentoo-user+ow...@lists.gentoo.org', I wouldn't know Gmail 
bounced it once more.  :-/


> > Is it possible to get
> > an URL to the archived copy at http://archives.gentoo.org/ using that
> > number?

Hmm ... not sure if this is possible, or I don't know how to receive bounced 
messages via http.  The way I do it is by following a process of elimination.  
I check an online M/L archive service and the bounced message is the one I 
have not received out of the list of recent messages.


> >> Anyone else getting these?

Yep. I do, but it may well be related to me using a Gmail to receive messages 
and Gmail may be rejecting the odd message for some reason.  I have not added 
any recipients to a blacklist myself, so this is a Gmail action.


> > It might just be the DMARC policy thing again.
> > 
> > Here's a thread from last October/November about a similar message:
> > https://marc.info/?t=15725373431
> 
> It's my list emails, where I start a new subject. Usually, I can reply
> to an existing thread without issue.

Hi James.  I did receive your email yesterday from your verizon email address 
about Mesos, via the M/L.  It was titled "mesos updated ebuild advice?".  Your 
messages are being delivered to this M/L and Gmail distributes them without 
bouncing as far as I can surmise:

https://marc.info/?l=gentoo-user=157895127422780

The messages which seem to be bounced by Gmail are sent by Mr. Alan Grimes.  
The most recent bounced message was yesterday, titled "WTF is up with mysqld?"


> I've read this and still do not know what *I* need to do to fix this, or
> implement a workaround. I use thunderbird-(Installed versions:  68.4.1).

Nothing you need to do.  If people do not respond to a message it could well 
mean they have nothing valuable to add, rather than they haven't received it.

-- 
Regards,

Mick

signature.asc
Description: This is a digitally signed message part.


Re: [gentoo-user] Re: Bouncing messages from gentoo-user@lists.gentoo.org

2020-01-14 Thread james

On 1/13/20 5:24 PM, (Nuno Silva) wrote:

On 2020-01-13, james wrote:


On 1/13/20 11:32 AM, gentoo-user+ow...@lists.gentoo.org wrote:


Some messages to you could not be delivered. If you're seeing this
message it means things are back to normal, and it's merely for your
information.

Here is the list of the bounced messages:
- 189231


How does one get to the message from that number? Is it possible to get
an URL to the archived copy at http://archives.gentoo.org/ using that
number?


Anyone else getting these?


It might just be the DMARC policy thing again.

Here's a thread from last October/November about a similar message:
https://marc.info/?t=15725373431




It's my list emails, where I start a new subject. Usually, I can reply 
to an existing thread without issue.


I've read this and still do not know what *I* need to do to fix this, or 
implement a workaround. I use thunderbird-(Installed versions:  68.4.1).



So some explicit pathways to a solution/workaround would be appreciated. 
I also have a "free" limited/restricted email address::
'dtf...@protonmail.com'  not sure if using this address would fix 
things. The nice thing about 'thunderbird'
is I have a vast amount of saved emails, and it has worked flawlessly, 
until these bounced messages started this year.


I've read through that aforementioned thread, but, being old and slow, I 
did not see a fix for me. Perhaps gentoo runs a mail server, if I setup 
with proxy-maintainer?


I was trying to post a new about MESOS 'A distributed systems kernel'. 
Back in 2015 I have a working EAPI-5 gentoo ebuild, which I have 
locally. Upgraded to

Mesos-1.9.0 via EAPI 7(or ?) was the guidance I was looking for.

So can I get a gentoo-rookie-proxy mail server access?
I'm quite certain *MY* issues are due to how Verizon
administers the mail services. Often, when I fire up Thunderbird, it 
pucks for a few hours, then starts working with repetitive sends and 
pulls. I guess it finally reverts back to something that works for 
Thunderbird. I've been using thunderbird for a very, very long time and 
have little desire to stop using thunderbird, as my main email system. 
Now setting up
an easy-to-admin mail system(s) that is thunderbird friendly;  I'm all 
ears. I may be getting a single static IP, to facilitate just that, from 
Verizon or ?.



Any help via this list or direct is most appreciated.

James




Re: [gentoo-user] Re: Bouncing messages from gentoo-user@lists.gentoo.org

2020-01-13 Thread Neil Bothwick
On Mon, 13 Jan 2020 22:24:51 +, (Nuno Silva) wrote:

> >> Here is the list of the bounced messages:
> >> - 189231  
> 
> How does one get to the message from that number?

Look at the List-Help header in any message. Following that returns a
list of commands you can send to the listserv.


-- 
Neil Bothwick

Never underestimate the bandwidth of a station wagon full of tapes!


pgpzyMsvhdLWd.pgp
Description: OpenPGP digital signature


[gentoo-user] Re: Bouncing messages from gentoo-user@lists.gentoo.org

2020-01-13 Thread nunojsilva
On 2020-01-13, james wrote:

> On 1/13/20 11:32 AM, gentoo-user+ow...@lists.gentoo.org wrote:
>>
>> Some messages to you could not be delivered. If you're seeing this
>> message it means things are back to normal, and it's merely for your
>> information.
>>
>> Here is the list of the bounced messages:
>> - 189231

How does one get to the message from that number? Is it possible to get
an URL to the archived copy at http://archives.gentoo.org/ using that
number?

> Anyone else getting these?

It might just be the DMARC policy thing again. 

Here's a thread from last October/November about a similar message:
https://marc.info/?t=15725373431

-- 
Nuno Silva




[gentoo-user] Re: Bouncing messages from gentoo-user@lists.gentoo.org

2020-01-13 Thread james

On 1/13/20 11:32 AM, gentoo-user+ow...@lists.gentoo.org wrote:


Some messages to you could not be delivered. If you're seeing this
message it means things are back to normal, and it's merely for your
information.

Here is the list of the bounced messages:
- 189231





Anyone else getting these?

James



Re: [gentoo-user] Re: Bouncing Messages

2018-03-02 Thread Grant Taylor

On 03/02/2018 05:47 PM, Ian Zimmerman wrote:
Flam^H^H^H^H value judgments aside, does DMARC also change the long 
standing standard of sending rejections to the envelope address?


No, DMARC should not change the principle operation of SMTP, save for 
additional checks that messages must pass.  All other aspects of sending 
email should be the same.


MTAs should continue to send bounces back to the SMTP envelope address. 
Though, ideally the MTA would reject the message during SMTP time 
instead of accepting and bouncing the message.


DMARC does offer the ability to have reports about DMARC failures sent 
to the domain publishing the DMARC record.




--
Grant. . . .
unix || die




[gentoo-user] Re: Bouncing Messages

2018-03-02 Thread Ian Zimmerman
On 2018-03-02 15:51, Grant Taylor wrote:

> The reason that messages are being rejected is because of the DMARC
> policy.  1) I publish DMARC records and 2) Gmail honor published DMARC
> records.

[...]

> - This is a growing change in the email industry.  - I just happen to
> live towards (but not on) the bleeding edge of email.

Flam^H^H^H^H value judgments aside, does DMARC also change the
long standing standard of sending rejections to the envelope address?

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.



Re: [gentoo-user] Re: Bouncing Messages

2018-03-02 Thread Grant Taylor

On 03/02/2018 09:36 AM, Ian Zimmerman wrote:
These are all from Grant Taylor.  They are DKIM-signed, and, not 
surprisingly given the list header and footer munging, signature 
verification fails (on my mail server).


Correct.  DKIM verification is failing and my DMARC policy is configured 
to REJECT messages that fail DKIM or SPF tests.


The reason that messages are being rejected is because of the DMARC 
policy.  1)  I publish DMARC records and 2) Gmail honor published DMARC 
records.


The same type of problem will happen with any other sending domain that 
publishes REJECT records to a recipient where the receiving server 
honors said REJECT records.


This is not just me.  More and more sending domains are publishing DMARC 
records and more and more receiving servers are honoring said records. 
Further, multiple governments are mandating that governmental agencies 
and sub-contractors implement DMARC (which also means DKIM and SPF). 
The US and Germany come to mind immediately.  -  This is a growing 
change in the email industry.  -  I just happen to live towards (but not 
on) the bleeding edge of email.


Munging by lists should just die.  Why do it?  Windoze and Goo users may 
have to split their mail into folders by Subject, but surely Gentooers 
know better?


I do not believe that munging is a bad thing.  I'll even go so far as to 
say that I think it's a good thing.  (This can turn into a long running 
discussion that likely doesn't belong on the Gentoo-User mailing list.)


IMHO the biggest issue is that the messages aren't munged enough.  From 
also needs to be munged to make the message appear to be from a 
different address.  (Ideally one that the mailing list owns.)


I also think that any security headers that exist on the incoming 
message should be removed as messages come into the mailing list and 
certainly before going out from the mailing list.


 - ARC-*
 - Authentication-Results
 - DKIM-*

Removing these extra headers should help ensure that they don't 
accidentally get mis-interpreted by servers receiving messages from the 
mailing list manager.


I have created a new email address in a sub-domain and (re)subscribed to 
the Gentoo-User mailing list with it and unsubscribed my main email 
address.  This new sub-domain has a different DMARC policy ("NONE" 
instead of "REJECT") and I'm hoping that it will minimize the number of 
messages that get bounced.  (This is the first time I'm testing it, so I 
may not have things correctly configured for the new sub-domain yet.)




--
Grant. . . .
unix || die



[gentoo-user] Re: Bouncing Messages

2018-03-02 Thread Ian Zimmerman
On 2018-03-02 12:04, Floyd Anderson wrote:

> 
> 
> 

These are all from Grant Taylor.  They are DKIM-signed, and, not
surprisingly given the list header and footer munging, signature
verification fails (on my mail server).

Munging by lists should just die.  Why do it?  Windoze and Goo users may
have to split their mail into folders by Subject, but surely Gentooers
know better?

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.



[gentoo-user] Re: Bouncing Messages

2018-03-01 Thread Ian Zimmerman
On 2018-03-01 18:12, Dale wrote:

> Here is the list of the bounced messages:
> - 182748
> - 182749
> - 182751

If you succeed in retrieving them, please let us know which ones they
were, so we can guess as to the cause.

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.



[gentoo-user] Re: Bouncing Messages

2018-03-01 Thread Ian Zimmerman
On 2018-03-01 18:12, Dale wrote:

> If it helps, this is the complete message headers and all that I got
> for one of them. Obviously, I'm editing out my email addy. I get
> enough spam as it is. I'm replacing my email addy with ohnoyourenot
> even if it is a partial. It seems to me that they are coming from the
> Gentoo servers BUT I'm no expert on these things.

Yes, this is sent by the gentoo server.  It's different from what I
get, and it does mean the gentoo list server couldn't push some messages
to you, or so it thinks.

If you weren't on gmail, I'd say you might be the other side of the same
coin, i.e. the recipient who bounces my messages.  But maybe there's a
common reason why both Goo and Micro$oft think my messages or maybe
other messages on this list are spam.  The difference would be that Goo
at least bounces correctly, ie. to the MAIL FROM (aka envelope) address.

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.



Re: [gentoo-user] Re: Bouncing Messages

2018-03-01 Thread Dale
Ian Zimmerman wrote:
> On 2018-03-01 23:48, Branko Grubic wrote:
>
>>> I keep my messages locally so when I miss messages, it can throw a
>>> thread into some random weirdness.  If one uses the web interface to
>>> read/reply etc then it wouldn't matter but for those who use email
>>> software, it seems we are missing something.
>> I have no idea, does it mean it bounced, and mailing list software did
>> re-send them later or not. I don't see a way to use those numbers to
>> find out which email message relates to the number. So no answer for
>> any of those.
> Just to clarify: what I see is messages _I_ send to the list bounced by
> some recipients (presumably list subscribers), the bounces coming from
> Microsoft outlook/365 servers.
>
> I myself don't seem miss to any messages in this list, and I get back
> mine as well, which tells me this is not a problem with the list server.
>


If it helps, this is the complete message headers and all that I got for
one of them.  Obviously, I'm editing out my email addy.  I get enough
spam as it is.  I'm replacing my email addy with ohnoyourenot even if it
is a partial.  It seems to me that they are coming from the Gentoo
servers BUT I'm no expert on these things. 


>From - Wed Feb 28 18:03:16 2018
X-Account-Key: account2
X-UIDL: GmailId161dede902deb213
X-Mozilla-Status: 0001
X-Mozilla-Status2: 
X-Mozilla-Keys: 

Delivered-To: ohnoyoure...@gmail.com
Received: by 10.25.154.67 with SMTP id c64csp7109702lfe;
Wed, 28 Feb 2018 16:03:03 -0800 (PST)
X-Google-Smtp-Source: 
AG47ELucwZNeFRXiKJjxlh2eudY7NO2VLO3a9qKkxD2klVL6Ox6wytGi7pvTBGED47eJF4jE6Cjx
X-Received: by 10.36.73.95 with SMTP id z92mr460219ita.38.1519862583426;
Wed, 28 Feb 2018 16:03:03 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1519862583; cv=none;
d=google.com; s=arc-20160816;
b=qfZuMfl7obhz2C7JcaZfXaanwriCPPw7BIFfP7XSK1HsMm9B0A6gXRSyAXXE74Ev1e
 Kz+ECG1ljQ1cUrYvhIkGROJJdQ8RVTiMPHA13UfQO5tSbYC0jK3C2FKH1B46upQu6Qgy
 0oufsqe5DqcI4XGZNtV6MFpAh5sa9JArxJRi2VhE03tsQ2H3sU3mur949sGOTYb03FGk
 zrg/G+wjU1vYmBPej/93yKfKUSff1y1OEBNeWX9arCvReA0qQR478xS6x3QjPs1y7LNZ
 WCD5mNYhdrh77iFnbB1BQFzNJ1NhvTgZapAP2Oaqv4dDy+/YFwpJpiaAsff4YMdvfjjD
 mOXw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; 
s=arc-20160816;
h=content-transfer-encoding:mime-version:date:message-id:to:from
 :list-unsubscribe:list-subscribe:list-archive:list-owner:list-faq
 :list-help:list-post:errors-to:precedence:subject
 :arc-authentication-results;
bh=ZE0FyWZlIM4FKnvLuANrV6Ruv/741w0j0qAXZBDqGy0=;
b=vHxQPOk0fNvCMkSX69ytRVE8cKh4f4eV9AP11Rtg+svjrf1hi7nOs8HtX2ZABEo3TB
 tRRI2dNkuOds3K4Lx2gasbo4/GeYU3Q6oOSUygkJx3sXTal8qtu8b0tpQzrjs84gPgs3
 bog58QIgQUx/Rz+uExTICPdi5PQUxy+elgR2AFTvgOBeSpeKrqSVFU8/neSL0m6yXdqV
 IkpepCs252y4NpuLCVmZAGRGyopMxhqeF4LOF2Z5VuT6ADlOT+1hFvtcKIr7a5poZt2A
 5gydw0JcyrDB07i5UeVRwxcYb2HA2h23aWoRhgspWATtLMBGu6b++mvZI9tIODV1dNrM
 dvAw==
ARC-Authentication-Results: i=1; mx.google.com;
   spf=pass (google.com: domain of 
gentoo-user+bounces-probe-ohnoyourenot=gmail@lists.gentoo.org designates 
208.92.234.80 as permitted sender) 
smtp.mailfrom=gentoo-user+bounces-probe-ohnoyourenot1967=gmail@lists.gentoo.org;
   dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=lists.gentoo.org
Return-Path: 
Received: from lists.gentoo.org (pigeon.gentoo.org. [208.92.234.80])
by mx.google.com with ESMTPS id q5si1660555ioq.283.2018.02.28.16.03.03
for 
(version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
Wed, 28 Feb 2018 16:03:03 -0800 (PST)
Received-SPF: pass (google.com: domain of 
gentoo-user+bounces-probe-ohnoyourenot=gmail@lists.gentoo.org designates 
208.92.234.80 as permitted sender) client-ip=208.92.234.80;
Authentication-Results: mx.google.com;
   spf=pass (google.com: domain of 
gentoo-user+bounces-probe-ohnoyourenot=gmail@lists.gentoo.org designates 
208.92.234.80 as permitted sender) 
smtp.mailfrom=gentoo-user+bounces-probe-ohnoyourenot=gmail@lists.gentoo.org;
   dmarc=pass (p=NONE sp=QUARANTINE dis=NONE) header.from=lists.gentoo.org
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id E8BD7E0949
for ; Thu,  1 Mar 2018 00:03:02 + (UTC)
Subject:=?utf-8?q?_Bouncing_messages_from_gentoo-user=40lists.gentoo.org?=
Precedence: bulk
Errors-To: <"mailto:postmaster"@lists.gentoo.org>
X-BeenThere: gentoo-user@lists.gentoo.org
List-Post: 
List-Help: 
List-FAQ: 
List-Owner: 

[gentoo-user] Re: Bouncing Messages

2018-03-01 Thread Ian Zimmerman
On 2018-03-01 23:48, Branko Grubic wrote:

> > I keep my messages locally so when I miss messages, it can throw a
> > thread into some random weirdness.  If one uses the web interface to
> > read/reply etc then it wouldn't matter but for those who use email
> > software, it seems we are missing something.

> I have no idea, does it mean it bounced, and mailing list software did
> re-send them later or not. I don't see a way to use those numbers to
> find out which email message relates to the number. So no answer for
> any of those.

Just to clarify: what I see is messages _I_ send to the list bounced by
some recipients (presumably list subscribers), the bounces coming from
Microsoft outlook/365 servers.

I myself don't seem miss to any messages in this list, and I get back
mine as well, which tells me this is not a problem with the list server.

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.



[gentoo-user] Re: Bouncing Messages

2018-03-01 Thread Ian Zimmerman
On 2018-03-01 14:42, R0b0t1 wrote:

> I keep getting emails from the mailer daemon about bouncing messages.
> I am worried. Am I missing messages from my internet friends? Please
> send help.

Do you mean the crud from outlook/365?  I get that too; it's probably
because my list mail lacks DKIM sigs (intentionally so).  But whatever
the reason it's horrifying brain damage on their part to send the
bounces to _me_ rather than the envelope sender which is the bounce
address of the list.  Micro$oft may have softened from the 90s but it's
still breaking standard protocols left and right, it seems.

I have just configured my MTA to send bounces from their IP ranges to
/dev/null.

-- 
Please don't Cc: me privately on mailing lists and Usenet,
if you also post the followup to the list or newsgroup.
To reply privately _only_ on Usenet and on broken lists
which rewrite From, fetch the TXT record for no-use.mooo.com.