uting to postfix!
I hope this small addition can make it into the docs...
johnea
snippet from mail archives
to sum up:
- if f...@example.com can only be used by user 'foo', then use
reject_sender_login_mismatch
- if f...@example.com must be authent
sasl2/smtpd.conf
pwcheck_method: authdaemond
log_level: 3
mech_list: PLAIN LOGIN
authdaemond_path:/var/run/authdaemond/socket
The authentication sets you up for mobile sending.
Hope this helps...
johnea
strictions into recipient restrictions?
Or maybe just specify a blank helo restrictions line for submission in
the master.cf?
Thank You Very Much for sharing your expertise!
johnea
On 10/21/09 17:47, Sahil Tandon wrote:
On Wed, 21 Oct 2009, johnea wrote:
Generally, the output of 'postconf -n' is preferred in lieu of snippets
or entire main.cf dumps.
Next time, exclude the comments. :)
Will do, thank you for those tips
What ever you decide, just make s
inal) that SPAM messages often show up
for many users across different domains all at once.
Has anyone else tried such an approach? Is there any postfix infrastructure I
could adopt to implement such a strategy?
Also, could anyone recommend any other SPAM rejection policies I should put in
place?
Thank You!
johnea
Hello,
Is there a simple way to extract links from an email body and submit to DNSBL?
Thank You!
johnea
; in the EHLO response.
Hello Wietse,
Is it possible to use this to DNSBL check URLs present in the body of an email?
(pre-queue)
Thank you!
johnea
p.s. Sorry to diverge from the topic. I hope this isn't so far off as to
constitute thread hijacking.
to get them to
adopt a more efficient surveillance system.
Obviously Great God Google is the king of this, but many many minions also
participate (Constant Contact, etc).
Users outside of the above mentioned extremist minority have no idea, or care,
that they increase their vulnerability surface.
johnea
Could anyone say why the server side count would be less than the number shown
by the client?
Thank You!
johnea
