I receive a lot of bounces for mail messages which I have not originally
sent. Most of this bounces have the original mail somewhere in the body.
The original mail often contains a "Received:" line with one of my
domains but wrong ip addresses.
I wonder wether there exists a plugin to filter t
l at first. I'm using SPF for my domains so that this
mail could easily be detected as not being legitimate. But then, not
everybody is using qpsmtpd.
Werner
Johan Almqvist schrieb:
Werner,
Werner Fleck wrote:
I receive a lot of bounces for mail messages which I have not
originally sen
Thank you very much! I think this is a good starting point to write my
first plugin.
Werner
Johan Almqvist schrieb:
Werner Fleck wrote:
Why should I miss legitimate bounces? I thought, since I'm in control
of any mail server which might legitimately identify itself as
mydomain.com, any
ounces and they would not get the double bounces...
Werner
Mark Farver schrieb:
Werner Fleck wrote:
I receive a lot of bounces for mail messages which I have not
originally sent. Most of this bounces have the original mail somewhere
in the body. The original mail often contains a "Received
[EMAIL PROTECTED] schrieb:
[...]
The spammers who take my domain name in vain tend to use a random
username for the emails, so I reject bounces sent to non-existent users
with a special message that says "Looks like you're bouncing a mail
witha spoofed sender - if you'd consider checking SPF r
Now I've made my own plugin fo filter those bounces. I took the
rcpt_regexp plugin and modified it, that it only handles bounce mails,
i.e. mails where the envelope sender is "<>". The plugin is attached to
this message.
Werner
Werner Fleck schrieb:
[EMAIL PROTECTED
Yes, you're right and I wanted to do this at first. But after reading
some time about the "plug-in template" and the "documented namespace
standard" I still have no clue how to do this. So I decided to post the
plugin to the newsgroup instead of doing nothing and keeping it for myself.
Cheers
ted the wiki, so it can be downloaded at
http://wiki.qpsmtpd.org/plugins:spam:bounce_rcpt_regexp
Werner
James Turnbull schrieb:
Werner Fleck wrote:
Yes, you're right and I wanted to do this at first. But after reading
some time about the "plug-in template" and the "docume
So maybe the best thing to do is to make the list of envelope sender
addresses of bounce messages configurable. And to provide a working
email address in the error message so that a postmaster can send us mail.
Werner
Hans Salvisberg schrieb:
Werner Fleck wrote:
I have changed the plugin so
ding it to
yet another server.
Werner
Hans Salvisberg schrieb:
Since this thread is still active, I'll add my 2 cents:
Werner Fleck wrote:
I did not mean forged bounces but real bounces for forged mails.
Spammers discovered my domains some months ago and are increasingly
using them for forg
With the attached patch applied, the spamassassin plugin adds the
X-Spam-Level header line to the mail, i.e. a header consisting of
'X-Spam-Level: ' followed by a number of asterisks '*' given by the spam
level.
With this line present it is easier to write filter rules for the most
email prog
lease provide an example.
At Fri, 21 Sep 2007 22:34:12 +0200,
Werner Fleck wrote:
[1 ]
With the attached patch applied, the spamassassin plugin adds the
X-Spam-Level header line to the mail, i.e. a header consisting of
'X-Spam-Level: ' followed by a number of asterisks '*'
Guy Hulbert schrieb:
On Fri, 2007-09-21 at 22:34 +0200, Werner Fleck wrote:
With the attached patch applied, the spamassassin plugin adds the
X-Spam-Level header line to the mail, i.e. a header consisting of
'X-Spam-Level: ' followed by a number of asterisks '*' give
Attached you find a patch for the whitelist_soft plugin to allow regular
expressions in the whitelistrcpt configuration file. Regular expressions
have to be enclosed between slashes to differentiate between the old
string matching and the new regular expression matching behaviour.
It is useful
2:28 PM, Werner Fleck wrote:
+Entries in whitelistrcpt may be regular expressions surrounded by
+slashes ('/'). In this case only the recipient but not the hostname
+component is matched.
Shouldn't the hostname component be matched too?
- ask
[EMAIL PROTECTED] schrieb:
we mis-communicate i believe. i suggested that you include the url in
the smtp error message you send when you reject the initial email.
then you do not generate any backscatter spam. however, it does
require that the origin MTA send the text of the message back to the
Michael Salbinger schrieb:
hi,
my greylisting mechanism is blocking too much mails.
not only spam, its blocking web.de and so on.
how can i configure this thing right?
my denysoft_greylist.dbm has 290 ips in it.
am i able to delete it or such thing?
thanks
m.
There was a discussion reac
17 matches
Mail list logo
