1 |
On Sunday 20 September 2009, Daniel Troeder wrote: |
2 |
> On Sun, 2009-09-20 at 21:38 +0100, Mick wrote: |
3 |
> > On Sunday 20 September 2009, Harry Putnam wrote: |
4 |
> > > Mick <michaelkintzios@×××××.com> writes: |
5 |
> > > > -----The following addresses had permanent fatal errors----- |
6 |
> > > > <email_account@×××.com> |
7 |
> > > > (reason: 550 5.1.0 <nagios@×××××××××××××××××.com> sender rejected : |
8 |
> > > > invalid sender domain) |
9 |
> > > > |
10 |
> > > > -----Transcript of session follows ----- |
11 |
> > > > |
12 |
> > > > ... while talking to smtp.ISP.com: |
13 |
> > > >>>> MAIL From:<nagios@×××××××××××××××××.com> SIZE=745 AUTH=<> |
14 |
> > > > |
15 |
> > > > <<< 550 5.1.0 <nagios@×××××××××××××××××.com> sender rejected : |
16 |
> > > > invalid sender domain |
17 |
> > > > 554 5.0.0 Service unavailable |
18 |
> > > > ================================================================ |
19 |
> > > > |
20 |
> > > > Does this fail because the ISP's reverse DNS on my dynamically |
21 |
> > > > allocated IP address resolves to an ISP domain instead of |
22 |
> > > > myserver.mydomain.com? |
23 |
> > > > |
24 |
> > > > Is there something I could change in the configuration of my server |
25 |
> > > > to make this work again? |
26 |
> > > |
27 |
> > > I think you might avoid the problem by making sendmail Impersonate your |
28 |
> > > isps domain. |
29 |
> > > |
30 |
> > > Using some or all of these settings in sendmail.mc |
31 |
> > > MASQUERADE_AS(`yourISP.domain')dnl |
32 |
> > > MASQUERADE_DOMAIN(`youractual.domain')dnl |
33 |
> > > FEATURE(masquerade_entire_domain)dnl |
34 |
> > > FEATURE(masquerade_envelope)dnl |
35 |
> > |
36 |
> > Yes, that should fix the reverse DNS problem alright, but then people who |
37 |
> > receive email notifications from myserver will be confused by the domain |
38 |
> > that these messages are sent from. |
39 |
> |
40 |
> I don't know this sendmail feature, but I think sendmail should not |
41 |
> modify your message, but just the envelop. So `youractual.domain' would |
42 |
> still be in the "To"-header, while `yourISP.domain' is in the envelop. |
43 |
> That should make your ISP happy, and no receiver will ever notice |
44 |
> (except if they look at the headers), because MUAs only show the |
45 |
> "To"-header :) |
46 |
> |
47 |
> Your ISP could still check the "To"-header - but that would be just |
48 |
> plain ugly... |
49 |
> |
50 |
> > I could also use the ISP's domain for my IP address in the server's |
51 |
> > /etc/hosts file - although it would have the same problem with regards to |
52 |
> > the domain that messages are sent from. |
53 |
|
54 |
I will give it a go - hopefully the ISP will be happy and I won't need to |
55 |
register with a mail relaying service. |
56 |
|
57 |
Thanks for your suggestions. |
58 |
-- |
59 |
Regards, |
60 |
Mick |