Victor Duchovni schrieb:
On Wed, Sep 30, 2009 at 11:26:30PM +0200, Patrick Ben Koetter wrote:
ldap:/some/file.cf
Thanks, that solved it. *shame*
What happens if you don't use it properly? Why does it fall back to using
localhost then?
The table name is assumed to refer to a parameter
Hello list,
This might be working as intended, but since it seemed a tad odd and I
couldn't find any conclusive documentation that explained it, I
figured I'd work up the courage and ask. I moved 'check_sender_access'
from the 'smtpd_sender_restrictions' to the
'smtpd_recipient_restrictions'
* URCentral Support (GMail) urcent...@gmail.com:
Hello list,
This might be working as intended, but since it seemed a tad odd and I
couldn't find any conclusive documentation that explained it, I
figured I'd work up the courage and ask. I moved 'check_sender_access'
from the
Dan Schaefer wrote:
Email address: mail...@example.com
Aliases: ali...@example.com
ali...@example.com
ali...@example.com
What I want to accomplish is any email being sent to
mail...@example.com to be put into the mail...@example.com's Inbox and
1 copy to be sent to the 3 aliases. I'm using
Hi all,
could you give me any clue how to accomplish following:
1. I need to configure postfix to allow some users only receive emails.
They can download received emails by outlook or other client from postfix
server,
but they are prohibited to send one.
2. The second group of users
Dan Schaefer:
Dan Schaefer wrote:
Email address: mail...@example.com
Aliases: ali...@example.com
ali...@example.com
ali...@example.com
What I want to accomplish is any email being sent to
mail...@example.com to be put into the mail...@example.com's Inbox and
1 copy to be sent
Wietse Venema wrote:
Dan Schaefer:
Dan Schaefer wrote:
Email address: mail...@example.com
Aliases: ali...@example.com
ali...@example.com
ali...@example.com
What I want to accomplish is any email being sent to
mail...@example.com to be put into the mail...@example.com's Inbox and
1
Is there an unofficial Postfix VCS repository? I believe there is not an
official one, is there a reason for that? I'm asking because I want to
keep track of what is going on 2.7 development. Checking the release
notes file or the change log file is not very practical.
Regards,
Miguel
My expertise with email servers protocols is very limited. That
being said, here is a problem I've been dealing with for a few hours
now without finding a suitable solution:
I run a box in Amazon's EC2, and I use postfix. In order to avoid
being marked as a SPAM source because of EC2's IPs being
Hi,
I'm using dovecot for SASL authentication:
smtpd_sasl_auth_enable = yes
smtpd_recipient_restrictions =
permit_mynetworks
permit_sasl_authenticated
reject_unauth_destination
smtpd_sasl_type = dovecot
smtpd_sasl_path = private/auth-client
Now if for whatever reason dovecot is not
* Hagen Fürstenau hfuerste...@gmx.net:
Hi,
I'm using dovecot for SASL authentication:
smtpd_sasl_auth_enable = yes
smtpd_recipient_restrictions =
permit_mynetworks
permit_sasl_authenticated
reject_unauth_destination
smtpd_sasl_type = dovecot
smtpd_sasl_path =
Hi all,
I need to add another filter to my existing anti-virus one.
I've allready set an advanced content filter like the example in the
Postfix After-Queue Content tutorial.
Postfix Queue -- Port 10025 (Anti-Virus+AntiSpam)-- that reinject mails
through the 10026 port to postfix -- delivery
Peter Macko kirjoitti:
Hi all,
could you give me any clue how to accomplish following:
1. I need to configure postfix to allow some users only receive emails.
They can download received emails by outlook or other client from
postfix server,
but they are prohibited to send one.
2. The
Now if for whatever reason dovecot is not running, smtpd will also
refuse to work, complaining fatal: no SASL authentication mechanisms.
Indeed!
I would much prefer it to fall back to smtpd_sasl_auth_enable = no in
that case, so that mail for local recipients can still be received. Is
this
* Darvin Denmian darvin.denm...@gmail.com:
Hello,
Currently I'm using content_filter to filter inbound messages.
How?
Now I need to know if is possible to do something like content_filter
for outbound messages.
Every outbound message was inbound once, no?
--
Ralf Hildebrandt
RBsussy:/var/log # postfix -n
postfix: invalid option -- 'n'
postfix: fatal: usage: postfix [-c config_dir] [-Dv] command
sussy:/var/log #
postconf -n
Oct 1 23:02:05 sussy postfix/scache[1715]: statistics: start interval
Oct 1 22:58:45 Oct 1 23:02:05 sussy postfix/scache[1715]:
On Thu, Oct 1, 2009 at 12:56 PM, Ralf Hildebrandt
ralf.hildebra...@charite.de wrote:
Is this by design, working as intended? Or am I missing something somewhere?
Where's the main.cf snippet?
Guess I did miss something somewhere. This is how it looks like now;
smtpd_sender_restrictions =
My understanding of client and sender are these:
Client: An application used to send, receive e-mail messages.
Sender: The from or sender name in the header that shows who (is
claimed to have) sent the email.
The context of the use that has me concerned are these:
smtpd_client_restrictions and
Dan Schaefer wrote:
Wietse Venema wrote:
Dan Schaefer:
Dan Schaefer wrote:
Email address: mail...@example.com
Aliases: ali...@example.com
ali...@example.com
ali...@example.com
What I want to accomplish is any email being sent to
mail...@example.com to be put into the
On Wed, 30 Sep 2009 22:12:15 -0500
Stan Hoeppner s...@hardwarefreak.com wrote:
Ricky Tompu Breaky put forth on 9/30/2009 5:10 PM:
Sending failed:
Your SMTP server does not support The server responded: 5.7.8
Error: authentication failed: generic failure. Choose a different
On Thu, 01 Oct 2009 19:41:14 +0300
Eero Volotinen eero.voloti...@iki.fi wrote:
RBsussy:/var/log # postfix -n
postfix: invalid option -- 'n'
postfix: fatal: usage: postfix [-c config_dir] [-Dv] command
sussy:/var/log #
postconf -n
RBWupps... Shame on me. Sorry.
sussy:~ # postconf -n
sussy:~ # postconf -n
alias_maps = hash:/etc/aliases
biff = no
body_checks = regexp:/etc/postfix/body_checks
broken_sasl_auth_clients = yes
canonical_maps = hash:/etc/postfix/canonical
command_directory = /usr/sbin
config_directory = /etc/postfix
content_filter = amavis:[127.0.0.1]:10024
Robert Lopez wrote:
My understanding of client and sender are these:
Client: An application used to send, receive e-mail messages.
Sender: The from or sender name in the header that shows who (is
claimed to have) sent the email.
Indeed.
The context of the use that has me concerned are
On Thu, 01 Oct 2009 19:59:51 +0300
Eero Volotinen eero.voloti...@iki.fi wrote:
...
Well, default config on suse? is really messy, maybe you can take
basic config from postfix and start with it?
RBYes, you're right Eero It's from OpenSuSE11.1 MMM... Do you
RBhave the sample of
Ricky Tompu Breaky kirjoitti:
On Thu, 01 Oct 2009 19:59:51 +0300
Eero Volotinen eero.voloti...@iki.fi wrote:
...
Well, default config on suse? is really messy, maybe you can take
basic config from postfix and start with it?
RBYes, you're right Eero It's from OpenSuSE11.1 MMM...
On Thu, 01 Oct 2009 20:15:52 +0300
Eero Volotinen eero.voloti...@iki.fi wrote:
Ricky Tompu Breaky kirjoitti:
On Thu, 01 Oct 2009 19:59:51 +0300
Eero Volotinen eero.voloti...@iki.fi wrote:
...
Well, default config on suse? is really messy, maybe you can take
basic config from
On Thu, Oct 1, 2009 at 6:46 PM, URCentral @ Gmail urcent...@gmail.com wrote:
Is this by design, working as intended? Or am I missing something somewhere?
Where's the main.cf snippet?
Guess I did miss something somewhere. This is how it looks like now;
smtpd_sender_restrictions =
On Wed, Sep 30, 2009 at 11:39:12PM +0200, Patrick Ben Koetter wrote:
* Jay G. Scott g...@arlut.utexas.edu:
okay, maybe i'm catching on.
i set up the /etc/sasldb2 method of authentication.
that's doing so far what i want.
1. okay, i guess /etc/postfix/sasl_passwd is only
Ricky Tompu Breaky wrote:
On Thu, 01 Oct 2009 20:15:52 +0300
Eero Volotinen eero.voloti...@iki.fi wrote:
Ricky Tompu Breaky kirjoitti:
On Thu, 01 Oct 2009 19:59:51 +0300
Eero Volotinen eero.voloti...@iki.fi wrote:
...
Well, default config on suse? is really messy, maybe you can take
URCentral @ Gmail wrote:
On Thu, Oct 1, 2009 at 6:46 PM, URCentral @ Gmail urcent...@gmail.com wrote:
Which works; if 'postmas...@configcast.com' is used as a sender, it
rejects the rest of the SMTP session, but if used as a recipient, it's
fine, as expected. If I move
Miguel Di Ciurcio Filho:
Is there an unofficial Postfix VCS repository? I believe there is not an
official one, is there a reason for that? I'm asking because I want to
keep track of what is going on 2.7 development. Checking the release
notes file or the change log file is not very
Wietse Venema wrote:
Miguel Di Ciurcio Filho:
Is there an unofficial Postfix VCS repository? I believe there is not an
official one, is there a reason for that? I'm asking because I want to
keep track of what is going on 2.7 development. Checking the release
notes file or the change log
Jose Maria Sanchez de Ocana:
OK, so now here is my problem: When my postfix receives a SPAM message
bound for one of my accounts, this email is forwarded to gmail's SMTP
server directly. But then gmail's SPAM filter rejects this message and
here starts my problem. AFAIK what postfix should do
On Thu, 2009-10-01 at 13:27 -0400, Wietse Venema wrote:
Miguel Di Ciurcio Filho:
Is there an unofficial Postfix VCS repository? I believe there is not an
official one, is there a reason for that? I'm asking because I want to
keep track of what is going on 2.7 development. Checking the
On Thu, Oct 1, 2009 at 7:26 PM, Brian Evans - Postfix List
grkni...@scent-team.com wrote:
Correcting myself; there are two hash databases specified on the live
server, like this;
check_sender_access
hash:/etc/postfix/chk_sender_local
URCentral @ Gmail wrote:
On Thu, Oct 1, 2009 at 7:26 PM, Brian Evans - Postfix List
grkni...@scent-team.com wrote:
Correcting myself; there are two hash databases specified on the live
server, like this;
check_sender_access
hash:/etc/postfix/chk_sender_local
On Thu, Oct 1, 2009 at 11:02 AM, Brian Evans - Postfix List
grkni...@scent-team.com wrote:
Robert Lopez wrote:
snip
check_client_access=hash:/etc/postfix/access
smtpd_client_restrictions =
permit_mynetworks
hash:/etc/postfix/whitelist
This is depreciated syntax equivalent to
On Thursday 01 October 2009 11:47:47 Robert Lopez wrote:
My understanding of client and sender are these:
Client: An application used to send, receive e-mail messages.
In the context of check_client_access it means the IP address and/or
forward-confirmed reverse DNS name of the client
Brian Evans - Postfix List:
Wietse Venema wrote:
Miguel Di Ciurcio Filho:
Is there an unofficial Postfix VCS repository? I believe there is not an
official one, is there a reason for that? I'm asking because I want to
keep track of what is going on 2.7 development. Checking the
Wietse Venema wrote:
Brian Evans - Postfix List:
Wietse Venema wrote:
Miguel Di Ciurcio Filho:
Is there an unofficial Postfix VCS repository? I believe there is not an
official one, is there a reason for that? I'm asking because I want to
keep track of what is going on
RBps: What is 'rtfm'? What does that stand for?
It means that you need to read the friendly manual on the long run.
--
Eero
On 1-Oct-2009, at 12:42, Eero Volotinen wrote:
RBps: What is 'rtfm'? What does that stand for?
It means that you need to read the friendly manual on the long run.
The 'f' does not stand for 'friendly'.
Read The F-ing Manual
--
I know she's in there, said Verence, holding his crown in his
On Thu, Oct 1, 2009 at 12:56 PM, Ricky Tompu Breaky ricky.bre...@uni.de wrote:
On Thu, 01 Oct 2009 19:41:14 +0300
Eero Volotinen eero.voloti...@iki.fi wrote:
RBsussy:/var/log # postfix -n
postfix: invalid option -- 'n'
postfix: fatal: usage: postfix [-c config_dir] [-Dv] command
LuKreme kirjoitti:
On 1-Oct-2009, at 12:42, Eero Volotinen wrote:
RBps: What is 'rtfm'? What does that stand for?
It means that you need to read the friendly manual on the long run.
The 'f' does not stand for 'friendly'.
Read The F-ing Manual
Well, there are many variations:
I'm trying to setup before queue filtering using policyd-weight but
can't get my configuration right. Could someone please point out what
I've done wrong...
My policyd-weight.conf contains only this:
$TCP_PORT= 12524;
My main.cf contains the following relevant lines:
soft_bounce = yes
Kevin Gagel wrote:
I'm trying to setup before queue filtering using policyd-weight but
can't get my configuration right. Could someone please point out what
I've done wrong...
[snip]
When I use the above settings I end up with no mail flowing and tons
of error messages stating:
Out: 451
Kevin Gagel:
When I use the above settings I end up with no mail flowing and tons
of error messages stating:
Out: 451 4.3.0 Error: queue file write error
Perhaps surprisingly, Postfix writes the details of the problem to
the mailog file, not to the SMTP client.
Wietse
On Oct 1, 2009, at 12:17 PM, LuKreme krem...@kreme.com wrote:
Read The F-ing Manual
Fishing? I always thought it was read the fine manual.
--
If this was a real .signature it would be more interesting.
Euro,
Especially for you, I highly appreciate your help so (much) far.
Thank you thousands time.
Let me dip my concentration in the documentation and information I get
from this mailing list.
Again thank you...thank you...thank you...
===
On Thu, 01 Oct 2009 21:42:02 +0300
Eero Volotinen
I don't how to say thank you.
I highly appreciate your help so (much) far.
Thank you thousands time.
Let me dip my concentration in the documentation and information I get
from this mailing list.
Again thank you...thank you...thank you...
On Thu, 01 Oct 2009 10:25:55 -0700
Seth Mattinen
On Thu, Oct 01, 2009 at 01:46:51PM -0400, Wietse Venema wrote:
Then we agree. A system that computes SHA1 without secret key
provides no detection of after-the-fact changes.
Except that the SHA-1 signature is just 20 bytes covering the entire
tree, and there are *many* trees (no single
OK, reconfigured to:
main.cf
smtpd_recipient_restrictions = reject_non_fqdn_recipient,
reject_non_fqdn_sender,
reject_non_fqdn_recipient,
reject_unknown_sender_domain,
check_sender_mx_access cidr:/etc/postfix/wildcard_mx_records.cidr,
permit_mynetworks,
check_client_access
On Thu, 01 Oct 2009 22:25:35 +0300
Eero Volotinen eero.voloti...@iki.fi wrote:
http://en.wikipedia.org/wiki/RTFM
RBYes, but this mailing-list has made so much further step for my
RBunderstanding. Now it's my turn to work on it alone. The information
RBI got is already enough. I think now I can
On Thu, 1 Oct 2009 15:22:39 -0400
Aaron Wolfe aawo...@gmail.com wrote:
On Thu, Oct 1, 2009 at 12:56 PM, Ricky Tompu Breaky
ricky.bre...@uni.de wrote:
On Thu, 01 Oct 2009 19:41:14 +0300
Eero Volotinen eero.voloti...@iki.fi wrote:
RBsussy:/var/log # postfix -n
postfix: invalid
Kevin Gagel wrote:
OK, reconfigured to:
main.cf
smtpd_recipient_restrictions = reject_non_fqdn_recipient,
reject_non_fqdn_sender,
reject_non_fqdn_recipient,
reject_unknown_sender_domain,
check_sender_mx_access cidr:/etc/postfix/wildcard_mx_records.cidr,
permit_mynetworks,
Ricky Tompu Breaky kirjoitti:
On Thu, 01 Oct 2009 22:25:35 +0300
Eero Volotinen eero.voloti...@iki.fi wrote:
http://en.wikipedia.org/wiki/RTFM
RBYes, but this mailing-list has made so much further step for my
RBunderstanding. Now it's my turn to work on it alone. The information
RBI got is
Eero Volotinen wrote:
read the: http://www.poor-attitude.org/postfix/basic.html
This page is horribly out of date and should not be referenced. (it's
about Postfix 1.x)
On Thu, Oct 01, 2009 at 03:08:31PM +0200, Hagen F??rstenau wrote:
I'm using dovecot for SASL authentication:
smtpd_sasl_auth_enable = yes
smtpd_recipient_restrictions =
permit_mynetworks
permit_sasl_authenticated
reject_unauth_destination
smtpd_sasl_type = dovecot
On Thu, Oct 01, 2009 at 09:35:02AM +0200, Jakob Lenfers wrote:
I find the manpage not clear on that issue, perhaps it could be said
more explicitly here...
|file_name
| The name of the lookup table source file when rebuilding
a database.
Wietse Venema put forth on 10/1/2009 12:34 PM:
The REAL mistake in your setup is that you forward SPAM into gmail.
This causes gmail to treat your machine as a SPAMMER, and may affect
legitimate mail that you do want to receive.
110% correct.
You must NEVER bounce SPAM to the sender
Robert Lopez wrote:
My understanding of client and sender are these:
Client: An application used to send, receive e-mail messages.
No. the client is the IP node. so it's either the IP of the reverse DNS
of the host that is trying to send mail. regarding reverse dns, if it is
not confirmed, then
Darvin Denmian wrote:
Ralf,
I'm testing this using:
master.cf :
# Inbound
smtp inet n - - - - smtpd -v
-o content_filter=filter:dummy
filterunix - n n - 10 pipe
flags=Rq user=filter null_sender=
Ralf Hildebrandt wrote:
* Hagen Fürstenau hfuerste...@gmx.net:
Hi,
I'm using dovecot for SASL authentication:
smtpd_sasl_auth_enable = yes
smtpd_recipient_restrictions =
permit_mynetworks
permit_sasl_authenticated
reject_unauth_destination
smtpd_sasl_type = dovecot
mouss,
as you said , if I use content_filter=filter:localhost:port
and my filter is able to reinject the message in postfix queue,
Postfix will check inbound and outbound messages, right?
Thanks!!!
On Thu, Oct 1, 2009 at 6:46 PM, mouss mo...@ml.netoyen.net wrote:
Darvin Denmian wrote:
mouss,
as you said , if I use content_filter=3Dfilter:localhost:port
and my filter is able to reinject the message in postfix queue,
Postfix will check inbound and outbound messages, right?
Thanks!!!
On Thu, Oct 1, 2009 at 6:46 PM, mouss mo...@ml.netoyen.net wrote:
Darvin Denmian wrote:
Ricky Tompu Breaky put forth on 10/1/2009 2:54 PM:
Let me dip my concentration in the documentation and information I get
from this mailing list.
Dip into one or more of these as well:
http://www.fredshack.com/docs/postfix.html
Brian Evans - Postfix List put forth on 10/1/2009 3:03 PM:
Kevin Gagel wrote:
Now I get these errors:
Oct 1 12:54:59 gateway postfix/smtpd[14635]: warning: connect to
127.0.0.1:12524: Connection refused
Oct 1 12:54:59 gateway postfix/smtpd[14635]: warning: problem talking
to server
Robert Lopez put forth on 10/1/2009 11:47 AM:
My understanding of client and sender are these:
Client: An application used to send, receive e-mail messages.
In the context of Postfix client restrictions, the _client_ is the
remote SMTP server that is sending email to your Postfix server. It is
68 matches
Mail list logo
