On May 18, 2012, at 07:22, Stan Hoeppner wrote:
A little OT, but I'd like to ask, as I've not been able to find real
information via Google. What's the memory consumption of a single spamd
process using the default SA configuration? Maybe a better question is
how much real RAM is SA eating
On Thu, May 17, 2012 at 01:19:52PM -0400, Wietse Venema wrote:
Ben Rosengart:
I enabled verbose mode in smtpd(8), but I don't know what to look for
Adding headers is implemented in cleanup(8).
Before or after header_checks?
Headers will never be
added when smtpd(8) is followed by a
Ben Rosengart:
On Thu, May 17, 2012 at 01:19:52PM -0400, Wietse Venema wrote:
Ben Rosengart:
I enabled verbose mode in smtpd(8), but I don't know what to look for
Adding headers is implemented in cleanup(8).
Before or after header_checks?
Between header_checks and
I'm heavily afraid this is a FAQ, but I couldn't find anything.
Short form: My impression is that not fully qualifying the value of relaylhost
causes Postfix to only look up records for it.
Long form:
I'm on NetBSD 6.0_BETA/amd64 with the supplied Postfix 2.8.8.
Basically I have the
Edgar Fu?:
Apperantly, Postfix only tries to look up an IPv6 address for smtp: I get
Host or domain name not found. Name service error for name=smtp
type=: Host not found
Postfix tries ALL CONFIGURED ADDRESS TYPES, and when NO CONFIGURED
ADDRESS TYPE works it logs the LAST ERROR.
Postfix tries ALL CONFIGURED ADDRESS TYPES,
Your capitalization of configured address types seems to imply this is a
well-defined term in the context of Postfix configuration, but sorry, I don't
know how it's defined.
and when NO CONFIGURED ADDRESS TYPE works
This seems to imply Postfix tried
Hi everyone,
I am having a problem trying to run dspam as an _after-queue_ content
filter on postfix with the
restriction that sasl authenticated users bypass dspam. All my users and
domains are virtual.
When I first installed postfix/dspam/dovecot I did not worry about
excluding my
Edgar Fu?:
Postfix tries ALL CONFIGURED ADDRESS TYPES,
Your capitalization of configured address types seems to imply
this is a well-defined term in the context of Postfix configuration,
but sorry, I don't know how it's defined.
Sorry for shouting, I did not have color or underline
The Postfix DNS client no longer appends the default domain.
Well, this explains it all, thanks.
I should read more RELEASE_NOTES, sorry.
On Fri, May 18, 2012 at 06:20:04AM -0400, Wietse Venema wrote:
Ben Rosengart:
On Thu, May 17, 2012 at 01:19:52PM -0400, Wietse Venema wrote:
Ben Rosengart:
I enabled verbose mode in smtpd(8), but I don't know what to look for
Adding headers is implemented in cleanup(8).
On Fri, May 18, 2012 at 10:11:10AM -0400, Ben Rosengart wrote:
I have one last problem, which is I have code (borrowed from Viktor)
which peeks at the files in the hold queue, and does special processing if
X-MS-Floodstopper is present.
That code is in turn borrowed from qshape(1), which
Ben Rosengart:
On Fri, May 18, 2012 at 06:20:04AM -0400, Wietse Venema wrote:
Ben Rosengart:
On Thu, May 17, 2012 at 01:19:52PM -0400, Wietse Venema wrote:
Ben Rosengart:
I enabled verbose mode in smtpd(8), but I don't know what to look for
Adding headers is implemented in
On Fri, May 18, 2012 at 02:27:11PM +, Viktor Dukhovni wrote:
2. I never liked milters (multi-threading complexity, and poor degradation
when CPU is scarce under high load).
If you strip away the API layer, it's a client/server protocol over a
socket, not so different from the
Ben Rosengart:
On Fri, May 18, 2012 at 02:27:11PM +, Viktor Dukhovni wrote:
2. I never liked milters (multi-threading complexity, and poor degradation
when CPU is scarce under high load).
If you strip away the API layer, it's a client/server protocol over a
socket, not so
On Fri, May 18, 2012 at 10:55:49AM -0400, Wietse Venema wrote:
Ben Rosengart:
On Fri, May 18, 2012 at 02:27:11PM +, Viktor Dukhovni wrote:
2. I never liked milters (multi-threading complexity, and poor
degradation
when CPU is scarce under high load).
If you strip
On May 18, 2012, at 7:41 AM, Chris wrote:
master.cf
-
smtp inet n - - - - smtpd
-o content_filter=lmtp:unix:/tmp/dspam.sock
Why did you remove that last line above? I thought about doing a before queue
content filter, but that really kills user's ability to train dspam. :)
Ben Rosengart:
On Fri, May 18, 2012 at 10:55:49AM -0400, Wietse Venema wrote:
Ben Rosengart:
On Fri, May 18, 2012 at 02:27:11PM +, Viktor Dukhovni wrote:
2. I never liked milters (multi-threading complexity, and poor
degradation
when CPU is scarce under high
Viktor Dukhovni wrote:
On Fri, May 18, 2012 at 10:11:10AM -0400, Ben Rosengart wrote:
...
2. I never liked milters (multi-threading complexity, and poor degradation
when CPU is scarce under high load).
Take a look at libmilter with a pool of workers. It's a FFR :
Hi Everyone.
I have a question.
We have a postfix server, it works great. All the users on that postfix
are added without home directory, we need to change the mbox default to
maildir in order to have dovecot working with IMAP.
We just changed the home_mailbox = Mailbox command to
On 5/18/2012 7:41 AM, Chris wrote:
Hi everyone,
I am having a problem trying to run dspam as an _after-queue_
content filter on postfix with the
restriction that sasl authenticated users bypass dspam. All my users
and domains are virtual.
When I first installed postfix/dspam/dovecot I
* Alfonso Alejandro Reyes Jimenez are...@ibossmonitor.com:
Hi Everyone.
I have a question.
We have a postfix server, it works great. All the users on that
postfix are added without home directory, we need to change the mbox
default to maildir in order to have dovecot working with IMAP.
I'm sorry you are right, I totally forgot that information.
Here it is:
[root@mail postfix]# postconf -n
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
broken_sasl_auth_clients = yes
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory =
Le 18/05/2012 18:11, Alfonso Alejandro Reyes Jimenez a écrit :
I'm sorry you are right, I totally forgot that information.
Please do not top post. google for top posting if this isn't clear.
keep reading.
[snip]
mail_spool_directory = /var/spool/mail
according to this, mail should be
Thanks and Sorry for the top posting.
here's the log you requested:
May 18 10:10:11 mail postfix/local[3912]: 3CB3E819F:
to=are...@mydomain.com, relay=local, delay=0.08, delays=0.04/0/0/0.04,
dsn=5.2.0, status=bounced (cannot update mailbox /home/areyes/Mailbox
for user areyes. unable to
Mouss.
Here's the updated configuration, I didn't attached the correct one.
[root@mail postfix]# postconf -n
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/aliases
broken_sasl_auth_clients = yes
command_directory = /usr/sbin
config_directory = /etc/postfix
daemon_directory =
Le 18/05/2012 07:22, Stan Hoeppner a écrit :
On 5/17/2012 11:44 PM, /dev/rob0 wrote:
[snip]
Note that you must disable restrictions on the reinjection from
content_filter. You do NOT want to reject at that point, because it
is risking backscatter.
Of course. But this is mostly a concern
Hi Chad,
If I leave the '-o content_filter' in for the smtp service then I assume
that authenticating users on port 25 will still pass through the dspam
filter because it will apply to all messages. A majority of my users use
port 25 as their outbound smtp server port in their mail clients.
Hi Noel,
The email from gmail.com in my example log comes in on port 25 - the 1st
line in master.cf. If I leave the -o
content_filter=lmtp:unix:/tmp/dspam.sock in instead of removing it,
then authenticating users who choose to use port 25 in their email
clients will also go through dspam as
Le 18/05/2012 19:25, Alfonso Alejandro Reyes Jimenez a écrit :
Mouss.
Here's the updated configuration, I didn't attached the correct one.
ah. so you have
home_mailbox = Maildir/
as
http://www.postfix.org/postconf.5.html#home_mailbox
says, Optional pathname of a mailbox file
Le 18/05/2012 20:06, Chris a écrit :
Hi Noel,
The email from gmail.com in my example log comes in on port 25 - the 1st
line in master.cf. If I leave the -o
content_filter=lmtp:unix:/tmp/dspam.sock in instead of removing it,
then authenticating users who choose to use port 25 in their email
On 5/18/2012 1:06 PM, Chris wrote:
Hi Noel,
The email from gmail.com in my example log comes in on port 25 - the
1st line in master.cf. If I leave the -o
content_filter=lmtp:unix:/tmp/dspam.sock in instead of removing it,
then authenticating users who choose to use port 25 in their email
thanks, the configuration is now as you suggest. But I'm having the same
issue:
May 18 14:45:27 mail postfix/local[5656]: warning: maildir access
problem for UID/GID=505/505: create maildir file
/home/test/Maildir/tmp/1337370327.P5656.mail.mydomain.com: Permission denied
May 18 14:45:27 mail
what exactly was unclear in Please do not top post. google for top posting
if this isn't clear.?
(yes my post is also top-posting because the thread is still unreadable)
Am 18.05.2012 21:56, schrieb Alfonso Alejandro Reyes Jimenez:
thanks, the configuration is now as you suggest. But I'm having
On 5/18/12 3:02 PM, Wietse Venema wrote:
Alfonso Alejandro Reyes Jimenez:
thanks, the configuration is now as you suggest. But I'm having the same
issue:
May 18 14:45:27 mail postfix/local[5656]: warning: maildir access
problem for UID/GID=505/505: create maildir file
On Fri, May 18, 2012 at 02:19:14PM -0500, Noel Jones wrote:
On 5/18/2012 1:06 PM, Chris wrote:
The email from gmail.com in my example log comes in on port 25 - the
1st line in master.cf. If I leave the -o
content_filter=lmtp:unix:/tmp/dspam.sock in instead of removing it,
then
I recently upgraded my server to Debian 6.
One of the things that seems to have been changed in the Postfix-Dovecot
setup is the configuration of the mailbox_command.
In my old setup the command was
mailbox_command = /usr/lib/dovecot/dovecot-lda -f ${sender} *-d
${recipient}* -m ${extension}
36 matches
Mail list logo
