Hey again postfix-users,
On 13.03.2013 09:47, Christian Rohmann wrote:
1) Use the XCLIENT attribute LOGIN and have postfix send that to the
scanner. But I don't know if postfix even does send XCLIENT data to
another SMTP server (content filter in this case). I quick test showed
that postfix
On 2013-03-17 11:05, Ansgar Wiechers wrote:
On 2013-03-17 Per olof Ljungmark wrote:
We've had a working configuration since a few years where we allow
authenticated users to relay mail even if the sender address does not
match a local user and the recipient is non-local.
Now this is about to
Christian Rohmann:
Hey again postfix-users,
On 13.03.2013 09:47, Christian Rohmann wrote:
1) Use the XCLIENT attribute LOGIN and have postfix send that to the
scanner. But I don't know if postfix even does send XCLIENT data to
another SMTP server (content filter in this case). I quick
Per olof Ljungmark:
I'd recommend separating authenticated from unauthenticated submission.
Enable submission (port 587) with authentication required, and remove
permit_sasl_authenticated from the smtpd instance on port 25. For the
submission port you could enable
Mohsen Pahlevanzadeh:
I uses debian, but i compiled postfix and i just want to know name of
them.
http://www.postfix.org/BASIC_CONFIGURATION_README.html
http://www.postfix.org/STANDARD_CONFIGURATION_README.html
Wietse
Hello Wietse, postfix-users,
On 18.03.2013 12:01, Wietse Venema wrote:
Are there any plans to implement XCLIENT forwarding into postfix.
Please read the XFORWARD document.
I read the XFORWARD_README and I believe XFORWARD is what I want and
should use to get variables from postfix MTA to my
Christian Rohmann:
Hello Wietse, postfix-users,
On 18.03.2013 12:01, Wietse Venema wrote:
Are there any plans to implement XCLIENT forwarding into postfix.
Please read the XFORWARD document.
I read the XFORWARD_README and I believe XFORWARD is what I want and
should use to get
On 2013-03-18 12:07, Wietse Venema wrote:
Per olof Ljungmark:
I'd recommend separating authenticated from unauthenticated submission.
Enable submission (port 587) with authentication required, and remove
permit_sasl_authenticated from the smtpd instance on port 25. For the
submission port you
On 2013-03-18 17:55, Per olof Ljungmark wrote:
On 2013-03-18 12:07, Wietse Venema wrote:
Per olof Ljungmark:
I'd recommend separating authenticated from unauthenticated submission.
Enable submission (port 587) with authentication required, and remove
permit_sasl_authenticated from the smtpd
Hello everyone,
I have set up always_bcc = jour...@mydomain.org for an email archiving
account.
How can bypass always_bcc for certain senders? for example I do not want to
always_bcc any email that comes from
aud...@mydomain.com and or aud...@mydomain.com
Thanks in advance for any
Jumping Mouse:
Hello everyone,
I have set up always_bcc = jour...@mydomain.org for an email
archiving account. How can bypass always_bcc for certain senders?
It's called *always*_bcc for a reason...
for example I do not want to always_bcc any email that comes from
aud...@mydomain.com
On 3/14/2013 2:51 AM, Ansgar Wiechers wrote:
On 2013-03-13 Littlefield, Tyler wrote:
first, I have my postfix setup to receive mail and drop it in the
user's ~/mail directory.
I'm trying to figure out if there's a way I can have both virtual
users and non virtual users.
You can alias
Viktor Duknovni wrote
If you're using Debian, they modify Postfix with additional
configuration parameteter, in particular if I recall correctly
myhostname can be set to a filename rather than a hostname.
myhostname = /etc/hostname
and optional database drivers are installed as separate
--On Sunday, March 17, 2013 8:15 PM -0400 Wietse Venema
wie...@porcupine.org wrote:
Snaphot 20130317 addresses sub-optimal behavior in the LMDB client
code that affected tlsmgr and postmap -i, and it makes the code
more resilient.
In particular, the Postfix LMDB client will no longer keep
On Mon, Mar 18, 2013 at 01:23:10PM -0600, Robert Lopez wrote:
I suppose I should have known this years ago. I did not know Debian
modified the Postfix code and even added database drivers. Does Canonical
then further modify it? I have never been successful in compiling and
configuring a
On Mon, Mar 18, 2013 at 02:42:23PM -0400, Jumping Mouse wrote:
I have set up always_bcc = jour...@mydomain.org for an email
archiving account.
How can bypass always_bcc for certain senders?
For example I do not want to always_bcc any email that comes from
aud...@mydomain.com and or
Hi All.
The scenario:
From: a...@site1.com
To: b...@site2.com
CC: m...@site3.com
After receiving the email CC at site 3, site 3 is sending out emails to
everyone on the original,
basically a duplicate email arrives to the sender and everyone in the headers.
a sends mail to b with
--On Monday, March 18, 2013 4:26 PM -0400 Wietse Venema
wie...@porcupine.org wrote:
Quanah Gibson-Mount:
--On Sunday, March 17, 2013 8:15 PM -0400 Wietse Venema
wie...@porcupine.org wrote:
Snaphot 20130317 addresses sub-optimal behavior in the LMDB client
code that affected tlsmgr and
Hi Ed,
It seems that site3.com smtp server use header recipients instead of
SMTP RCPT TO recipients and also send to the sender ...
Can you post email headers to check the Received From fields ?
Le 18/03/2013 21:51, Ed a écrit :
Hi All.
The scenario:
From: a...@site1.com
To:
On 03/18/2013 09:51 PM, Ed wrote:
Hi All.
The scenario:
From: a...@site1.com
To: b...@site2.com
CC: m...@site3.com
After receiving the email CC at site 3, site 3 is sending out emails
to everyone on the original,
Configure site3 to stop doing that.
--
J.
Dear Postfix-users!
Over the last weekend i've setup a mail-environment for my personal
use with a remote Postfix and Dovecot SASL/IMAP and locally mutt with
Postfix as MTA.
To be able to authenticate SMTP to the remote Postfix, i'm currently
using smtp_sasl_password_maps, as described in
Hi,
imho, the best approach to getting a road-warrior (laptop) authenticated
as a sattelite sytem using your central MTA as a relayhost is have it in
mynetworks. As in, connect it to the MTA through a VPN tunnel.
Then, there is nothing that that limits you to use PAM for
authenticaiton. You can
Finally, after an interesting discussion over this issue on opendkim-users,
I've been able to google my way out, with a solution from Wietse:
http://postfix.1071664.n5.nabble.com/Any-best-practices-for-stacking-filters-td51592.html
thanks,
On 17 mars 2013, at 14:51, patrick.proniew...@free.fr
23 matches
Mail list logo
