Alexander Gr?ner:
> Hi,
>
> is there a possibilty for an exception for the parameter
> smtpd_hard_error_limit like there is one for
> smtpd_client_event_limit_exceptions ?
>
> We have a quite funny Lotus server running here which seems to have
> problems when running into this limit.
>
> I di
On Tue, Nov 4, 2008 at 17:06, Nikita Kipriyanov <[EMAIL PROTECTED]> wrote:
> http://www.postfix.org/RESTRICTION_CLASS_README.html#internal
>
> You have to add forward3 into protected_destinations file, and user9 into
> insiders file.
My main.cf :
smtpd_sender_restrictions =
permit_mynetworks,
M. Rodrigo Monteiro wrote:
> On Tue, Nov 4, 2008 at 17:06, Nikita Kipriyanov <[EMAIL PROTECTED]> wrote:
>
>> http://www.postfix.org/RESTRICTION_CLASS_README.html#internal
>>
>> You have to add forward3 into protected_destinations file, and user9 into
>> insiders file.
>>
>
> My main.cf :
>
Martin Strand wrote:
Our customers are extremely non-technical (some believe the Internet
is "that blue 'e' on the computer") so I have little hope in
explaining why postmaster is a reserved mailbox. :) This particular
customer registered his domain somewhere else and now decided to
switch to
Hello.
For a local aliasing, it is possible to specify the command as a
destination for mail, using 'pipe' character. We're using this
possibility to bind spam-learning facility, like this:
(main.cf)
alias_maps = /etc/aliases
(/etc/aliases)
spam: "|/usr/local/bin/spamlearn_from_mail.tcl SPAM
Alexander Grüner wrote:
Hi,
is there a possibilty for an exception for the parameter
smtpd_hard_error_limit like there is one for
smtpd_client_event_limit_exceptions ?
We have a quite funny Lotus server running here which seems to have
problems when running into this limit.
I did not foun
Nikita Kipriyanov wrote:
Hello.
For a local aliasing, it is possible to specify the command as a
destination for mail, using 'pipe' character. We're using this
possibility to bind spam-learning facility, like this:
(main.cf)
alias_maps = /etc/aliases
(/etc/aliases)
spam: "|/usr/local/bin/sp
Hi,
is there a possibilty for an exception for the parameter
smtpd_hard_error_limit like there is one for
smtpd_client_event_limit_exceptions ?
We have a quite funny Lotus server running here which seems to have
problems when running into this limit.
I did not found one, yet on http://www.
Nikita Kipriyanov:
> Hello.
>
> For a local aliasing, it is possible to specify the command as a
> destination for mail, using 'pipe' character. We're using this
> possibility to bind spam-learning facility, like this:
>
> (main.cf)
> alias_maps = /etc/aliases
>
> (/etc/aliases)
> spam: "|/usr
Setting up a backup server on a two mail server network:
Reading the postfix book, it looks like relay_domains will try to relay
all mail for those domains.
Relay_recipients must specify all the mails on the primary or I can use
a wildcard of @thedomain.com
However, what if I want to
On Mon, Nov 10, 2008 at 02:17:20PM -0500, Bailo, John wrote:
> Setting up a backup server on a two mail server network:
>
> Reading the postfix book, it looks like relay_domains will try to relay
> all mail for those domains.
Will by default accept mail for the domains from untrusted (to relay t
Hi,
Most of our group mailing lists (which are defined via an LDAP entry
directly accessed by Postfix) are restricted so that you must have or be
spoofing a local email address -- checked via check_sender_access and
rejecting anything not from our own domain. Each list entry in LDAP for
whic
Rob Tanner wrote:
Hi,
Most of our group mailing lists (which are defined via an LDAP entry
directly accessed by Postfix) are restricted so that you must have or be
spoofing a local email address -- checked via check_sender_access and
rejecting anything not from our own domain. Each list entr
On Mon, Nov 10, 2008 at 12:09:38PM -0800, Rob Tanner wrote:
> Hi,
>
> Most of our group mailing lists (which are defined via an LDAP entry
> directly accessed by Postfix) are restricted so that you must have or be
> spoofing a local email address -- checked via check_sender_access and
> reject
It appears that my postfix server is using invalid TLS certs from
/etc/postfix/main.cf. When I set up my client to use TLS, I get an
invalid certificate error from Outlook that tells me the hostname and
domain of the server which are wrong. I renamed the FQDN at some point
however I must have re-us
Hi, Please excuse me if it is not relevant on this forum.
I am planning to use domain keys and dkim for our domain just to send mails
outside.
Is DKIMproxy good enough to cover both older Yahoo Domainkeys and new DKIM?
thanks you.
~LA
On Sat, Nov 8, 2008 at 12:06 AM, Sahil Tandon <[EMAIL PROTECTED]> wrote:
> Terry Carmen <[EMAIL PROTECTED]> wrote:
>
> > Sahil Tandon wrote:
> >> Linux Addict <[EMAIL PROTECTED]> wrote:
> >>
> >>
> >>> Steven King wrote:
> >>>
> Postfix is very cautious about system resource usage. It keeps a
On 11/10/08 12:32 PM, Noel Jones wrote:
Rob Tanner wrote:
Hi,
Most of our group mailing lists (which are defined via an LDAP entry
directly accessed by Postfix) are restricted so that you must have or
be spoofing a local email address -- checked via check_sender_access
and rejecting anything
Linux Addict wrote:
Hi, Please excuse me if it is not relevant on this forum.
I am planning to use domain keys and dkim for our domain just to send
mails outside.
Is DKIMproxy good enough to cover both older Yahoo Domainkeys and new DKIM?
thanks you.
~LA
dkimproxy supports both DKIM and D
Rob Tanner wrote:
On 11/10/08 12:32 PM, Noel Jones wrote:
Rob Tanner wrote:
Hi,
Most of our group mailing lists (which are defined via an LDAP entry
directly accessed by Postfix) are restricted so that you must have or
be spoofing a local email address -- checked via check_sender_access
and
Carlos Williams wrote:
It appears that my postfix server is using invalid TLS certs from
/etc/postfix/main.cf. When I set up my client to use TLS, I get an
invalid certificate error from Outlook that tells me the hostname and
domain of the server which are wrong. I renamed the FQDN at some point
Now I got it! I had the feeling I was somehow thinking of this in
reverse. Today I had the time to sit down and figure this out, and I
was right – I had been thinking that the name itself (e.g. "smtpd2")
would need to be defined first so that parameters could be assigned to
them in main.cf (how els
On Mon, Nov 10, 2008 at 5:26 PM, Noel Jones <[EMAIL PROTECTED]> wrote:
> Yes, the FQDN of the server is encoded in the certificate. If you rename
> the server, you must get a new certificate (or generate a new one if
> self-signed).
>
> If your existing verisign certificate is a "server" type cert
I'm starting to get a lot of SPAM where the Sender matches the To:.
I hear the same from several others. There was the thread recently on
something similar but dealing with lists so it seems to not apply.
I'm at a complete loss after being six pages into a search using
Google.com with "postfi
Roderick A. Anderson wrote:
I'm starting to get a lot of SPAM where the Sender matches the To:.
I hear the same from several others. There was the thread recently on
something similar but dealing with lists so it seems to not apply.
I'm at a complete loss after being six pages into a search
Roderick A. Anderson:
> I'm starting to get a lot of SPAM where the Sender matches the To:.
You mean, the From: and To: headers, or the MAIL FROM and the RCPT
TO address in SMTP commands?
Note that From: and To: headers can be completely different from
the MAIL FROM and the RCPT TO address in SM
On Mon, Nov 10, 2008 at 06:36:53PM -0500, Carlos Williams wrote:
> On Mon, Nov 10, 2008 at 5:26 PM, Noel Jones <[EMAIL PROTECTED]> wrote:
> > Yes, the FQDN of the server is encoded in the certificate. If you rename
> > the server, you must get a new certificate (or generate a new one if
> > self-
Wietse Venema wrote:
Roderick A. Anderson:
I'm starting to get a lot of SPAM where the Sender matches the To:.
You mean, the From: and To: headers, or the MAIL FROM and the RCPT
TO address in SMTP commands?
One of these days I'll stating thinking in the correct terms. Probably
about a week
28 matches
Mail list logo
