On 4/06/2010 1:08 PM, Sahil Tandon wrote:
>
> That's unfortunate. Now that we have established the issue, it seems to
> me this is no longer the appropriate forum to continue this thread.
> Perhaps you can convince the host to exempt you from the mismatch
> check(s). Good luck.
>
>
I understa
On Fri, Jun 4, 2010 at 12:25 PM, Terry Gilsenan wrote:
> From: owner-postfix-us...@postfix.org [owner-postfix-us...@postfix.org] On
> Behalf Of Paul McGougan [paul.mcgou...@braintree.com.au]
> Sent: Friday, 4 June 2010 12:42 PM
> To: postfix-users@postfix.org
> Subject: Re: Local delivery rejecte
From: owner-postfix-us...@postfix.org [owner-postfix-us...@postfix.org] On
Behalf Of Paul McGougan [paul.mcgou...@braintree.com.au]
Sent: Friday, 4 June 2010 12:42 PM
To: postfix-users@postfix.org
Subject: Re: Local delivery rejected
On 4/06/2010 12:37 PM, Sahil Tandon wrote:
>
> A better solutio
Paul McGougan put forth on 6/3/2010 9:42 PM:
> So that's not really a possibility unfortunately.
What is possible is walking to a new provider.
--
Stan
On Fri, 04 Jun 2010, Paul McGougan wrote:
> On 4/06/2010 12:37 PM, Sahil Tandon wrote:
> >
> > A better solution is for you to configure your MUA to AUTH with
> > mail.limedomains.net.
>
> I did originally use their SMTP servers for sending, however they have
> now been blacklisted by so many peo
On 4/06/2010 12:37 PM, Sahil Tandon wrote:
>
> A better solution is for you to configure your MUA to AUTH with
> mail.limedomains.net.
>
>
Hi Sahil.
I did originally use their SMTP servers for sending, however they have
now been blacklisted by so many people because there are so many
spammers
On Fri, 04 Jun 2010, Paul McGougan wrote:
> Is there some way that they could modify smtpd_sender_restrictions, so
> that they can still use this, but that local deliveries are accepted
> before this check is imposed?
A better solution is for you to configure your MUA to AUTH with
mail.limedomain
Hi Victor.
On 4/06/2010 12:17 PM, Victor Duchovni wrote:
> What is your MUA? What SMTP submission service are you using?
I'm not sure of the relevance of this, because as I have shown, my local
ISP's SMTP server accepts the email and tries to deliver it, but for
completeness sake I'm using Thunde
On 6/2/2010 7:30 AM, Wietse Venema wrote:
I just uploaded new versions of Postfix 2.8-20100601 "experimental"
i think you have typo in your download site wieste, it said
postfix-2.8-20100603.tar.gz , which is not found.
thanks
PT.CITRA SARI MAKMUR
SATELLITE & TERRE
On 4/06/2010 12:12 PM, Sahil Tandon wrote:
> http://www.postfix.org/postconf.5.html#reject_unauthenticated_sender_login_mismatch
>
Thanks Sahil.
Yes, I can see how the description for that matches the problem I am having.
And I can see how this is something that they'd like to use, but I woul
On Fri, Jun 04, 2010 at 11:41:43AM +1000, Paul McGougan wrote:
> 1. I compose an email from an email account that is hosted on my
> limedomains service to an email account that is also hosted on my
> limedomains service (it could be the same or a different account as the
> FROM account, it doesn't
On Fri, 04 Jun 2010, Paul McGougan wrote:
> The problem is:
> 1. I compose an email from an email account that is hosted on my
> limedomains service to an email account that is also hosted on my
> limedomains service (it could be the same or a different account as the
> FROM account, it doesn't ap
Victor Duchovni put forth on 6/3/2010 8:29 PM:
> And Stan also.
As usual, you're right Victor. My apologies to Moe for the "brain damaged"
comment. Unprofessional and uncalled for.
Sorry Moe.
--
Stan
Moe put forth on 6/3/2010 8:10 PM:
> So with that, no hard feelings. I'll make sure to not bother
> you guys again.
No hard feelings intended Moe.
What I just can't wrap my small brain around is how the pain and effort to
insert 'myhostname = mx1.example.com' into main.cf is greater than the pai
Hi.
I have a domain hosted by a hosting service. They are running Postfix as
the mail server there. I have started having a problem with delivery to
local accounts, and they appear to be too stupid to figure out the
problem, and additionally are not native English speakers, so I am
having a lot of
Wietse Venema wrote:
> Moe:
>> The docs for 'myhostname' even explicitly state "The default is to use
>> the fully-qualified domain name from gethostname()", which makes no
>> sense as gethostname() does not normally return a FQDN.
>
> Only a brain-damaged person would claim that Postfix promises
On Fri, Jun 04, 2010 at 01:57:51AM +0200, Jan Kohnert wrote:
> Maybe it got lost due to the language, but: my comment was just sarcasm.
> Only brain-damaged users would remove neccessary parameters out off the
> config file while expecting things to work somehow out-of-the-box by
> magic.
This is
Moe:
> The docs for 'myhostname' even explicitly state "The default is to use
> the fully-qualified domain name from gethostname()", which makes no
> sense as gethostname() does not normally return a FQDN.
Only a brain-damaged person would claim that Postfix promises
domain auto-detection.
Any co
Jan Kohnert wrote:
> Stan Hoeppner schrieb:
>> Jan Kohnert put forth on 6/3/2010 5:55 PM:
>>> Or let the Debian people write that patch for their version, as their
>>> users are apparently the only ones who comlain and such a fix could
>>> probably mess up more postfix-experienced users... ;)
>> Pl
Stan Hoeppner schrieb:
> Jan Kohnert put forth on 6/3/2010 5:55 PM:
> > Or let the Debian people write that patch for their version, as their
> > users are apparently the only ones who comlain and such a fix could
> > probably mess up more postfix-experienced users... ;)
>
> Please don't paint the
Jan Kohnert put forth on 6/3/2010 5:55 PM:
> Or let the Debian people write that patch for their version, as their users
> are apparently the only ones who comlain and such a fix could probably mess
> up
> more postfix-experienced users... ;)
Please don't paint the Debian user base with such a
Victor Duchovni schrieb:
> On Thu, Jun 03, 2010 at 08:36:52PM +0200, Moe wrote:
> > My point is: When 'myhostname' and 'mydomainname' are left out of
> > main.cf then postfix makes an attempt to auto-detect them.
>
> These are MTA configuration variables.
And there would also be the fix in Postfi
> > Currently we use postfixadmin for this, but this is undesirable as it
will
> > often double-up or triple-up entire sends (we intend to fix this,
> > eventually). I know the previous system we used was basically a script
that
> > copied a file into everyone's Inbox under their Maildir folder - w
Jim Wright wrote (on Thu, Jun 03, 2010 at 04:47:05PM -0500):
> On Jun 3, 2010, at 1:36 PM, Moe wrote:
>
> > My point is: When 'myhostname' and 'mydomainname' are left out of main.cf
> > then postfix makes an attempt to auto-detect them.
>
> There's your problem. Fix that. See my original reply
On Jun 3, 2010, at 1:36 PM, Moe wrote:
> My point is: When 'myhostname' and 'mydomainname' are left out of main.cf
> then postfix makes an attempt to auto-detect them.
There's your problem. Fix that. See my original reply at the start of this
thread.
On Thu, Jun 03, 2010 at 05:47:25PM +0200, gmx wrote:
> In our postfix configs, we use multiple queries based on the mysql_table
> that only differ by the postfix listener port as configured in the
> master.cf.
Generally, users (should and do) combine "mysql" tables with "proxy:"
prefixes to reduc
Phil Howard:
> It looks like postmap can read stdin when getting a list of keys for
> delete or query.
As documented in the postmap manpage:
-d key
...
If a key value of - is specified, the program reads key values
from the standard input strea
On Thu, June 3, 2010 6:31 pm, Victor Duchovni wrote:
> On Thu, Jun 03, 2010 at 06:00:26PM -, Pau Amma wrote:
>
>> foo.cf: dbConf.cf.in foo.cf.in
>> cat dbConf.cf.in foo.cf.in > foo.cf
>
> Make that:
>
> foo.cf: dbConf.cf.in foo.cf.in
> $(RM) -f foo.cf.tmp
>
It looks like postmap can read stdin when getting a list of keys for
delete or query. There appeared to be no documented way to read from
stdin to create a new map. So I tried the following:
marconi/root/x0 /root 37# ls -dl
On Thu, Jun 03, 2010 at 08:36:52PM +0200, Moe wrote:
> My point is: When 'myhostname' and 'mydomainname' are left out of
> main.cf then postfix makes an attempt to auto-detect them.
These are MTA configuration variables.
> This auto-detection does not currently follow what other tools like
> 'ho
If you want Postfix to use a some value other than the default
("localdomain" or the kernel domain name), then you must update
the appropriate Postfix configuration parameter.
If you object to the idea of having to update a Postfix configuration
parameter, then you must not use Postfix.
W
On Thu, Jun 03, 2010 at 08:32:16PM +0200, Moe wrote:
> Remember we're talking about the case of auto-detection here
> - if someone is not willing to take that risk then they should hardcode
> 'myhostname' and 'mydomainname' in main.cf, no?
>
> Moreover I'd suggest that postfix may very well accep
Victor Duchovni wrote:
> On Wed, Jun 02, 2010 at 10:46:47PM -0400, Matt Hayes wrote:
>
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=214741
>>
>> Now, I'm not all that bright on how postfix sorts out the hostname, and
>> frankly, I don't care, but I don't like people saying its a 'bug' when
On Thu, Jun 03, 2010 at 08:26:16PM +0200, Moe wrote:
> * Make sure /etc/hosts has something like:
> 127.0.0.1 tail.call tail
>
> * 'hostname' should return: tail
> * 'hostname -f' should now return: tail.call
> * 'postconf -d mydomain' will still return: localdomain
Which is correct behaviour.
I called and talk to globalpops. It is not a range. it is a ip number
like this
ex: 192.168.1.0 --- notice the zero. So I don't think that will work.
They actually recomend what I'm going and that is smtp-auth. But still
any response would be appricated.
thanks,
josh
--
This message h
Wietse Venema wrote:
> Moe:
>> The right way, as explained by Mike Paul in that ticket, would be to
>> call gethostbyname() on the return value of gethostname() and then split
>> the result of *that* into hostname and domainname.
>
> That would be AN INCREDIBLY STUPID IDEA, causing all mail proces
On Thu, Jun 03, 2010 at 06:00:26PM -, Pau Amma wrote:
> foo.cf: dbConf.cf.in foo.cf.in
> cat dbConf.cf.in foo.cf.in > foo.cf
Make that:
foo.cf: dbConf.cf.in foo.cf.in
$(RM) -f foo.cf.tmp
cat dbConf.cf.in foo.cf.in > foo.cf.tmp
mv fo
Wietse Venema wrote:
> Moe:
> [ Charset ISO-8859-1 unsupported, converting... ]
>> Wietse Venema wrote:
>>> Matt Hayes:
Yes.. I know this has come up quite a bit, but on freenode in #postfix
this discussion once again erupted when someone mentioned a bug in
postfix and referencing th
Moe:
> The right way, as explained by Mike Paul in that ticket, would be to
> call gethostbyname() on the return value of gethostname() and then split
> the result of *that* into hostname and domainname.
That would be AN INCREDIBLY STUPID IDEA, causing all mail processes
to hang when the network i
On 6/3/2010 2:51 PM, Josh Cason wrote:
> I decided to impliment some new security and remove pop-before-smtp. But
> I have some dialup users and some of them use email. The company I'm
> going through is global pops. I would like to add there iprange to
> postfix as allowed users. I looked at /etc/
On 06/03/2010 08:51 PM, Josh Cason wrote:
I decided to impliment some new security and remove pop-before-smtp.
But I have some dialup users and some of them use email. The company
I'm going through is global pops. I would like to add there iprange to
postfix as allowed users. I looked at /etc/p
I decided to impliment some new security and remove pop-before-smtp.
But I have some dialup users and some of them use email. The company
I'm going through is global pops. I would like to add there iprange to
postfix as allowed users. I looked at /etc/postfix/access list example
192.168.0.1
Moe:
[ Charset ISO-8859-1 unsupported, converting... ]
> Wietse Venema wrote:
> > Matt Hayes:
> >> Yes.. I know this has come up quite a bit, but on freenode in #postfix
> >> this discussion once again erupted when someone mentioned a bug in
> >> postfix and referencing this:
> >>
> >> http://bugs.
On Thu, Jun 03, 2010 at 07:44:58PM +0200, Moe wrote:
> I was the guy complaining on IRC, so I'd like to jump in and clarify:
>
> * The bug is still present in 2.7.0, which is not 8 years old
There is no bug. Postfix is working *exactly* as designed. And the
design has been given much thought.
>
On Wed, Jun 02, 2010 at 10:46:47PM -0400, Matt Hayes wrote:
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=214741
>
> Now, I'm not all that bright on how postfix sorts out the hostname, and
> frankly, I don't care, but I don't like people saying its a 'bug' when I
> have no problems following
On Thu, June 3, 2010 3:35 pm, gmx wrote:
> So as per http://www.postfix.org/mysql_table.5.html each of the mysql
> config files contains a
>
> hosts = mydbhost.domain.tld
> user = mydbUser
> password = myPassword
> dbname = myDB
>
> section before the query.
> Once any of these parameters needs to
Wietse Venema wrote:
> Matt Hayes:
>> Yes.. I know this has come up quite a bit, but on freenode in #postfix
>> this discussion once again erupted when someone mentioned a bug in
>> postfix and referencing this:
>>
>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=214741
>
> They are talking abo
On 06/03/2010 05:35 PM, gmx wrote:
Dear list,
In our postfix configs, we use multiple queries based on the mysql_table
from the same DB .
So as per http://www.postfix.org/mysql_table.5.html each of the mysql config
files contains a
hosts = mydbhost.domain.tld
user = mydbUser
password = myPassw
On Jun 3, 2010, at 8:25 AM, Wietse Venema wrote:
> Jim Wright:
>> OS X 10.6.3, attempting to build 2.7.1-RC1:
>>
>> (snip)
>> In file included from dns_lookup.c:152:
>> dns.h:26:28: error: nameser_compat.h: No such file or directory
>> make: *** [dns_lookup.o] Error 1
>> make: *** [update] Error
On 2-Jun-2010, at 15:59, Mike Hutchinson wrote:
>
> Currently we use postfixadmin for this, but this is undesirable as it will
> often double-up or triple-up entire sends (we intend to fix this,
> eventually). I know the previous system we used was basically a script that
> copied a file into ever
Dear list,
In our postfix configs, we use multiple queries based on the mysql_table
that only differ by the postfix listener port as configured in the master.cf
.
So as per http://www.postfix.org/mysql_table.5.html if instead of the query
containing each a different hard coded
... where port
Dear list,
In our postfix configs, we use multiple queries based on the mysql_table
from the same DB .
So as per http://www.postfix.org/mysql_table.5.html each of the mysql config
files contains a
hosts = mydbhost.domain.tld
user = mydbUser
password = myPassword
dbname = myDB
section before the
On 6/3/2010 2:22 AM, Khawaja M. Jawad wrote:
Hi Everyone,
As shown below, one of my client is unable to send email. Can anyone let
me know what could be the reason…?
###
Jun 1 15:29:50 smtp postfix/smtpd[20384]: connec
Jim Wright:
> OS X 10.6.3, attempting to build 2.7.1-RC1:
>
> (snip)
> In file included from dns_lookup.c:152:
> dns.h:26:28: error: nameser_compat.h: No such file or directory
> make: *** [dns_lookup.o] Error 1
> make: *** [update] Error 1
>
>
> In my 2.7 build, I referenced this file: arpa/na
Matt Hayes:
> Yes.. I know this has come up quite a bit, but on freenode in #postfix
> this discussion once again erupted when someone mentioned a bug in
> postfix and referencing this:
>
> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=214741
They are talking about an eight-year old version of
punit jain:
> Hi Wietse,
>
> Gone through the links. I find Milter to be more suitable for my
> requirement. A quick query on smtpd_milters, the call to external filter
> would be same way the smtp negotiation happens ( HELO, MAIL FROM, RCPT TO
> etc ) before accepting the message to be queued or
Hi Wietse,
Gone through the links. I find Milter to be more suitable for my
requirement. A quick query on smtpd_milters, the call to external filter
would be same way the smtp negotiation happens ( HELO, MAIL FROM, RCPT TO
etc ) before accepting the message to be queued or is the call in some form
Hi Everyone,
As shown below, one of my client is unable to send email. Can anyone let me
know what could be the reason.?
###
Jun 1 15:29:50 smtp postfix/smtpd[20384]: connect from
unknown[10.184.10.213]
58 matches
Mail list logo
