We setup dovecot on our outbound relay to talk to a database containing the
user information and provide the auth socket to postfix. Unless the address of
the recipient has the same domain as the local postfix instance all messages
will be relayed on (we set the local domain to something bogus
Just curious if anyone knows of any tools that can search for messages
already delivered (to maildir) that are spam. We have many years of
email on our system, some of those years before having a reliable spam
filtering solution, so we would like to try to identify spam messages
and purge them
I prepared a script to work with check_policy_service using inet,
however I find that when the service is unavailable Postfix dies and no
longer accepts messages. Is there a method that would allow Postfix to
ignore the inet connection if it were unavailable and continue checking
other rules?
On 11/30/12 11:17 AM, Noel Jones wrote:
On 11/30/2012 10:45 AM, l...@airstreamcomm.net wrote:
On 11/30/12 10:22 AM, Wietse Venema wrote:
l...@airstreamcomm.net:
I am setup a 2.6.6 server with virtual domains and the entries in an
alias_maps file (/etc/postfix/aliases) which look like this
On 11/30/12 10:22 AM, Wietse Venema wrote:
l...@airstreamcomm.net:
I am setup a 2.6.6 server with virtual domains and the entries in an
alias_maps file (/etc/postfix/aliases) which look like this:
localuser :include:/etc/postfix/massmail/localuser
localuser2 :include:/etc/postfix
I am setup a 2.6.6 server with virtual domains and the entries in an
alias_maps file (/etc/postfix/aliases) which look like this:
localuser :include:/etc/postfix/massmail/localuser
localuser2 :include:/etc/postfix/massmail/localuser2
When trying to deliver to the users (echo "test" | ma
On 10/16/12 8:15 AM, Wietse Venema wrote:
Kaleb Hosie:
We host a mail server which runs Postfix and there has been a few
times where one of our clients computers becomes infected with
malware and the password is compromised.
How this has come to my attention is because every once in a while,
I
On 9/17/12 4:15 PM, /dev/rob0 wrote:
On Mon, Sep 17, 2012 at 03:51:03PM -0500, l...@airstreamcomm.net wrote:
We would like to block a couple ranges of ips before a sasl login is
able to happen. Smtpd_recipient_restrictions looks like this:
smtpd_recipient_restrictions
We would like to block a couple ranges of ips before a sasl login is
able to happen. Smtpd_recipient_restrictions looks like this:
smtpd_recipient_restrictions =
permit_mynetworks,
check_client_access cidr:/etc/postfix/restricted
permit_sasl_authenticated,
check_
I would like to build a script that checks whether a SASL user is able
to relay mail and I am not sure how to get started doing this with
postfix. Is there any functionality built into postfix that can do
this? I have already looked at policyd and would like to avoid having a
new service / da
On 8/17/12 3:17 PM, Patrick Ben Koetter wrote:
* l...@airstreamcomm.net :
I am trying to get SASL (with dovecot) setup on postfix 2.6.6 and
receiving this warning:
warning: domain.tld[ip.add.re.ss]: SASL LOGIN authentication failed:
Invalid authentication mechanism
The client attempts to use
I am trying to get SASL (with dovecot) setup on postfix 2.6.6 and
receiving this warning:
warning: domain.tld[ip.add.re.ss]: SASL LOGIN authentication failed:
Invalid authentication mechanism
There are a number of successful SASL attempts, but a large number of
these warnings are occurring
Looking for suggestions on classes or consulting with an educational aspect for
advanced postfix administration in and around the upper Midwest US (we are open
to any classes in Hawaii :). By the way, big thanks to the people that use
this list for providing a better support structure than any
13 matches
Mail list logo
