On 23.04.12 08:22, Sam Varshavchik wrote:
Have your customers connect to the appropriate IP for them. This is
much ado about nothing. Whether it's IPs or domains, anyone can
connect to any IP address; even more so anyone can use any return
address they wish to use.
Matus UHLAR - fantomas writes:
On 24/04/12 17:11, Matus UHLAR - fantomas wrote:
I hope the OP won't have users sending their spam forcifully
through different IP, to get someone other blacklisted...
Actually, one of the reasons for wanting to use this system is
exactly so that if one vhost does get blacklisted it does not
On 22.04.12 17:47, Sam Varshavchik wrote:
Let's try this again.
;-)
This is a development build of Courier packages.
Download: http://www.courier-mta.org/download.php
==Changes
* Put back sysinit scripts into the RPM package, so it can be built
on RHEL and Cent-OS without systemd.
* Do not
Mark Constable writes:
On 23/04/12 16:29, Mark Constable wrote:
Replace *SOURCE_ADDRESS* and *SOURCE_ADDRESS_IPV6* variables with
ipout and ip6out configuration files, which offer more functionality.
Wonderful Sam. I have a server set up with 3 IPs, domainnames and certs
to try this out
Matus UHLAR - fantomas writes:
* Replace '''SOURCE_ADDRESS''' and '''SOURCE_ADDRESS_IPV6'''
variables with ipout and ip6out configuration files, which offer more
functionality. The outgoing IP address may be specified based on the
IP address the sending client connected to, to relay the
On 23/04/12 20:49, Sam Varshavchik wrote:
Apr 23 02:14:32 u1 courieresmtpd: error,relay=:::xx.xx.132.242,
from=ad...@.com,to=ma...@renta.net: 513 Relaying denied.
You need to authenticate, or have the sending IP address have RELAYCLIENT set.
Isn't this authenticating?
Received:
On 23/04/12 20:49, Sam Varshavchik wrote:
shall we see it on courier's webpage?
Eventually.
https://gist.github.com/2470290
--
For Developers, A Lot Can Happen In A Second.
Boundary is the first to Know...and Tell
On 22.04.12 17:47, Sam Varshavchik wrote:
* Replace '''SOURCE_ADDRESS''' and '''SOURCE_ADDRESS_IPV6'''
variables with ipout and ip6out configuration files, which offer more
functionality. The outgoing IP address may be specified based on the
IP address the sending client connected to, to relay
On 23/04/12 21:56, Matus UHLAR - fantomas wrote:
so, while we can send mail with different source IPs
depending on which IP it was received on, we can't do it
according to source domains or other reasons. So, we can't
differ between different (kinds of), customers, VIP's etc...
I find this
Mark Constable writes:
On 23/04/12 20:49, Sam Varshavchik wrote:
shall we see it on courier's webpage?
Eventually.
https://gist.github.com/2470290
Yes, well, as I said, eventualy. That documentation is part of the man page,
which does get pushed to www.courier-mta.org, when the content
Am 23.04.2012 13:02, schrieb Mark Constable:
Isn't this authenticating?
Received: from [xx.xx.132.242] (zz.zzz.com [:::xx.xx.132.242])
(SSL: TLSv1/SSLv3,256bits,CAMELLIA256-SHA)
by .com with ESMTPS; Mon, 23 Apr 2012 02:13:47 -0700
id 00023701.4F951D4C.0467
Mark Constable writes:
On 23/04/12 20:49, Sam Varshavchik wrote:
Apr 23 02:14:32 u1 courieresmtpd: error,relay=:::xx.xx.132.242,
from=ad...@.com,to=ma...@renta.net: 513 Relaying denied.
You need to authenticate, or have the sending IP address have RELAYCLIENT
set.
Isn't this
Matus UHLAR - fantomas writes:
On 22.04.12 17:47, Sam Varshavchik wrote:
* Replace '''SOURCE_ADDRESS''' and '''SOURCE_ADDRESS_IPV6'''
variables with ipout and ip6out configuration files, which offer more
functionality. The outgoing IP address may be specified based on the
IP address the sending
On 23/04/12 22:13, Sam Varshavchik wrote:
https://gist.github.com/2470290
Yes, well, as I said, eventualy. That documentation is part
of the man page, which does get pushed to www.courier-mta.org,
when the content gets refreshed.
Yep. It's just that in the mean time no one can read up about
On 23/04/12 21:34, Bernd Wurst wrote:
Received: from [192.168.0.101] (foo [:::x.x.x.x])
(AUTH: PLAIN be...@bwurst.org,
TLS: TLSv1/SSLv3,256bits,CAMELLIA256-SHA)
by .org with ESMTPSA; Mon, 23 Apr 2012 13:21:04 +0200
Look at AUTH:
Just because you see something with TLS/SSL,
On 23/04/12 22:40, Mark Constable wrote:
Doh, of course. My fresh Courier install is probably missing
something.
Argh! My ./esmtpd:ESMTPAUTH= was empty!
--
For Developers, A Lot Can Happen In A Second.
Boundary is the
On 22.04.12 17:47, Sam Varshavchik wrote:
* Replace '''SOURCE_ADDRESS''' and '''SOURCE_ADDRESS_IPV6'''
variables with ipout and ip6out configuration files, which offer more
functionality. The outgoing IP address may be specified based on the
IP address the sending client connected to, to relay the
On 23/04/12 22:49, Mark Constable wrote:
Argh! My ./esmtpd:ESMTPAUTH= was empty!
Sorry for the noise. I meant to post the error below when getting
past the silly mis-step above...
Apr 23 05:14:36 u1 courieresmtp:
id=00023625.4F954552.0A46,
from=ad...@eth-os.com,
Hi.
Am 23.04.2012 15:23, schrieb Mark Constable:
Cannot assign requested address
This error is typically raised when an outgoing connection shall use an
IP address that is not available on the system.
So what does your file ipout.206.221.219.123 look like? Perhaps an
issue with leading or
On 24/04/12 01:54, Bernd Wurst wrote:
Cannot assign requested address
I added 206.221.219.123 to the contents of ipout.206.221.219.123
and it's now working.
So what does your file ipout.206.221.219.123 look like?
Perhaps an issue with leading or trailing whitespace or garbage?
Sam, does
Hi.
Am 23.04.2012 18:17, schrieb Mark Constable:
On 24/04/12 01:54, Bernd Wurst wrote:
Cannot assign requested address
I added 206.221.219.123 to the contents of ipout.206.221.219.123
and it's now working.
So what does your file ipout.206.221.219.123 look like?
Perhaps an issue with
Hi Sam.
Am 22.04.2012 23:47, schrieb Sam Varshavchik:
*
Replace *SOURCE_ADDRESS* and *SOURCE_ADDRESS_IPV6* variables with
ipout and ip6out configuration files, which offer more
functionality. The outgoing IP address may be specified based on the
IP address the sending
Matus UHLAR - fantomas writes:
On 23.04.12 08:22, Sam Varshavchik wrote:
Have your customers connect to the appropriate IP for them. This is
much ado about nothing. Whether it's IPs or domains, anyone can
connect to any IP address; even more so anyone can use any return
address they wish to
Bernd Wurst writes:
Hi Sam.
Am 22.04.2012 23:47, schrieb Sam Varshavchik:
*
Replace *SOURCE_ADDRESS* and *SOURCE_ADDRESS_IPV6* variables with
ipout and ip6out configuration files, which offer more
functionality. The outgoing IP address may be specified based on the
IP
Bernd Wurst writes:
I took the above to mean that if ipout.206.221.219.123 was empty
then it would use the file extension as the IP to use. Maybe it's
unclear exactly what same address is referring to.
I think you are right, it should work without adding the IP address as
content. Perhaps
25 matches
Mail list logo
