Hi Noel,
I just tested Your solution, but its not working with multiple RCPT TO:
When I`m sending an E-mail using telnet command, an email with single RCPT
TO: zalezny.niezale...@gmail.com is working fine. its blocked.
But when I will put second RCPT TO: u...@domain.com, then both E-mails are
se
Hi everybody,
I have a Postfix smarthost and a Postfix client who shall send mails
through that smathost using a TLS-certificate.
I don't get the client to send the certificate to the smarhost though.
The error is:
Anonymous TLS connection established from client.example.com [...]
smart
On 2016-06-29 10:59, Zalezny Niezalezny wrote:
But when I will put second RCPT TO: u...@domain.com, then both E-mails
are send, even that restricted by transport table.
header_checks is not pr recipient so it does not work
if you like to make pr recipient use check_policy_service
but check_p
Zalezny Niezalezny:
> Hi Noel,
>
> I just tested Your solution, but its not working with multiple RCPT TO:
>
> When I`m sending an E-mail using telnet command, an email with single RCPT
> TO: zalezny.niezale...@gmail.com is working fine. its blocked.
> But when I will put second RCPT TO: u...@dom
Hi friends.
I need to limit the number of addresses in the "To:" in messages from my
server domain users.
It is possible?
Sorry my bad english
Thanks.
Marcelo
--
View this message in context:
http://postfix.1071664.n5.nabble.com/Number-of-address-in-To-tp84617.html
Sent from the Postfix U
Hi,
@Wietse, than You for Your feedback.
Now its working with transport map.
domain.com relay:[smtp1.domain.local]
domain.com relay:[smtp.domain.local]
* error: Only one is allowed
With "error:" parameter Postfix filtering is working like a charm. :)
On 6/29/2016 5:25 AM, Tom Fernandes wrote:
> Hi everybody,
>
> I have a Postfix smarthost and a Postfix client who shall send mails
> through that smathost using a TLS-certificate.
>
> I don't get the client to send the certificate to the smarhost though.
>
> The error is:
> Anonymous TLS connec
Chip wrote:
> My mistake NOT "bounces-to" rather "return-path"
Return-path is a header added by the receiving MTA (usually on final
delivery) that contains the envelope sender (MAIL FROM) used by the
sending system.
> as in the following
> snippet of campaign emails from Home Depot, Martha Stewar
I need to configure alternative smarthosts for the same domain with a
defined order of preference (and different smarthosts for other
domains).
One solution is to not use smarthosts in Postfix but instead configure
MX records in the local DNS server, as suggested by Viktor here:
http://postfix.107
If Return-path is added by receiving MTA, as you say, below, and that it
contains the MAIL FROM, then why do I see the following in source code
of received message in which return-path does not match From?
X-Mozilla-Status: 0001
X-Mozilla-Status2:
X-Mozilla-Keys:
Return-path:
From: "
Le 29/06/2016 17:02, Chip a écrit :
If Return-path is added by receiving MTA, as you say, below, and that it
contains the MAIL FROM, then why do I see the following in source code
of received message in which return-path does not match From?
X-Mozilla-Status: 0001
X-Mozilla-Status2:
X-
On 29/06/16 17:02, Chip wrote:
> If Return-path is added by receiving MTA, as you say, below, and that it
> contains the MAIL FROM, then why do I see the following in source code
> of received message in which return-path does not match From?
Could I respectfully suggest that you read up on the di
I will read up on it. Thank you for the link.
Not everyone, I think, who visits this list is an engineer.
So it would have been easier to understand if the response had been
along the lines of:
"envelope-from" instead of just FROM since there are a number of Froms
in the source code.
Some
> I will read up on it. Thank you for the link.
>
> Not everyone, I think, who visits this list is an engineer.
In that you are mistaken.
Almost everyone who subscribes to this mailing-list is an engineer.
Please re-read that line.
This mailing list is for people who need to configure or make
On 6/29/16 2:30 PM, Michael J Wise wrote:
I will read up on it. Thank you for the link.
Not everyone, I think, who visits this list is an engineer.
In that you are mistaken.
Almost everyone who subscribes to this mailing-list is an engineer.
Please re-read that line.
This mailing list is fo
> On 6/29/16 2:30 PM, Michael J Wise wrote:
>
>>> I will read up on it. Thank you for the link.
>>>
>>> Not everyone, I think, who visits this list is an engineer.
>> In that you are mistaken.
>>
>> Almost everyone who subscribes to this mailing-list is an engineer.
>> Please re-read that line.
>
On 6/29/16 3:13 PM, Michael J Wise wrote:
On 6/29/16 2:30 PM, Michael J Wise wrote:
I will read up on it. Thank you for the link.
Not everyone, I think, who visits this list is an engineer.
In that you are mistaken.
Almost everyone who subscribes to this mailing-list is an engineer.
Please
> On Jun 29, 2016, at 1:06 PM, Miles Fidelman
> wrote:
>
> AND NOW I'M CURIOUS... What kinds of backgrounds and roles do people here
> have? Is managing a postfix installation part of your official duties, or
> something that you've fallen into?
CS degree from before the 'Net, missed the 'N
> On 6/29/16 3:13 PM, Michael J Wise wrote:
>
>>> On 6/29/16 2:30 PM, Michael J Wise wrote:
>>>
> I will read up on it. Thank you for the link.
>
> Not everyone, I think, who visits this list is an engineer.
In that you are mistaken.
Almost everyone who subscribes to th
> On Jun 29, 2016, at 8:25 PM, Tom Fernandes wrote:
>
> But when the postfix client authenticates it does not send the certificate.
>
> What am I missing?
>
> --main.cf non-default parameters--
> ...
> smtpd_sasl_type = dovecot
> smtpd_tls_cert_file = /etc/ssl/certs/mail_domain_de.crt
> sm
I noticed I was running postfix 3.1.0. Freebsd has rev 3.1.1, so I
figured I would upgrade.
Fist up, I reviewed the page I used as a starting point for setting up
my mail server, namely
http://blog.iandreev.com/?p=1604
In the configuration for postfix, the SPF option is not selected.
Somewhere i
I recently updated a server's Ubuntu version, and multi-domain
sender-dependent transport for Postfix has stopped working. Postfix is
now at 2.11.0, but I'm not actually sure what version it was at before.
This installation serves two domains, one of which is the one I'm using
to send this message
Eric Abrahamsen writes:
> I recently updated a server's Ubuntu version, and multi-domain
> sender-dependent transport for Postfix has stopped working. Postfix is
> now at 2.11.0, but I'm not actually sure what version it was at before.
>
> This installation serves two domains, one of which is the
23 matches
Mail list logo
