I used fetchmail to retreive email from the university and it hands off
the local system which cause the mail to try to be forward to
localhost.com. Obviously I've made a big error somewhere, but I can't
track it down
Sep 19 22:52:36 www postfix/error[11778]: 26479161244:
to=, orig_
On Fri, Sep 19, 2014 at 10:58:17PM -0400, Ruben Safir wrote:
> I used fetchmail to retreive email from the university and it hands off
> the local system which cause the mail to try to be forward to
> localhost.com. Obviously I've made a big error somewhere, but I can't
&g
On 19 Sep 2014, at 20:58 , Ruben Safir wrote:
> I used fetchmail to retreive email from the university and it hands off
> the local system which cause the mail to try to be forward to
> localhost.com. Obviously I've made a big error somewhere, but I can't
> track it dow
On Sat, Sep 20, 2014 at 04:42:01AM +, Viktor Dukhovni wrote:
> On Fri, Sep 19, 2014 at 10:58:17PM -0400, Ruben Safir wrote:
>
> > I used fetchmail to retreive email from the university and it hands off
> > the local system which cause the mail to try to be forward to
On Sat, Sep 20, 2014 at 03:13:51AM -0600, LuKreme wrote:
> On 19 Sep 2014, at 20:58 , Ruben Safir wrote:
> > I used fetchmail to retreive email from the university and it hands off
> > the local system which cause the mail to try to be forward to
> > localhost.com. Obvi
ands off
> > > the local system which cause the mail to try to be forward to
> > > localhost.com. Obviously I've made a big error somewhere, but I can't
> > > track it down
> >
> > Your mistake is misusing "localhost.com". That's someo
ail to try to be forward to
>>> localhost.com. Obviously I've made a big error somewhere, but I can't
>>> track it down
>>
>> $ dig localhost.com | grep -A1 ANSWER | tail -1
>> localhost.com. 5588IN A 74.125.224.72
>
>
> > > > I used fetchmail to retreive email from the university and it hands off
> > > > the local system which cause the mail to try to be forward to
> > > > localhost.com. Obviously I've made a big error somewhere, but I can't
> > > &
Am 21.09.2014 um 11:11 schrieb Ruben Safir:
> Ah - thank you. I thought you ment that, but I was being dense.
> When I ran fetchmail through verbose I saw that it connected to
> localhost on port 25 so I figured that maybe postfix was attaching a
> .com to that. I just wanted to make double sure
On Sun, Sep 21, 2014 at 05:11:02AM -0400, Ruben Safir wrote:
> > > > Your mistake is misusing "localhost.com". That's someone else's
> > > > domain. Do set "mydomain" explicitly to something sensible in
> > > > main.cf.
>
les mail for 4 domains.
> > >
> > > I thought that's what I said.
> >
> > :) well, we people from brooklyn sometimes need to be told twice.
>
> I hope twice was enough. Add a correct "mydomain" setting to
> main.cf.
That will work
On Sun, Sep 21, 2014 at 03:00:45PM -0400, Wietse Venema wrote:
> > I hope twice was enough. Add a correct "mydomain" setting to
> > main.cf.
>
> That will work. Another solution is setting append_dot_mydomain=no,
> so that user@localhost will become u...@localho
> > :) well, we people from brooklyn sometimes need to be told twice.
>
> I hope twice was enough. Add a correct "mydomain" setting to
> main.cf.
>
Yes and thanks for the explaination and the fix.
Ruben
> --
> Viktor.
--
So many immigrant groups have swept through our town
that Bro
>
> That will work. Another solution is setting append_dot_mydomain=no,
> so that user@localhost will become u...@localhost.com.
>
Yes - I am confused by this a little bit. Why would postfix want to add
a dot com to any outgoing email?
Ruben
--
DRM is THEFT - We are the STAKE
Am 28.09.2014 um 08:23 schrieb Ruben Safir:
>>
>> That will work. Another solution is setting append_dot_mydomain=no,
>> so that user@localhost will become u...@localhost.com.
>>
>
>
>
>
> Yes - I am confused by this a little bit. Why would postfix
temporarily
suspended: connect to localhost.com[74.125.224.72]:25: Connection timed out)
I have no idea where this r...@localhost.com is coming from. It must be a
misconfiguration but I cannot find it.
I have grep-ed /etc/postfix for all instances of localhost and there is nowhere
an instance of
/0.02/0/0, dsn=4.4.1, status=deferred (delivery
temporarily suspended: connect to localhost.com[74.125.224.72]:25:
Connection timed out)
I have no idea where this r...@localhost.com is coming from. It must
be a misconfiguration but I cannot find it.
I have grep-ed /etc/postfix for all
I have no idea where this r...@localhost.com is coming from. It must be a
misconfiguration but I cannot find it.
Since root@localhost is rewritten in r...@localhost.com, I would also check in
aliases/virtual_aliases, etc.
Not likely, but check if something wacky got into /etc/aliases as
Thank you, I have checked all aliases, virtual and otherwise and there is
nothing...This is strange...
Would adding a catchall alias (should be in /etc/aliases or virtual aliases?)
for root perhaps do the trick of stopping to trying r...@localhost.com?
On Thursday, June 6, 2024 at 01:53:20
Trouble Shooting Areas
==
Make sure mydestination contains localhost for postfix to know it gets
delivered locally.
Also double check myhostname, mydomain, and myorigin for anything that doesn't
look right.
Make sure nothing in /etc/aliases is sending root somewhere else.
/0/0, dsn=4.4.1, status=deferred (delivery temporarily
> suspended: connect to localhost.com[74.125.224.72]:25: Connection timed out)
>
Maybe you have "myhostname = something.com" and Postfix infers $mydomain from
that.
Wietse
___
s postfix/error[86771]: 5D9D148296D:
> > to=, orig_to=, relay=none, delay=4099,
> > delays=4099/0.02/0/0, dsn=4.4.1, status=deferred (delivery temporarily
> > suspended: connect to localhost.com[74.125.224.72]:25: Connection timed out)
> >
>
> Maybe you have "
belongs to Google.
> > > Jun 5 19:09:32 arthemis postfix/error[86771]: 5D9D148296D:
> > > to=, orig_to=, relay=none,
> > > delay=4099, delays=4099/0.02/0/0, dsn=4.4.1, status=deferred (delivery
> > > temporarily suspended: connect to localhost.com[74.125.
On Thu, Jun 06, 2024 at 10:40:20PM -0400, Wietse Venema via Postfix-users wrote:
> > It might be reasonable to infer "mydomain = $myhostname" when the latter
> > has two or fewer labels.
>
> There are top-level domains with more than 2 components.
Yes, but we could handle at least the obvious ca
24 matches
Mail list logo
