[- Tue 12.Mar'13 at 18:47:00 -0500 Larry Stone :-]
On Mar 12, 2013, at 6:37 PM, Archangel killerpeptobis...@gmail.com wrote:
Ok, Postfix is acting like a three year old.
When I try to send e-mail in roudcube, it returns, Relay access denied.
I telnet to port 25 on
Archangel skrev den 2013-03-13 00:37:
Ok, Postfix is acting like a three year old.
+1
you did not show postconf -n here
When I try to send e-mail in roudcube, it returns, Relay access
denied.
and you used port 25
I telnet to port 25 on the server, ehlo and rcpt from
without a problem.
Hello postfix-users,
I'd like to somehow get/forward the SASL username of an authenticated
user to a before-queue SMTP content filter that is connected via
smtpd_proxy_filter.
I know I can use smtpd_sasl_authenticated_header = yes, but that is
not quite what I want or need as the scanner can only
Hi!
I am trying to set up mail relays for our domain. Basically, the relays
should only route e-mails to their destination. They are not supposed
to deliver any e-mails locally. Relays are also supposed to masquerade
server names. All mail accounts for our domain reside on a central
mailbox
On Mar 13, 2013, at 09:47, Christian Rohmann crohm...@netcologne.de wrote:
Hello postfix-users,
I'd like to somehow get/forward the SASL username of an authenticated
user to a before-queue SMTP content filter that is connected via
smtpd_proxy_filter.
I know I can use
[- Wed 13.Mar'13 at 10:47:09 +0100 Gerald Vogt :-]
Hi!
I am trying to set up mail relays for our domain. Basically, the relays
should only route e-mails to their destination. They are not supposed
to deliver any e-mails locally. Relays are also supposed to masquerade
he smtpd_relay_restrictions is intended for relay decisions
only[1]. In this case, that looks like it would be:
authenticated_smtpd_relay_restrictions =
permit_sasl_authenticated
reject_unauth_destination
(and I suggest plain old reject, rather than
reject_unauth_destination on the
On 13.03.2013 11:07, James Griffin wrote:
virtual_alias_domains = example.com
virtual_alias_maps = hash:/etc/postfix/virtual
/etc/postfix/virtual:
u...@example.comu...@mailbox.example.com
first.l...@example.com u...@mailbox.example.com
Perhaps you should add the fqdn to
On 13.03.2013 11:29, DTNX Postmaster wrote:
Masquerading is intended for outgoing only, AFAIK, see;
http://www.postfix.org/postconf.5.html#masquerade_domains
Why not use 'transport_maps', if you are not delivering any mail
locally?
example.com relay:[mailbox.example.com]
You
Please keep this on-list. I'm not doing personal support for free.
On 2013-03-12 Archangel wrote:
mydestination = bayesianmarketing.com, mediaserver, localhost.localdomain,
localhost
myhostname = bayesianmarketing.com
mynetworks = 127.0.0.0/8 [:::127.0.0.0]/104 [::1]/128
[...]
mail.log:
On Mar 13, 2013, at 11:37, Gerald Vogt v...@spamcop.net wrote:
On 13.03.2013 11:29, DTNX Postmaster wrote:
Masquerading is intended for outgoing only, AFAIK, see;
http://www.postfix.org/postconf.5.html#masquerade_domains
Why not use 'transport_maps', if you are not delivering any mail
On 13.03.2013 14:40, DTNX Postmaster wrote:
On Mar 13, 2013, at 11:37, Gerald Vogt v...@spamcop.net wrote:
On 13.03.2013 11:29, DTNX Postmaster wrote:
Masquerading is intended for outgoing only, AFAIK, see;
http://www.postfix.org/postconf.5.html#masquerade_domains
Why not use
Hello,
I have installed an autoresponder using a perl script and special
transport (autoreply) in master.cf
my problem is that postfix send the email to the perl script twice so
the perl script sends two mails to the recipient instead of one as i wish.
when an user has set up its
On 3/12/2013 11:22 PM, Alex wrote:
header_checks = pcre:/etc/postfix/header_checks.pcre
pcre:/etc/postfix/header_checks-jimsun.pcre
Are the jimsum checks still effective? I thought these were years
old, and I wouldn't expect them to do much good.
Not really. I just use it to outright
Gerald Vogt:
Any hostname/subdomain under example.com is local. That's what I want to
tell postfix. And that regardless of what comes after the @ but in our
domain, I know all the names which can appear before the @.
IMHO, that should not require to list all possible server names...
Use a
On 3/13/2013 5:13 AM, Christian Rößner wrote:
he smtpd_relay_restrictions is intended for relay decisions
only[1]. In this case, that looks like it would be:
authenticated_smtpd_relay_restrictions =
permit_sasl_authenticated
reject_unauth_destination
(and I suggest plain old reject,
On 13.03.2013 15:22, Wietse Venema wrote:
Gerald Vogt:
Any hostname/subdomain under example.com is local. That's what I want to
tell postfix. And that regardless of what comes after the @ but in our
domain, I know all the names which can appear before the @.
IMHO, that should not require to
Gerald Vogt:
On 13.03.2013 15:22, Wietse Venema wrote:
Gerald Vogt:
Any hostname/subdomain under example.com is local. That's what I want to
tell postfix. And that regardless of what comes after the @ but in our
domain, I know all the names which can appear before the @.
IMHO, that
On 13.03.2013 15:54, Wietse Venema wrote:
2. This still won't help to accept e-mails for users regardless of what
comes after the @ and reject it if the user does not exist.
To reject non-existent recipients, list the existing ones in
relay_recipient_maps. If you can't populate that table,
Gerald Vogt:
On 13.03.2013 15:54, Wietse Venema wrote:
2. This still won't help to accept e-mails for users regardless of what
comes after the @ and reject it if the user does not exist.
To reject non-existent recipients, list the existing ones in
relay_recipient_maps. If you can't
On 13.03.2013 16:22, Wietse Venema wrote:
Gerald Vogt:
On 13.03.2013 15:54, Wietse Venema wrote:
2. This still won't help to accept e-mails for users regardless of what
comes after the @ and reject it if the user does not exist.
To reject non-existent recipients, list the existing ones in
On 3/13/2013 10:22 AM, Wietse Venema wrote:
Gerald Vogt:
On 13.03.2013 15:54, Wietse Venema wrote:
2. This still won't help to accept e-mails for users regardless of what
comes after the @ and reject it if the user does not exist.
To reject non-existent recipients, list the existing ones in
On Wed, Mar 13, 2013 at 01:48:57PM +0100, Ansgar Wiechers wrote:
Mar 12 17:13:01 mediaserver postfix/smtpd[12785]: NOQUEUE: reject: RCPT
from ip68-227-115-116.ok.ok.cox.net[68.227.115.116]: 451 4.3.5
recipi...@domain.com: Recipient address rejected: Server configuration
error;
Hi,
Am 13.03.2013 um 15:29 schrieb Noel Jones njo...@megan.vbhcs.org:
A permit from one smtpd_*_restrictions section does not pass to
the next section. For mail to be accepted, each
smtpd_*_restrictions section must evaluate to permit or OK.
thanks. This is the key information that I was
Gerald Vogt:
Unfortunately, Postfix has (up to now) no way to feed the result
from one table into another table, but there is a workaround
which requires Postfix 2.7 or later:
Too bad. I have a Centos 6 with postfix 2.6.6
That's a 4-year old code base. It was unfortunately not possible
On 13.03.2013 11:29, DTNX Postmaster wrote:
Masquerading is intended for outgoing only, AFAIK, see;
http://www.postfix.org/postconf.5.html#masquerade_domains
According to this:
http://www.postfix.org/ADDRESS_REWRITING_README.html#receiving
masquerading is done when mail is received.
But
Wietse Venema:
Gerald Vogt:
Unfortunately, Postfix has (up to now) no way to feed the result
from one table into another table, but there is a workaround
which requires Postfix 2.7 or later:
Too bad. I have a Centos 6 with postfix 2.6.6
That's a 4-year old code base. It was
On 2013-03-13 Viktor Dukhovni wrote:
On Wed, Mar 13, 2013 at 01:48:57PM +0100, Ansgar Wiechers wrote:
Mar 12 17:13:01 mediaserver postfix/smtpd[12785]: NOQUEUE: reject:
RCPT from ip68-227-115-116.ok.ok.cox.net[68.227.115.116]: 451 4.3.5
recipi...@domain.com: Recipient address rejected: Server
On Wed, Mar 13, 2013 at 12:58:16PM -0400, Wietse Venema wrote:
Analogous to Noel's suggestion, one possibility is that you list
bare usernames (without @example.com etc.) in relay_recipient_maps.
It's not documented, but I could add that note since the behavior is
not going to change.
On Wed, Mar 13, 2013 at 06:35:41PM +0100, Ansgar Wiechers wrote:
No, it is generally safe to do recipient access lookups, even before
anti-relay policy, since the recipient cannot be spoofed. Just don't
allow mail to recipients in outside domains.
The latter is what I meant by prone to
Am 13.03.2013 20:45, schrieb Archangel:
here's the output of the grep command on mail.log:
Mar 12 17:13:01 mediaserver postfix/smtpd[12785]: error: open database
/etc/postfix/filtered_domains.db: No such
file or directory
Mar 12 17:13:01 mediaserver postfix/smtpd[12785]: connect from
On 2013-03-13 Archangel wrote:
here's the output of the grep command on mail.log:
Mar 12 17:13:01 mediaserver postfix/smtpd[12785]: error: open database
/etc/postfix/filtered_domains.db: No such file or directory
Well, the error message is rather self-explanatory. You advised Postfix
to check
Le 13/03/2013 15:01, Arnaud Jayet a écrit :
Hello,
I have installed an autoresponder using a perl script and special
transport (autoreply) in master.cf
does your autoresponder obeys
http://tools.ietf.org/html/rfc3834
?
if not, get it out.
my problem is that postfix send the email to
33 matches
Mail list logo
