Hello,
one of our clients wants to offer mass mailing services for his clients.
The problem is, that our client wants to send emails with the sender domains of
his clients from his own postfix server.
As far as I know, some anti spam measure rely on the check, whether the sending
e-mailserver
* Stefan Michael Guenther :
> Hello,
>
> one of our clients wants to offer mass mailing services for his clients.
>
> The problem is, that our client wants to send emails with the sender domains
> of his clients from his own postfix server.
1. Make sure the sending server has matching forward/re
Hi,
I have an email receiving setup with one Postfix instance mapped to one
instance of Amavisd-new (spamassassin, ClamAV),
Now to prepare for increasing traffic, I am looking on to scale out strategies
of my setup.
So with that in mind, is it possible that one instance of Postfix can itself
Patrick Ben Koetter:
> * Stefan Michael Guenther :
> > Hello,
> >
> > one of our clients wants to offer mass mailing services for his clients.
> >
> > The problem is, that our client wants to send emails with the sender domains
> > of his clients from his own postfix server.
>
> 1. Make sure the
On 07 Feb 2014, at 01:12 , Stefan Michael Guenther wrote:
> The problem is, that our client wants to send emails with the sender domains
> of his clients from his own postfix server.
There si no legitimate reason to do this. In fact, my servers (and I suspect
many servers) block all email fro
On Fri, Feb 07, 2014 at 11:24:22AM +, Sharma, Ashish wrote:
> In essence can postfix work as an SMTP load balancer ?
Yes. Either pre-queue with smtpd_proxy_filter or post-queue with
content_filter. In either case the filter host can be a multi-homed
SMTP service. With content_filter the ta
Am 07.02.2014 16:26, schrieb LuKreme:
> On 07 Feb 2014, at 01:12 , Stefan Michael Guenther
> wrote:
>
>> The problem is, that our client wants to send emails with the sender domains
>> of his clients from his own postfix server.
>
> There is no legitimate reason to do this. In fact, my serve
>I have an email receiving setup with one Postfix instance mapped to one
>instance of Amavisd-new (spamassassin, ClamAV),
>
>Now to prepare for increasing traffic, I am looking on to scale out strategies
>of my setup.
>
>So with that in mind, is it possible that one instance of Postfix can itse
(I'm sorry if this is a duplicate post. If the earlier one
got through I haven't seen it.)
Here's what I want to do:
When (incoming) mail is addressed to
user@hostname.domain
I want to change that to:
user@domain
before I deliver it.
in main.cf:
recipient_canonical_maps=regexp
This will do what you're looking for, much easier.
in main.cf:
mydomain = arlut.utexas.edu
# SENDING MAIL
#
# The myorigin parameter specifies the domain that locally-posted
# mail appears to come from. The default is to append $myhostname,
# which is fine for small sites. If you run a domain
On Thu, Feb 06, 2014 at 05:37:16PM +, Alan Munday wrote:
> My certificate creation process also followed the old way of doing
> things. I've updated this to also follow the HowTo. In doing so I
> needed to edit two values in the openssl.cnf namely:
>
> [ CA_default ]
> unique_subject = no
>
On 07 Feb 2014, at 09:16 , li...@rhsoft.net wrote:
> Am 07.02.2014 16:26, schrieb LuKreme:
>> On 07 Feb 2014, at 01:12 , Stefan Michael Guenther
>> wrote:
>>
>>> The problem is, that our client wants to send emails with the sender
>>> domains of his clients from his own postfix server.
>>
>> T
Am 07.02.2014 22:51, schrieb LuKreme:
> On 07 Feb 2014, at 09:16 , li...@rhsoft.net wrote:
>> Am 07.02.2014 16:26, schrieb LuKreme:
>>> On 07 Feb 2014, at 01:12 , Stefan Michael Guenther
>>> wrote:
>>>
The problem is, that our client wants to send emails with the sender
domains of his
Viktor Dukhovni wrote the following on 07/02/14 19:07:
On Thu, Feb 06, 2014 at 05:37:16PM +, Alan Munday wrote:
>> I did try CA:FALSE but this was causing outlook.com mail to fail
>> (and, as Viktor stated, mail from other domains as well).
>
> Usually, the CA certificate is created using a
On Fri, Feb 07, 2014 at 10:40:37PM +, Alan Munday wrote:
> > Usually, the CA certificate is created using a different extension
> > section (not "usr_cert"). You then have "CA:FALSE" in "usr_cert",
> > and "CA:TRUE" in the CA extension section.
>
> I'll try this.
Should not be too hard. In
Viktor Dukhovni wrote the following on 07/02/14 23:13:
On Fri, Feb 07, 2014 at 10:40:37PM +, Alan Munday wrote:
Should not be too hard. In your case, as I suggested upstream, a
simple self-signed certificate with no issuing CA is quite sufficient:
Assuming a suitable private key in key.pem
In $PREVIOUSJOB, we had a number of internet facing SMTP machines, which
looked up accounts/mailboxes/transport maps etc from MySQL; all changes
were done on a master database on a separate machine, and synced out
with MySQL replication to all of the SMTP machines. This way we could
take any single
On Fri, Feb 07, 2014 at 11:49:55PM +, Alan Munday wrote:
> >Assuming a suitable private key in key.pem, a self-signed cert is just
> >one command:
> >
> > openssl req -x509 -sha1 -new -key key.pem -out newcert.pem \
> > -subj "/CN=$(uname -n)" -days 3650
> >
>
> Not difficult at a
On Thu, 2014-02-06 at 17:24:06 -0600, Jay G. Scott wrote:
> recipient_canonical_maps=regexp:/etc/postfix/pfrecipient_canonical
>
> [root@davis postfix]# more pfrecipient_canonical
> /^gl@.*\.arlut\.utexas\.edu$/ g...@arlut.utexas.edu
> /^a@.*\.arlut\.utexas\.edu$/a...@arlut.utexas.edu
> /^b@
19 matches
Mail list logo
