> It would be perfect to combine this with some of the features of TMDA
> (http://tmda.sourceforge.net/) like dated and keyword addresses.
Hi Werner,
thanks for pointing me to this. I never heard about it - seems to be
pretty interesting though. I'll think about adding the temporary
address stuff
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
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
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
> 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
> sender. my basic ru
> This plugin might be able to reject unwanted mail during the original
> smtp transaction if it sent a URL back at that time. The origin MTA
> would have to pass that on to the user, but then you would not even
> need the captcha at that point. Visiting the page could be enough to
> enable the ma
On Dec 7, 3:58 pm, [EMAIL PROTECTED] (M. Allan Noah) wrote:
> does this not turn your host into a backscatter joe-job spam zombie?
>
> allan
of course you should run all common qpsmtpd anti-spam plug-ins up-
front, like: no_dialup, geo_blacklist_whitelist, check_earlytalker,
and so on. Captcha res
autowhitelist_captcha
http://wiki.qpsmtpd.org/plugins:spam:autowhitelist_captcha
This plug-in is a whitelist which automatically maintains itself based
on well known and widely used Captcha authentication where a user must
identify characters within an image. You can define one ore more mail-
dom
> What are the two patches that need to be appied? (I don't see them in
> the plugins documentation).
I've updated the documentation in the Wiki:
Right now, this plug-in always returns DECLINED because recipient-
>host and sender->host are always empty
when a email address with IDN arrives into q
On Dec 4, 4:44 pm, [EMAIL PROTECTED] (Peter J. Holzer) wrote:
> As far as I can tell, this is not an issue for SMTP. The MUA is supposed
> to convert the domain name into ACE format (just like the browser
> is supposed to convert the domain name before sending an HTTP request).
> So MTAs always on
Hello,
I run one of the famous new IDN domains - those domains that contains
evil utf-8 characters, like german umlaute or japanese chars. IDN is
around for some years now and more of less supported in all browsers
at least for HTTP.
I was wondering if someone knows the status of IDN support for
11 matches
Mail list logo
