If MercuryE is working, I suspect the ASSP logs will show the outgoing mail is bypassing ASSP.  That's not necessarily a big problem.

Your logs showed ASSP was on the same machine as Mercury - that's a setup I'm familiar with, and MercuryE will only forward through ASSP is you force all mta DNS queries to localhost and use another relay beyond ASSP.

The best place to understand more about ASSP is on its mailing list or via the wiki/forum at www.asspsmtp.org .  There is a diagram if you follow the link to 'configuration'.

Hi everybody,

I have just replaced my old mailserver with a Mercury/32 installation. While all normal components seems to be working fine, I cannot get the mailing list feature to work. I have created mailing lists, but the mail is not distributed to users that are not local. In the SMTP window, I see the mail being sent to all non-local users, but it never arrives. Can anybody imagine what might be the problem here? Is it anything about the mailing list setup, or rather about the connection settings?

Best regards,
Stefan.

A few questions to start with: Are you using MercuryE or MercuryC for external delivery? What does the log for that module say? Can you send other emails to non-local recipients?

/Rolf 

Hi Rolf,

I'm using MercuryC because I relay to my assp spam filter, which then sends the mail onwards. I can send mail... Wait a minute, I could send mail earlier today, but it seems I've screwed around with the settings long enough so I can no longer send mail to non-local receipients. So - before I screw up even more, I send you some logs. Before I do so - my local domains are: <deleted to prevent spam>. My internal server name is Braga (192.168.22.250), external: <deleted to prevent spam>. I have the following entries in the core module local host configuration:

<deleted to prevent spam>

Syslog:
<deleted to prevent spam>

SMTP log:
<deleted to prevent spam>

SMTP session log:
<deleted to prevent spam>

This is what the syslog said earlier when I tried to send to a mailing list:
<deleted to prevent spam>

Thanks a lot for your help!

 Stefan.

OK... Relevant domain records (mx, ptr) for hitziger.at look good. There should be brackets around the local IP (mail   [192.168.22.250]), but that will presumably not make any difference for external delivery. The MercuryC log seems to indicate that messages were in fact received by the assp program, so you may need to check assp logs to find out what happened there.

/Rolf 

[quote user="spalan"]I'm using MercuryC because I relay to my assp spam filter, which then sends the mail onwards.[/quote]

How are you relaying outward through ASSP?  Since it is only a proxy, you need to use the relay port and relay host sections, and point to another smarthost.

As Rolf says, check the ASSP logs.

Okay people, I changed everything. I initially used MercuryC because I could not get MercuryE to send through assp. Everything except that worked fine, so I decided to switch back to MercuryE so my mails would at least get out. And voilá - now MercuryE also seems to send through assp, so it seems my problems are *all* solved, all of a sudden.

So first off - thanks a lot for your help and your time in this matter. Secondly - I'd like to understand this whole thing better. Can somebody explain to me how assp manages to get in between the Mercury SMTP server and the outside world, so it registers mails we send for its whitelist?