> >
> > Normally, it is caused by your mailserver rejecting a malformed mail
> > that has been sent to the list - the list software has accepted it and
> > not corrected its "non-compliance" - hence your mailserver bounces it.
>
> No I would see the reject in the
he list - the list software has accepted it and
> not corrected its "non-compliance" - hence your mailserver bounces it.
No I would see the reject in the mail logs, and when I requested the bounced
messages I had already received all of them. So that was why I wondered why
the list serve
On Wed, 20 May 2020 13:09:14 +0100
Phil Reynolds wrote:
> On Tue, 19 May 2020 07:43:14 -0400
> "Rick Cooper" wrote:
> > This time I went ahead and the email that would retrieve the
> > messages that had bounced and I have every single one of them
> > already... Every singled one.
> >
> > What
On Tue, 19 May 2020 07:43:14 -0400
"Rick Cooper" wrote:
> I occasionally get emails warning me of bounced mail, this one
> doesn't go through we will send a probe, yada, yada.
>
> They say they include the bounce message but they always look like
> this: --- Enclosed is a copy of the bounce mess
I occasionally get emails warning me of bounced mail, this one doesn't go
through we will send a probe, yada, yada.
They say they include the bounce message but they always look like this:
--- Enclosed is a copy of the bounce message I received.
Return-Path: <>
Received: (qmail 21198 invoked for
>> I think you've just proved my point. It's too hard to try and
>> determine who to contact in these situations
>
> Do it like Spamcop does with SPAM: Contact *everybody* in the chain, and
> complain to them. Some sort of SPFcop would be nice for that..
cat /var/log/maillog | pflogsumm -d today
Michael Monnerie <[EMAIL PROTECTED]> writes:
> Do it like Spamcop does with SPAM: Contact *everybody* in the chain, and
> complain to them. Some sort of SPFcop would be nice for that..
Or even use SpamCop itself. Bounces to forged emails are now
considered legitimate for reporting to spamcop. Th
On Montag, 26. Juni 2006 01:36 Gino Cerullo wrote:
> > Spambot A => Recipient Server C => (Bounce) => Forged Email Server
> > D
>
> I think you've just proved my point. It's too hard to try and
> determine who to contact in these situations
Do it like Spamcop does with SPAM: Contact *everybody*
On 25-Jun-06, at 7:22 PM, John D. Hardin wrote:
On Sun, 25 Jun 2006, Jim Hermann - UUN Hostmaster wrote:
There are at least two ISPs involved:
Spammer A => SMTP Server B => Recipient Server C => (Bounce) =>
Forged Email Server D
I don't think that's the case for most spam these days. For a
On 25-Jun-06, at 7:01 PM, Jim Hermann - UUN Hostmaster wrote:
Personally, nowadays I believe bouncing messages back to
the alleged
sender
That's not what he's asking. He wants to know whether asking ISPs to
implement SPF checks (where they don't yet check SPF) will work.
I'm not convinced
On Sun, 25 Jun 2006, Jim Hermann - UUN Hostmaster wrote:
> There are at least two ISPs involved:
>
> Spammer A => SMTP Server B => Recipient Server C => (Bounce) =>
> Forged Email Server D
I don't think that's the case for most spam these days. For a
spambotnet of compromised home systems, you'l
> >> Personally, nowadays I believe bouncing messages back to
> the alleged
> >> sender
> >
> > That's not what he's asking. He wants to know whether asking ISPs to
> > implement SPF checks (where they don't yet check SPF) will work.
>
> I'm not convinced that is what he meant but he wasn't clear
On 25-Jun-06, at 5:51 PM, John D. Hardin wrote:
On Sun, 25 Jun 2006, Gino Cerullo wrote:
Does it do any good to complain to the ISP that accepted the
original email
with a forged email address that uses a domain name that I
administer?
Personally, nowadays I believe bouncing messages back
On Sun, 25 Jun 2006, Gino Cerullo wrote:
> > Does it do any good to complain to the ISP that accepted the
> > original email
> > with a forged email address that uses a domain name that I administer?
>
> Personally, nowadays I believe bouncing messages back to the alleged
> sender
That's not
ver receives numerous bounced messages from therecipient servers because the recipients do not exist or do not accept thespam. Of course, I can reject or delete the bounced messages if the forgedemail address does not exist.However, I would like to be more proactive and complain to the ISP thataccept
people call this a JoeJob. Obviously, I can't prevent this, although I can
use SPF with HARDFAIL to help the recipient server identify that the email
address has been forged.
The problem is that my server receives numerous bounced messages from the
recipient servers because the recipients d
16 matches
Mail list logo
