>That has nothing to do with how postfix percieves the domain.
Understood. As i stated in another reply, the box perceives them all as
relay_domains.
On 11/18/2012 08:26 PM, Jan Johansson wrote:
NOTE that domainALPHA.com must be in an address class you control:
relay, local, or virtual_*.
The presence of the alias alone does not mean mail for the domain is accepted.
That I gathered. The box is a MX for the domains in question.
That has n
Viktor Dukhovni:
> text mentioning 0.9.9 is from Postfix documentation, we should
> update it, there was never an OpenSSL 0.9.9 release, only development
> snapshots.
Fixed in the next release.
Wietse
Am 18.11.2012 20:19, schrieb Wietse Venema:
> Jim Reid:
>> On 18 Nov 2012, at 17:40, Michael Monnerie
>> wrote:
>>
>>> Nothing should have problems with leading zeroes.
>>
>> Sometimes reality intrudes on ideals. There is legacy software out
>> there which will not behave the way you expect. So
>I think you read too much into the question. The OP appeared to asking about
>basic virtual_alias_maps use; nothing was said about how/whether to accept the
>mail. Maybe it's already being accepted under >permit_mynetworks, or via
>sendmail(1)?
Basically the box is set up to relay to other box
On Sun, Nov 18, 2012 at 08:38:39AM -0500, thorso...@lavabit.com wrote:
> "smtpd_tls_eecdh_grade (default: see "postconf -d" output)
>
>
>
> This feature is available in Postfix 2.6 and later, when it is
> compiled and linked with OpenSSL 1.0.0 or later." [0]
>
> I'm using Postfix 2.7.1
>NOTE that domainALPHA.com must be in an address class you control:
>relay, local, or virtual_*.
>
>The presence of the alias alone does not mean mail for the domain is accepted.
That I gathered. The box is a MX for the domains in question.
>That's what $virtual_alias_maps [1] is for.
>
>Add the following line to main.cf:
>
>virtual_alias_maps = hash:/etc/postfix/virtual
>
>Create a file /etc/postfix/virtual with the mappings you need:
That seem simple enough... Looks like I was over complicating the issue. Thanks!
Jim Reid:
> On 18 Nov 2012, at 17:40, Michael Monnerie
> wrote:
>
> > Nothing should have problems with leading zeroes.
>
> Sometimes reality intrudes on ideals. There is legacy software out
> there which will not behave the way you expect. Sometimes a digit
You mean, like UNIX libc libraries?
On Sun, Nov 18, 2012 at 05:13:05AM -0500, thorso...@lavabit.com wrote:
> > This will write a new 1280-bit RSA key and the corresponding
> > self-signed certificate with server name "mail.example.com" valid
> > for ~10 years to the file /etc/postfix/smtpd.pem, which you can
> > use as the server ce
On 18 Nov 2012, at 17:40, Michael Monnerie
wrote:
> Nothing should have problems with leading zeroes.
Sometimes reality intrudes on ideals. There is legacy software out there which
will not behave the way you expect. Sometimes a digit string which begins with
a leading zero will be treated as
Am Sonntag, 18. November 2012, 14:12:47 schrieb Reindl Harald:
> the list is invalid because ip-segments
> does not have leading zeros
?
cat list|sed 's/00/0/g' if you need to. But whois can cope with that:
% The key "125.088.125.201" has been changed to "125.88.125.201" for
lookup.
Nothing shou
"smtpd_tls_eecdh_grade (default: see "postconf -d" output)
This feature is available in Postfix 2.6 and later, when it is
compiled and linked with OpenSSL 1.0.0 or later." [0]
I'm using Postfix 2.7.1. "aptitude show postfix" shows libssl0.9.8 in
dependencies.
"postconf -d" lists this o
Am 18.11.2012 14:08, schrieb Michael Monnerie:
> We've got one users e-mail password hacked, and at the sime time a lot
> of different IPs started to use that address.
welcome to the club, thanks to rate-controls reduce
the damage to < 700 messages at all
> Here is the list
the list is invali
We've got one users e-mail password hacked, and at the sime time a lot
of different IPs started to use that address. Here is the list. How
should we report those IPs, is there a "anti botnet unit" somewhere?
What is the best way to fight it?
008.021.006.226
014.139.187.017
014.149.118.062
014.1
> This will write a new 1280-bit RSA key and the corresponding
> self-signed certificate with server name "mail.example.com" valid
> for ~10 years to the file /etc/postfix/smtpd.pem, which you can
> use as the server certificate (and implicitly key) file:
Should I specify it like this?
smtpd_tls_
16 matches
Mail list logo
