With some inspiration from Sam, I cleaned up my code a bit and added a
configurable whitelist to my hnbl plugin. The new config file is called
'notbadmailfromhost'. Please note the need to edit the $errormail variable
to point to a fairly open address that you can check regularly like yahoo
or hot
On Tue, 23 Mar 2004, Skaag Argonius wrote:
> I guess it would probably be qmail-remote. How do I change this?
Why do you want to change it? There's a good chance you'll break something
if you try.
---
Charlie
The only way I've been able to solve that problem is to specify my source ip
address in my default route:
default via 192.168.4.1 dev eth2 src 192.168.4.68
Otherwise it'll use the primary IP address, 192.168.4.68 in this example:
eth2: mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:40:f
On Mar 23, 2004, at 12:10 PM, Skaag Argonius wrote:
I changed the file /config/IP and it still other hosts see another ip
address connecting to them.
If you are trying to make qmail-remote use a different address, then
the "qmail-remote outgoingip patch" might be useful to you:
http://www.lamer
I guess it would probably be qmail-remote. How do I change this?
Aric
On Tue, 23 Mar 2004, Skaag Argonius wrote:
> My mail server has several ip addresses. I want qpsmtpd to bind to a
> specific one. How do I do this?
That depends on which form of qpsmtpd you run (i.e. how you start
qpsmtpd).
> I changed the file /config/IP and it still other hosts see another
My mail server has several ip addresses. I want qpsmtpd to bind to a
specific one. How do I do this?
I changed the file /config/IP and it still other hosts see another ip
address connecting to them.
Any ideas?
Aric
>By its self, this plug-in seemed to eliminate the largest chunk of remaining
>spam when I added it in. It also reduced the load on the server by saving
>the following plugins the effort of more tests.
I used to do the equivalent for qmail, i.e. temporarily rejecting
incoming TCP connections from
On Tue, 23 Mar 2004, Sam Laffere wrote:
> Charlie Brady wrote:
>
> > Yes, [greylisting] does lock. I didn't check that it will always remove the lock.
> > Behaviour probably depends on which form of the command is run - Sam,
> > are you using select server, or running under tcpserver?
>
> Tcpser
On Tue, 23 Mar 2004, Sam Laffere wrote:
> > Make no mistake, this plugin is a heavy hand.
>
> By its self, this plug-in seemed to eliminate the largest chunk of remaining
> spam when I added it in. It also reduced the load on the server by saving
> the following plugins the effort of more tests
Charlie Brady wrote:
> On Mon, 22 Mar 2004, Matt Sergeant wrote:
>
>> It probably has to be re-written with locking (though I haven't read
>> the code for the plugin - does it lock?)
>
> Yes, it does lock. I didn't check that it will always remove the lock.
> Behaviour probably depends on which for
frank wrote:
> (note: I'm the author)
>
> I have to agree with this guy here. Since I wrote the plugin, I've
> been in
> touch with at least 10 mail admins who were interested in bringing
> their
> server closer to spec. Course I'm not quite sure what spec is, I'm
> just a
> hacker who is sick of s
> Also just a random suggestion. On the list a reply-to field of
> [EMAIL PROTECTED]
> would help. Just hitting replies got directly to the sender, hense off
> list. W/ that in the reply field just hitting reply would send the
> message to the list.
Please google for "Reply-To Considered Harm
(note: I'm the author)
I have to agree with this guy here. Since I wrote the plugin, I've been in
touch with at least 10 mail admins who were interested in bringing their
server closer to spec. Course I'm not quite sure what spec is, I'm just a
hacker who is sick of spam on his box and used a bit
Nick Leverton wrote:
Qpsmtpd doesn't use smtproutes, as someone else said. It purely
replaces qmail-smtpd; you still need the rest of your /var/qmail_in
programs (qmail-queue, qmail-send, qmail-remote, etc).
You can tell qpsmtpd to forward directly via SMTP to your scanner instead
of calling qmai
[EMAIL PROTECTED] wrote:
Possible solution, assuming I understand your setup correctly,
would be to set up a .qmail-default in your ~alias directory that forwards
everything inbound to localhost:10024. I expect that that qmail
installation will take care of final delivery.
Hadn't though
On Tue, 23 Mar 2004, Skaag Argonius wrote:
> I disagree with you and robert about remote mail admins not giving a damn.
> Every mail admin i've talked to online, made the efforts to fix the
> problems, because I am hosting mail for some companies that do some serious
> business. Lost mail means lo
I disagree with you and robert about remote mail admins not giving a damn.
Every mail admin i've talked to online, made the efforts to fix the
problems, because I am hosting mail for some companies that do some serious
business. Lost mail means lost business! I've helped them understand why
they ne
On Mon, Mar 22, 2004 at 06:03:12PM -0600, Roger wrote:
> I recently installed qpsmtpd and sorta got it to run. The problem is
> qpsmtpd would not recognise my smtproutes setup - which forwards all
Qpsmtpd doesn't use smtproutes, as someone else said. It purely
replaces qmail-smtpd; you still n
Hi Sam,
On Mon, Mar 22, 2004 at 07:12:29PM -0600, Sam Laffere wrote:
> I implemented this plugin on a test domain, and it seemed great, but after
> implementing on my production server, I had too many customers not getting
> their email because of the 'no reverse lookup' part. For now I have
> r
On Mon, Mar 22, 2004 at 05:13:43PM -0500, Charlie Brady wrote:
> On Mon, 22 Mar 2004, Matt Sergeant wrote:
>
> > It probably has to be re-written with locking (though I haven't read
> > the code for the plugin - does it lock?)
>
> Yes, it does lock. I didn't check that it will always remove the
21 matches
Mail list logo
