Hello,
I googled everywhere, read how-tos but can not find solution for simple
problem in postfix:
I would like to have such config:
- smtp25/tcp; only server-server communication, only
mail receive for local domain, no relay, no send, encryption optional,
SPF, blocking 'serve
I am using postfix+mysql virtual domains/users+dovecot+sieve. I am
using virtual domains, users, and aliases in mysql. How can I create a
pipe to a program like "test: |/usr/local/bin/test". If I insert an a
record in aliases tables, postfix tries to deliver the mail to
"|/usr/local/bin/t...@mydoma
On Monday, July 27, 2009 at 10:56 CEST,
Zbyszek wrote:
> I googled everywhere, read how-tos but can not find solution for
> simple problem in postfix:
> I would like to have such config:
> - smtp25/tcp; only server-server communication, only
> mail receive for local domain, n
On Monday, July 27, 2009 at 11:00 CEST,
Alejandro Vargas wrote:
> I am using postfix+mysql virtual domains/users+dovecot+sieve. I am
> using virtual domains, users, and aliases in mysql. How can I create
> a pipe to a program like "test: |/usr/local/bin/test". If I insert
> an a record in al
Hi,
I'm using a couple of anti-spam techniques which successfully reject
(5xx) or ban (ipfilter firewall rule) most spam before even getting in
the queue. A couple of days ago about 2600 spam messages where delivered
to an user with a catch-all account. These messages where classified as
SPAM or S
On Mon, 2009-07-27 at 11:40 +0200, Martijn de Munnik wrote:
> Hi,
>
> I'm using a couple of anti-spam techniques which successfully reject
> (5xx) or ban (ipfilter firewall rule) most spam before even getting in
> the queue. A couple of days ago about 2600 spam messages where delivered
> to an us
On Monday 27 July 2009 10:40:34 Martijn de Munnik wrote:
>
> I'm using a couple of anti-spam techniques which successfully reject
> (5xx) or ban (ipfilter firewall rule) most spam before even getting in
> the queue.
You use a LOT of blacklists, which probably results in more false positives
than
2009/7/27 Magnus Bäck :
>> I am using postfix+mysql virtual domains/users+dovecot+sieve. I am
>> using virtual domains, users, and aliases in mysql. How can I create
>> a pipe to a program like "test: |/usr/local/bin/test". If I insert
>> an a record in aliases tables, postfix tries to deliver the
On 7/27/2009, Martijn de Munnik (mart...@youngguns.nl) wrote:
> Are there ways to block these spam attacks?
Don't use catchalls for live/normal domains...
--
Best regards,
Charles
On Mon, 2009-07-27 at 10:55 +0100, Simon Waters wrote:
> On Monday 27 July 2009 10:40:34 Martijn de Munnik wrote:
> >
> > I'm using a couple of anti-spam techniques which successfully reject
> > (5xx) or ban (ipfilter firewall rule) most spam before even getting in
> > the queue.
>
> You use a L
John/SML:
> < Jul 24 14:16:22 imapsv02 postfix/master[17734]: warning: process
> /usr/lib/postfix/cleanup pid 17969 exit status 2
...
> I googled the problem, but find no clue. Any idea?
This is the official reference:
http://www.postfix.org/DEBUG_README.html#logging
And please turn off that ve
On Monday 27 July 2009 11:13:34 Martijn de Munnik wrote:
> Losing catchall seems to be the best solution but some of my customers
> want to create an emailaddress for every website the register on.
>
> m...@desjors.nl
> pay...@desjors.nl
> deb...@desjors.nl
They could use the "recipient_delimiter"
On Monday, July 27, 2009 at 11:55 CEST,
Alejandro Vargas wrote:
> Thank you very much. For the record, the solution was this:
> 1) in /etc/postfix/main.cf:
>
> ensure alias_maps = hash:/etc/postfix/aliases
> ensure mydestination = localhost
> transport_maps = hash:/etc/postfix/transport
>
I'm pulling my hair out with this one. I need to make the server PCI
compliant and we are still failing the test because we accept SSLv2
connections. I'm running Postfix 2.5.1 on a Fedora machine, and here is
my postconf:
$ postconf -n
alias_database = hash:/etc/aliases
alias_maps = hash:/etc/
Jake Vickers:
> Now I know I posted the other day about disabling SSLv2, but if I add
That solution was for MANDATORY TLS encryption. If TLS is not mandatory,
then disabling SSLv2 is pointless: you allow plaintext email.
But if it gives someone warm fuzzies, you can use smtpd_tls_protocols
inste
On Jul 27, 2009, at 5:08, Magnus Bäck wrote:
On Monday, July 27, 2009 at 10:56 CEST,
Zbyszek wrote:
I googled everywhere, read how-tos but can not find solution for
simple problem in postfix:
I would like to have such config:
- smtp25/tcp; only server-server communication,
2009/7/27 Magnus Bäck :
> On Monday, July 27, 2009 at 11:55 CEST,
> Alejandro Vargas wrote:
>
>> Thank you very much. For the record, the solution was this:
>> 1) in /etc/postfix/main.cf:
>>
>> ensure alias_maps = hash:/etc/postfix/aliases
>> ensure mydestination = localhost
>> transport_maps
Well Magnus, I did what you told me, and
postfix stoped receiving mails, when an external smtp
tries to send mail to my local users, postfix respond
access denied.
I didn't do it exaclty like in you example, but I was
doing int the smtpd_recipent_restrictions,
this is what I did:
smtpd_sender_res
Mangus,
taking a deep look into your example, I notice
the restriction is only applied to example.com, isn't it ?
if this is the case, I have a problem on doing it, my list
of domains is virtual, so I need to restrict the test to
them, is it possible ?
On Monday 27 July 2009 11:27:51 am
On Monday, July 27, 2009 at 16:27 CEST,
Pablo Yaggi wrote:
> Well Magnus, I did what you told me, and postfix stoped receiving
> mails, when an external smtp tries to send mail to my local users,
> postfix respond access denied.
> I didn't do it exaclty like in you example,
Like most progra
On Monday, July 27, 2009 at 16:37 CEST,
Pablo Yaggi wrote:
> taking a deep look into your example, I notice
> the restriction is only applied to example.com, isn't it ?
Yes.
> if this is the case, I have a problem on doing it, my list of domains
> is virtual, so I need to restrict th
Martijn de Munnik wrote:
>
> Losing catchall seems to be the best solution but some of my customers
> want to create an emailaddress for every website the register on.
>
> m...@desjors.nl
> pay...@desjors.nl
> deb...@desjors.nl
>
> etc.
>
> Then they use their mail client to filter the messages a
On Monday 27 July 2009 12:46:04 pm Magnus Bäck wrote:
> On Monday, July 27, 2009 at 16:37 CEST,
> Pablo Yaggi wrote:
>
> > taking a deep look into your example, I notice
> > the restriction is only applied to example.com, isn't it ?
>
> Yes.
>
> > if this is the case, I have a proble
On Monday, July 27, 2009 at 18:05 CEST,
Pablo Yaggi wrote:
> On Monday 27 July 2009 12:46:04 pm Magnus Bäck wrote:
> > On Monday, July 27, 2009 at 16:37 CEST,
> > Pablo Yaggi wrote:
> >
> > > taking a deep look into your example, I notice
> > > the restriction is only applied to
I can see why he would want to do that - 99% of the spam I get is from
US-based cable modem- and DSL-hosted systems. My host - earthlink -
recently reconfigured their routers to disallow outbound email that
doesn't go through their servers, and I wish all ISPs would do that.
Perhaps . .
On Monday 27 July 2009 05:38:17 Wietse Venema wrote:
> John/SML:
> > < Jul 24 14:16:22 imapsv02 postfix/master[17734]: warning: process
> > /usr/lib/postfix/cleanup pid 17969 exit status 2
>
> ...
>
> > I googled the problem, but find no clue. Any idea?
>
> This is the official reference:
>
> http:
On Monday 27 July 2009 05:47:29 Simon Waters wrote:
> On Monday 27 July 2009 11:13:34 Martijn de Munnik wrote:
> > Losing catchall seems to be the best solution but some of my customers
> > want to create an emailaddress for every website the register on.
> >
> > m...@desjors.nl
> > pay...@desjors.
On Monday 27 July 2009 01:21:43 pm Magnus Bäck wrote:
> On Monday, July 27, 2009 at 18:05 CEST,
> Pablo Yaggi wrote:
>
> > On Monday 27 July 2009 12:46:04 pm Magnus Bäck wrote:
> > > On Monday, July 27, 2009 at 16:37 CEST,
> > > Pablo Yaggi wrote:
> > >
> > > > taking a deep loo
On Jul 27, 2009, at 7:18 PM, /dev/rob0 wrote:
On Monday 27 July 2009 05:47:29 Simon Waters wrote:
On Monday 27 July 2009 11:13:34 Martijn de Munnik wrote:
Losing catchall seems to be the best solution but some of my
customers
want to create an emailaddress for every website the register on.
On Mon, Jul 27, 2009 at 08:03:20AM -0400, Wietse Venema wrote:
> Jake Vickers:
> > Now I know I posted the other day about disabling SSLv2, but if I add
> That solution was for MANDATORY TLS encryption. If TLS is not mandatory,
> then disabling SSLv2 is pointless: you allow plaintext email.
I don
On Mon, 27 Jul 2009, Simon Waters wrote:
On Monday 27 July 2009 11:13:34 Martijn de Munnik wrote:
Losing catchall seems to be the best solution but some of my customers
want to create an emailaddress for every website the register on.
m...@desjors.nl
pay...@desjors.nl
deb...@desjors.nl
They
If I have a box with a valid reverse DNS entry of mail.example.com that
has virtual domains of
domain.com
otherdomain.com
somedomain.com
will my "wrong" reverse DNS for the virtual domains affect delivery? Do
I need to do anything?
thx,
Cameron
On Monday 27 July 2009 13:52:07 Charles Sprickman wrote:
> On Mon, 27 Jul 2009, Simon Waters wrote:
> > On Monday 27 July 2009 11:13:34 Martijn de Munnik wrote:
> >> Losing catchall seems to be the best solution but some of my customers
> >> want to create an emailaddress for every website the regi
On Monday 27 July 2009 14:14:54 Cameron Camp wrote:
> If I have a box with a valid reverse DNS entry of mail.example.com that
> has virtual domains of
>
> domain.com
> otherdomain.com
> somedomain.com
>
> will my "wrong" reverse DNS for the virtual domains affect delivery?
We cannot guess what mil
On Mon, July 27, 2009 21:14, Cameron Camp wrote:
> If I have a box with a valid reverse DNS entry of mail.example.com that
> has virtual domains of
>
> domain.com
> otherdomain.com
> somedomain.com
>
> will my "wrong" reverse DNS for the virtual domains affect delivery? Do
> I need to do anything?
Cameron Camp schrieb:
> If I have a box with a valid reverse DNS entry of mail.example.com that
> has virtual domains of
>
> domain.com
> otherdomain.com
> somedomain.com
>
> will my "wrong" reverse DNS for the virtual domains affect delivery? Do
> I need to do anything?
>
> thx,
> Cameron
>
If I have a box with a valid reverse DNS entry of mail.example.com that
has virtual domains of
domain.com
otherdomain.com
somedomain.com
will my "wrong" reverse DNS for the virtual domains affect delivery? Do
I need to do anything?
You can simply do the following:
domain.com. MX 10 mail.examp
I don't think that's a terribly good idea, but anyway:
main.cf:
smtpd_client_restrictions = check_client_access pcre:/path/to/file
/path/to/file:
/(ppp|dialup|adsl)/ REJECT
You can move the check_client_access restriction to any other
smtpd_xxx_restrictions if you want. You probably
John/SML a écrit :
>
> [snip]
>
> however, there is an error about cleanup server in the verbose log when
> using LDAP :-
mouss said:
>> next time, do not show VERBOSE logs unless asked. ...
>
> [verbose log ignored]
>
> I googled the problem, but find no clue. Any idea?
>
Please be coll
/dev/rob0 a écrit :
> On Monday 27 July 2009 14:14:54 Cameron Camp wrote:
>> If I have a box with a valid reverse DNS entry of mail.example.com that
>> has virtual domains of
>>
>> domain.com
>> otherdomain.com
>> somedomain.com
>>
>> will my "wrong" reverse DNS for the virtual domains affect deliv
Cameron Camp a écrit :
> If I have a box with a valid reverse DNS entry of mail.example.com that
> has virtual domains of
>
> domain.com
> otherdomain.com
> somedomain.com
>
> will my "wrong" reverse DNS for the virtual domains affect delivery? Do
> I need to do anything?
>
many people confuse
/dev/rob0 a écrit :
> Unfortunately, I have found that many Web programmers don't bother to
> read RFC's and find out what characters are allowed in email addresses.
> Many sites will not accept a "+" in your username. I think the old
> default qmail delimiter, "-", is a better choice for those jus
Charles Sprickman a écrit :
> On Mon, 27 Jul 2009, Simon Waters wrote:
>
>> On Monday 27 July 2009 11:13:34 Martijn de Munnik wrote:
>>> Losing catchall seems to be the best solution but some of my customers
>>> want to create an emailaddress for every website the register on.
>>>
>>> m...@desjors
My idea to use
---
inet_protocols=ipv6
smtp_fallback_relay=smtp:[smtp.online.nl]
---
fails, since you can only specify a host, but not a transport. So
disabling IPv6 effectively disables also the ability to reach
smtp.online.nl. The alternative it to have the firewall quickly end any
IPv4 SMTP
Joris Dobbelsteen:
> My idea to use
> ---
> inet_protocols=ipv6
> smtp_fallback_relay=smtp:[smtp.online.nl]
> ---
Drop the inet_protocols=ipv6. The SMTP client will
succeed over IPv6, when IPv4 is blocked. If the client
can't reach via either IPv6 or IPv4, use the ISP relayhost.
Wietse
On 7/27/09 1:45 PM, /dev/rob0 wrote:
[1] Strictly speaking, it's $smtp_helo_name which should resolve, but
the default value for smtp_helo_name is $myhostname, and I would
not generally recommend setting smtp_helo_name without good reason.
My MTA is on the DMZ with an FQDN and IP on
When setting up Postfix with Amavis, ClamAV and spamassassin, should one
see spamassassin working (I am using a Ubuntu server)
--
You have a Good Day now,
Carl A Jeptha
http://www.airnet.ca
Office Phone: 905 349-2084
Office Hours: 9:00am - 5:00pm
skype cajeptha
Carl A jeptha wrote:
> When setting up Postfix with Amavis, ClamAV and spamassassin, should one
> see spamassassin working (I am using a Ubuntu server)
>
True?
~Seth
Carl A jeptha wrote:
> When setting up Postfix with Amavis, ClamAV and spamassassin, should
> one see spamassassin working (I am using a Ubuntu server)
This might be better asked on an amavisd forum -
But having said that, the spamassassin classes are actually called
directly by amavis, so you wo
Agree with the other, probably better for amavis-users list; however,
the answer is typically No. Amavis calls SA as a perl module. When
SA is processing you'll see amavisd processes in your ps list only,
not SA.
- N
On Mon, Jul 27, 2009 at 4:38 PM, Carl A jeptha wrote:
> When setting up Postfi
On 7/27/2009 7:38 PM, Carl A jeptha wrote:
When setting up Postfix with Amavis, ClamAV and spamassassin, should one
see spamassassin working (I am using a Ubuntu server)
Yes, you should. One config item I'm still troubled by is:
@local_domains_maps If the domain you're receiving mail at isn't
Hello,
To test Spam Assassin you can compose an email and within the body include:
XJS*C4JDBQADN1.NSBN3*2IDNEN*GTUBE-STANDARD-ANTI-UBE-TEST-EMAIL*C.34X
This will trigger spam assassin
2009/7/28 Joe :
> Carl A jeptha wrote:
>> When setting up Postfix with Amavis, ClamAV and spamassassin, should
On Monday 27 July 2009 18:07:51 ghe wrote:
> On 7/27/09 1:45 PM, /dev/rob0 wrote:
> > [1] Strictly speaking, it's $smtp_helo_name which should resolve, but
> > the default value for smtp_helo_name is $myhostname, and I would
> > not generally recommend setting smtp_helo_name without good
On Tue, July 28, 2009 01:07, ghe wrote:
> My MTA is on the DMZ with an FQDN and IP on a 1918 network. That IP gets
> NAT'ed on its way out to one that resolves to a218.slsware.com. So I set
> the helo name to what is seen by the universe.
>
> Is that a good enough reason?
yes if you make sure th
On Mon, July 27, 2009 23:06, Halassy Zoltán wrote:
> domain.com. MX 10 real.example.com.
> otherdomain.com. MX 10 real.example.com.
> somedomain.com. MX 10 real.example.com.
> mail.example.com. CNAME real.example.com.
imho mx records must not be a cname
--
xpoint
Hi Mouss,
The informaiton about Postfix environment follows :-
Postfix 2.5.1 (Ubuntu package)
Ubuntu 8.04.2 LTS
The content of main.cf using 'postconf -n' follows :-
=== begin of postconf -n ===
alias_database =
alias_maps =
append_dot_mydomain = no
biff = no
config_directory = /etc/postfix
On Mon, Jul 27, 2009 at 8:45 PM, Benny Pedersen wrote:
>
> On Mon, July 27, 2009 23:06, Halassy Zoltán wrote:
>
>> domain.com. MX 10 real.example.com.
>> otherdomain.com. MX 10 real.example.com.
>> somedomain.com. MX 10 real.example.com.
>> mail.example.com. CNAME real.example.com.
>
> imho mx reco
On Monday 27 July 2009 20:54:25 Aaron Wolfe wrote:
> On Mon, Jul 27, 2009 at 8:45 PM, Benny Pedersen wrote:
> > On Mon, July 27, 2009 23:06, Halassy Zoltán wrote:
> >> domain.com. MX 10 real.example.com.
> >> otherdomain.com. MX 10 real.example.com.
> >> somedomain.com. MX 10 real.example.com.
> >>
Bastian Blank wrote:
On Mon, Jul 27, 2009 at 08:03:20AM -0400, Wietse Venema wrote:
Jake Vickers:
Now I know I posted the other day about disabling SSLv2, but if I add
That solution was for MANDATORY TLS encryption. If TLS is not mandatory,
then disabling SSLv2 is pointless: you allow plaintex
On Mon, July 27, 2009 18:21, Magnus Bäck wrote:
> On Monday, July 27, 2009 at 18:05 CEST,
> Pablo Yaggi wrote:
>
>> On Monday 27 July 2009 12:46:04 pm Magnus Bäck wrote:
>> > On Monday, July 27, 2009 at 16:37 CEST,
>> > Pablo Yaggi wrote:
>> >
>> > > taking a deep look into your
>solution proposed by mouss:
>remove: this line:xfilter "/usr/bin/spamc"from maildroprc
I removed xfilter "/usr/bin/spamc"from maildroprcrestarted all services
but am still getting the following in my logs...
Jul 17 06:18:42 mail spamc[32239]: connect(AF_INET)
> I have gone through the postfix configs and amavis configs and could not f=
> ind any reference to spamc.. so where could this be coming from?
It should not be in amavisd-new: in normal configuration,
amavisd-new loads SpamAssassin as a Perl module and does not use
spamc/spamd mechanism.
You
Hi,
I read and re-read the address-rewriting readme and coul dnot find any
indication on the way to rewrite addresses to include GECOS
information:
o...@cs.ait.ac.th => Olivier Nicole
Is that possible in Postfix? I beleive yes.
Where is that done and how?
Best regards,
Olivier
63 matches
Mail list logo
