Re: check_qmail_deliverable

Hi, Juerd Waalboer wrote: I'm using it on several servers now. I'm pretty confident that my design withstands many edge cases well. Normal qmail, qmail+vpopmail, and qmail+plesk all just worked (although I had to hack in support for bouncesaying, for Plesk setups). I'm looking into implementin

HashCash reloaded

Hi list, I've written a HashCash plug-in that uses Digest::HashCash and is a bit more cleaned-up than the existing one. http://wiki.qpsmtpd.org/plugins:spam:hashcash Has anyone an idea how a plug-in can find out if the mail it currently handles is a incoming (local delivery) or outgoing (routed

Re: HashCash reloaded

[EMAIL PROTECTED] wrote: > Has anyone an idea how a plug-in can find out if the mail it currently > handles is a incoming (local delivery) or outgoing (routed to the > world) mail? Right now, I solved this by setting a connection-note in > another plug-in that check if the remote IP is a relay clie

Re: HashCash reloaded

On Dec 10, 3:15 pm, [EMAIL PROTECTED] (Johan Almqvist) wrote: > As you can see from my plugin, I based the decision on whether the mail > is sent by an authenticated user... Hi Johan, I cant find any plug-in or library in lib/Qpsmtpd that sets this "authuser" note. It seems not to be set within

Re: HashCash reloaded

On 2007-12-10 06:09:41 -0800, [EMAIL PROTECTED] wrote: > Has anyone an idea how a plug-in can find out if the mail it currently > handles is a incoming (local delivery) or outgoing (routed to the > world) mail? Right now, I solved this by setting a connection-note in > another plug-in that check if

Re: check_qmail_deliverable

Toni Mattila skribis 2007-12-10 14:25 (+0200): > >I'm using it on several servers now. I'm pretty confident that my design > >withstands many edge cases well. Normal qmail, qmail+vpopmail, and > >qmail+plesk all just worked (although I had to hack in support for > >bouncesaying, for Plesk setups).

Re: HashCash reloaded

On 10 Dez., 17:42, [EMAIL PROTECTED] (Peter J. Holzer) wrote: > Why set an additional connection-note and not use relay_client() > directly? I think that's what it is for. > > (not really "incoming" vs. "outgoing" but "authorized to send mail to > anybody" vs. "not authorized to send mail to anyb

Re: Overview of rcpt checkers

On 2007-12-09 23:42:51 +0100, Juerd Waalboer wrote: > Juerd Waalboer skribis 2007-12-07 1:53 (+0100): > > I'm going to email all the authors, as far as I can find their > > addresses, so they have a chance to respond to my critique. > > Instead of complaining about lack of qmail support, I've dec

Re: Overview of rcpt checkers

Peter J. Holzer skribis 2007-12-10 23:01 (+0100): > > Qmail's modular design made replacing the SMTP daemon very simple, and > > because > > development on qmail stopped with version 1.03 in 1993, several replacement >^ >

Re: Overview of rcpt checkers

Peter J. Holzer skribis 2007-12-10 23:01 (+0100): > The aliases plugin supports catch-all domains and catch-all extensions, Support for catch-all domains isn't obvious from the documentation, but indeed the source clearly supports a [EMAIL PROTECTED] wildcard, with a literal * in the alias file.

Qmail::Deliverable::Comparison draft 4

(Not all previous drafts have made it to the qpsmtpd list) Thanks for all your nice replies and corrections. Here's the new version. I consider it a release candidate. -- Met vriendelijke groet, Kind regards, Korajn salutojn, Juerd Waalboer: Perl hacker <[EMAIL PROTECTED]>