On 27/01/11 13:19, Wietse Venema wrote:
> John Fawcett:
>
>> Claudio
>> the problem is happening because your column definition for "domain"
>> column has character set latin1 (which by default has collation
>> latin_swedish_ci) and the data being passed from postfix is in utf8
>> (which by defa
Am 28.01.2011 03:39, schrieb Michael Westman:
> I've got Postfix and alterMIME configured on Ubuntu 10.10 Everything
> is working perfectly except that the disclaimer that is inserted by
> alterMIME is inserting an equal sign followed by a space. This is not
> there in the disclaimer.txt file.
>
On 01/27/2011 11:51 PM, Wietse Venema wrote:
> Steve Jenkins:
> [ Charset ISO-8859-1 unsupported, converting... ]
>> If we're using mutliple milters (with smtpd_milters), is it
>> appropriate to separate them with:
>>
>> a space?
>> smtpd_milters = inet:localhost:10035 inet:localhost:10036
>>
>> a
John Fawcett:
> On 27/01/11 13:19, Wietse Venema wrote:
> > John Fawcett:
> >
> >> Claudio
> >> the problem is happening because your column definition for "domain"
> >> column has character set latin1 (which by default has collation
> >> latin_swedish_ci) and the data being passed from postfix
>>b) how do I determine the source IP address of those domains
>Email can come from anywhere, via multiple routes that do not
> have any direct relation with the sending domain.
I thought if I entered the domain name, say dsta.gov.sg into
www.mxtoolbox.com, it would list out all the smtp/mail se
So is it right to say that though I want only a small handful of
users from certain domains/organizations to send email to me,
it could be email gateways (or "mail relay servers" ??) that are
unrelated to those domains/organizations that make Tcp25
connection to my email server?
As for the externa
On Fri, Jan 28, 2011 at 11:36:28PM +0800, sunhux G wrote:
> So is it right to say that though I want only a small handful of
> users from certain domains/organizations to send email to me,
> it could be email gateways (or "mail relay servers" ??) that are
> unrelated to those domains/organizations
Most of our Postfices disable local delivery with,
local_transport = error:...
but one web server is running Mailman and can't do that (I think?)
because it needs to support alias_maps like,
members: "|/usr/lib/mailman/mail/mailman post members"
The result is that some mail gets
We want the headers to correct show the mail system, with a bug in
centos, it shows localhost or 127.0.0.1 where it should show
mail.sheltoncomputers.com for PROPER, correct tracking.
/etc/postfix/header_checks.pcre:
s/(127\.0\.0\.1|localhost)/gi
REPLACE mail.sheltoncomputers.com
Jerrale G:
> We want the headers to correct show the mail system, with a bug in
> centos, it shows localhost or 127.0.0.1 where it should show
> mail.sheltoncomputers.com for PROPER, correct tracking.
>
> /etc/postfix/header_checks.pcre:
>
> s/(127\.0\.0\.1|localhost)/gi
Postfix behaves
On 1/28/2011 12:51 PM, Jerrale G wrote:
> We want the headers to correct show the mail system, with a bug in
> centos, it shows localhost or 127.0.0.1 where it should show
> mail.sheltoncomputers.com for PROPER, correct tracking.
>
> /etc/postfix/header_checks.pcre:
>
> s/(127\.0\.0\.1|localho
On 1/28/2011 1:13 PM, Brian Evans - Postfix List wrote:
On 1/28/2011 12:51 PM, Jerrale G wrote:
We want the headers to correct show the mail system, with a bug in
centos, it shows localhost or 127.0.0.1 where it should show
mail.sheltoncomputers.com for PROPER, correct tracking.
/etc/postfix/h
* Michael Orlitzky :
> but one web server is running Mailman and can't do that (I think?)
If it has a seperate domain for lists, you can use:
lists.domain.com local:
in transport_maps and thus route that one domain to local:
--
Ralf Hildebrandt
Geschäftsbereich IT | Abteilung Netzwerk
Cha
On 01/28/2011 02:09 PM, Ralf Hildebrandt wrote:
> * Michael Orlitzky :
>
>> but one web server is running Mailman and can't do that (I think?)
> If it has a seperate domain for lists, you can use:
>
> lists.domain.com local:
>
> in transport_maps and thus route that one domain to local:
>
Wou
On 1/28/2011 12:24 PM, Jerrale G wrote:
This is fine as long as I know how to keep the other part of
the line in a variable, like $1 or $3 and know how to put it
all back together afterwards. Could someone help me with this,
please?
An example replacement given the header
X-MyHeader: this is it
On 1/28/2011 1:53 PM, Michael Orlitzky wrote:
On 01/28/2011 02:09 PM, Ralf Hildebrandt wrote:
* Michael Orlitzky:
but one web server is running Mailman and can't do that (I think?)
If it has a seperate domain for lists, you can use:
lists.domain.com local:
in transport_maps and thus route
On 01/28/2011 03:06 PM, Noel Jones wrote:
> On 1/28/2011 1:53 PM, Michael Orlitzky wrote:
>> On 01/28/2011 02:09 PM, Ralf Hildebrandt wrote:
>>> * Michael Orlitzky:
>>>
but one web server is running Mailman and can't do that (I think?)
>>> If it has a seperate domain for lists, you can use:
>>
* Michael Orlitzky :
> I tried with transport_maps:
>
> example.com local:
>
> and local_transport = error:... and got this (http3.viabit.com is myorigin):
>
> Jan 28 15:05:25 http3 postfix/error[20737]: 24944A302DF:
> to=, orig_to=,
> relay=none, delay=2.7, delays=2.7/0/0/0, dsn=5.0.0
On 28/01/11 13:12, Wietse Venema wrote:
> John Fawcett:
>
> If UTF8SMTP support is introduced in Postfix, what rules should Postfix
>> follow for interpreting email addresses? That if there is at least one
>> non-ascii character, the string is treated as utf8 else it is treated as
>> ascii? What
On 1/28/2011 2:55 PM, Noel Jones wrote:
On 1/28/2011 12:24 PM, Jerrale G wrote:
This is fine as long as I know how to keep the other part of
the line in a variable, like $1 or $3 and know how to put it
all back together afterwards. Could someone help me with this,
please?
An example replacemen
On 1/28/2011 3:43 PM, Jerrale G wrote:
On 1/28/2011 2:55 PM, Noel Jones wrote:
On 1/28/2011 12:24 PM, Jerrale G wrote:
This is fine as long as I know how to keep the other part of
the line in a variable, like $1 or $3 and know how to put it
all back together afterwards. Could someone help me wi
On 1/28/2011 3:43 PM, Jerrale G wrote:
On 1/28/2011 2:55 PM, Noel Jones wrote:
On 1/28/2011 12:24 PM, Jerrale G wrote:
This is fine as long as I know how to keep the other part of
the line in a variable, like $1 or $3 and know how to put it
all back together afterwards. Could someone help me wi
John Fawcett:
> On 28/01/11 13:12, Wietse Venema wrote:
> > John Fawcett:
> >
> > If UTF8SMTP support is introduced in Postfix, what rules should Postfix
> >> follow for interpreting email addresses? That if there is at least one
> >> non-ascii character, the string is treated as utf8 else it is
On 1/28/2011 3:49 PM, Jerrale G wrote:
On 1/28/2011 3:43 PM, Jerrale G wrote:
On 1/28/2011 2:55 PM, Noel Jones wrote:
On 1/28/2011 12:24 PM, Jerrale G wrote:
This is fine as long as I know how to keep the other part of
the line in a variable, like $1 or $3 and know how to put it
all back toget
Jerrale G wrote:
sorry for not including. Centos automatically puts 127.0.0.1 as
$hostname in /etc/hosts.
could you not fix /etc/hosts? (So far as I'm concerned, the only
hostname legitimately associated with 127.0.0.1 is localhost. Anything
else is broken by definition. Others may n
On 1/28/2011 5:05 PM, Kris Deugau wrote:
Jerrale G wrote:
sorry for not including. Centos automatically puts 127.0.0.1 as
$hostname in /etc/hosts.
could you not fix /etc/hosts? (So far as I'm concerned, the
only hostname legitimately associated with 127.0.0.1 is localhost.
Anything e
On 01/28/2011 03:28 PM, Ralf Hildebrandt wrote:
> * Michael Orlitzky :
>
>> I tried with transport_maps:
>>
>> example.com local:
>>
>> and local_transport = error:... and got this (http3.viabit.com is myorigin):
>>
>> Jan 28 15:05:25 http3 postfix/error[20737]: 24944A302DF:
>> to=, orig_to
On 28/01/11 21:56, Wietse Venema wrote:
> John Fawcett:
>
>> On 28/01/11 13:12, Wietse Venema wrote:
>>
>>> John Fawcett:
>>>
>>> If UTF8SMTP support is introduced in Postfix, what rules should Postfix
>>>
follow for interpreting email addresses? That if there is at least one
what i really not understand in this post is why the OP
doens not change all his charset/collation to UTF8
to avoid mixing?
Am 28.01.2011 23:37, schrieb John Fawcett:
> On 28/01/11 21:56, Wietse Venema wrote:
>> John Fawcett:
>>
>>> On 28/01/11 13:12, Wietse Venema wrote:
>>>
John Faw
On Fri, Jan 28, 2011 at 11:40:42PM +0100, Reindl Harald wrote:
> what i really not understand in this post is why the OP
> doens not change all his charset/collation to UTF8
> to avoid mixing?
The input may not be valid UTF8. Not all octet strings are valid
UTF8. Someone posted a solution using
Am 28.01.2011 23:44, schrieb Victor Duchovni:
> On Fri, Jan 28, 2011 at 11:40:42PM +0100, Reindl Harald wrote:
>
>> what i really not understand in this post is why the OP
>> doens not change all his charset/collation to UTF8
>> to avoid mixing?
>
> The input may not be valid UTF8. Not all octet
On Sat, Jan 29, 2011 at 12:02:17AM +0100, Reindl Harald wrote:
> > The input may not be valid UTF8. Not all octet strings are valid
> > UTF8. Someone posted a solution using
>
> Yes but this seems not the problem as long the message is "mix of collations"
Fixing a tiny subset of use-cases is not
On 29/01/11 00:02, Reindl Harald wrote:
> Am 28.01.2011 23:44, schrieb Victor Duchovni:
>
>> On Fri, Jan 28, 2011 at 11:40:42PM +0100, Reindl Harald wrote:
>>
>>
>>> what i really not understand in this post is why the OP
>>> doens not change all his charset/collation to UTF8
>>> to avoid m
33 matches
Mail list logo
