Hi,
I was hoping for some help, I have exchange 2007, assp 2.0.1(1.1.27) &
mail enable. Can receive email fine through assp but cant send out.
I followed the document where I have three ip assigned in my nic 1 for
assp,exchange & mail enable.
I don't know where in assp where you put the ip for Mail enable, is it
under accept all mail?. I setup my exchange outbound on port 325, the
relay port in assp is the ip of exchange listening on port 325, as the
document says to do on the assp website.
When I send email out email in exchange the error says 451 4.4.0 dns
query failed. The error was smtpsend.dns.mxlookback; dns records for
this domain are configured in a loop.
In exchange if I change the send connector to port 25 & through
mx records it works but it doesn't send emails through assp.
In exchange if I route mail through the smart host which is assp it
doesn't work & I get the loopback error.
In assp where Where do you put the relay ip, so it knows to forward it
to mail enable.
Inbound: Assp -> Exchange: works
Outbound: exchange -> assp -> mail enable[mta] -> internet
How does assp know to pass it to mail enable
Where do you enter the ip address in assp 192.168.0.1:125
Hope someone can help me please
>
>
> On 18/08/10 9:14 AM, "Dan Hulme" <[email protected]> wrote:
>
>> Ok, so I discovered by looking at the code, that immed IS required,
>> even if using "ForceRestartAfterCodeChange". However, due to the fact
>> that ASSP does not immediately check after updating the script (60
>> minutes?), the value 'immed' does not really mean "immediate." It
>> means it will immediately update *the next time it checks*. Which is
>> fine, I suppose. But it makes it harder to test if things are
>> working.
>>
>> To make 'immed' actually take effect, I added the following line:
>>
>> $NextCodeChangeCheck=time-1;
>>
>> immediately after:
>>
>> &downloadASSPVersion();
>>
>> Seems to work.
>>
>> -Dan
>>
>> On Tue, Aug 17, 2010 at 2:00 PM, Dan Hulme <[email protected]> wrote:
>>> The setting:
>>>
>>> ForceRestartAfterCodeChange
>>>
>>> Does not seem to work. The process is not getting killed after an
>>> automatic download/install. I have put "immed" in the setting:
>>>
>>> RestartAfterCodeChange
>>>
>>> Even though that seems like it shouldn't be necessary.
>>>
>>> Shouldn't it kill the current process after downloading/installing if
>>> "ForceRestartAfterCodeChange" is set?
>>>
>>> On Tue, Aug 17, 2010 at 1:46 PM, Dan Hulme <[email protected]> wrote:
>>>> So the "restart" command implies that the process has already been
>>>> killed? I was assuming "restart" had to also stop the current
>>>> process.
>>>>
>>>> On Tue, Aug 17, 2010 at 12:05 PM, Fritz Borgstedt <[email protected]> wrote:
>>>>> For Users of ASSP <[email protected]> schreibt:
>>>>>>
>>>>>> Another nice feature for daemontools would be a way to tell assp that
>>>>>> the
>>>>>> "autorestart" command is just to exit. Since daemontools will
>>>>>> automatically
>>>>>> restart assp, that's all that would be needed for a restart.
>>>>>> Currently I am
>>>>>> using:
>>>>>>
>>>>>> /bin/kill `cat /daemon/assp/root/pid
>>>>>
>>>>> "cd ." would do it.
>>>>>
>>>>>
>>>>>
-------------------------------------------------------------------------->>>>>
-
>>>>> ---
>>>>> This SF.net email is sponsored by
>>>>>
>>>>> Make an app they can't live without
>>>>> Enter the BlackBerry Developer Challenge
>>>>> http://p.sf.net/sfu/RIM-dev2dev
>>>>> _______________________________________________
>>>>> Assp-user mailing list
>>>>> [email protected]
>>>>> https://lists.sourceforge.net/lists/listinfo/assp-user
>>>>>
>>>>
>>>
>>
>>
----------------------------------------------------------------------------->>
-
>> This SF.net email is sponsored by
>>
>> Make an app they can't live without
>> Enter the BlackBerry Developer Challenge
>> http://p.sf.net/sfu/RIM-dev2dev
>> _______________________________________________
>> Assp-user mailing list
>> [email protected]
>> https://lists.sourceforge.net/lists/listinfo/assp-user
>
>
> Important - This email and any attachments may be confidential. If received in
> error, please contact us and delete all copies. Before opening or using
> attachments check them for viruses and defects. Regardless of any loss, damage
> or consequence, whether caused by the negligence of the sender or not,
> resulting directly or indirectly from the use of any attached files our
> liability is limited to resupplying any affected attachments. Any
> representations or opinions expressed are those of the individual sender, and
> not necessarily those of the Department of Education and Early Childhood
> Development.
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by
>
> Make an app they can't live without
> Enter the BlackBerry Developer Challenge
> http://p.sf.net/sfu/RIM-dev2dev
> _______________________________________________
> Assp-user mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/assp-user
Important - This email and any attachments may be confidential. If received in
error, please contact us and delete all copies. Before opening or using
attachments check them for viruses and defects. Regardless of any loss, damage
or consequence, whether caused by the negligence of the sender or not,
resulting directly or indirectly from the use of any attached files our
liability is limited to resupplying any affected attachments. Any
representations or opinions expressed are those of the individual sender, and
not necessarily those of the Department of Education and Early Childhood
Development.
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Assp-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/assp-user
