[quote user="Greenman"]
[quote user="Sebby"]
So if I want on your list, I'd do:
To: maiser@dontspamthis.apsarchaeology.co.uk
X-SpamThisInstead: feedme@yamta.org (shameless!)
Subject: whatever
Body (3 lines including a blank):
subscribe external
exit
Make sure your messages really are complete 2822 messages when delivered to maiser. Use the Send Message option from Mercury and it should work. Mail submitted without headers, a blank line and commands in body aren't going to work. There has to be at least a readable plaintext portion; common for most mailers, even the webmail ones.
[/quote]
When I sent the (correct) command locally the body of the email contained
SUBSCRIBE external
and nothing else. Watching the core module shows mail from greenman@apsarchaeology.co.uk being delivered to maiser, and then maiser will respond with the error. Also, I thought that command processing would stop when a blank line was encountered. You mention a send message option in Mercury - I don't understand what you mean here. I've looked through the options for the mailing list but cannot find it.
[/quote]
Adding "exit" is just a sure way to avoid confusion (for instance, no signature will get in the way). It isn't strictly necessary; as you say, a blank line will do. Make sure there's at least one before the end of message, just in case Mercury reads an incomplete line (some mailers don't finish with a blank line for some obscure reason).
Look on the File menu of Mercury for the "Send Mail Message" option. It's described in the help system; it's on the index as something like "Sending mail messages from within Mercury".
[quote user="Greenman"]
[quote user="Sebby"]
Tip: don't forget the HTTP server, MercuryB. It has limited, but useful, mailing list support.
Cheers,
Sabahattin
[/quote]
We thought about this, but because we do not host our domain, we setup an A Record to point mail.apsarchaeology.co.uk to our IP address. This was to stop 550 verification errors when sending mail as apsarchaeology.co.uk.
[/quote]
Sorry, not quite sure how that works ... Verification probes (of the does-sender-exist type done by Exim) call the authoritative MXs to do the probing. That would mean your antispam service, which is your MX for the primary domain (Message Labs). The mail hostname presumably isn't used on the net at all except by that service and when your relaying outbound on your own box. Since you won't use addresses like somebody@mail.apsarchaeology.co.uk, I'd guess we aren't actually talking about the same thing. Can you recall the particular kind of verification?
[quote user="Greenman"]
If I type http://ipaddress or http://mail.aps... then the username and password prompt for the router will appear, which is actually very convenient. Any attempt to add /mlss to this results in a 404 error. My colleague was saying that when he was testing Mercury32 he managed to move the interface to another port, but cannot remember how this was done.
[/quote]
Of course, changing port is your only option - either of the router or of MercuryB. You'll need two distinct ports; whichever you use for MercuryB would get forwarded to the server. That port can be configured in the MercuryB dialog if I recall. You'll then have to update your HTTP URLs to include :portnumber after the hostname (EG http://mail.aps...:8080/blah).
Good luck!
Cheers,
Sabahattin
<P>[quote user="Greenman"]</P>
<P>[quote user="Sebby"] </P>
<P>So if I want on your list, I'd do:</P>
<P mce_keep="true">&nbsp;</P>
<P>To: <A href="mailto:maiser@dontspamthis.apsarchaeology.co.uk" mce_href="mailto:maiser@dontspamthis.apsarchaeology.co.uk">maiser@dontspamthis.apsarchaeology.co.uk</A></P>
<P>X-SpamThisInstead: <A href="mailto:feedme@yamta.org" mce_href="mailto:feedme@yamta.org">feedme@yamta.org</A> (shameless!)</P>
<P>Subject: whatever</P>
<P mce_keep="true">&nbsp;</P>
<P>Body (3 lines including a blank):</P>
<P>subscribe external</P>
<P>exit</P>
<P mce_keep="true">&nbsp;</P>
<P>Make sure your messages really are complete 2822 messages when delivered to maiser.&nbsp; Use the Send Message option from Mercury and it should work.&nbsp; Mail submitted without headers, a blank line and commands in body aren't going to work.&nbsp; There has to be at least a readable plaintext portion; common for most mailers, even the webmail ones.</P>
<P mce_keep="true">[/quote]</P>
<P mce_keep="true">&nbsp;</P>
<P mce_keep="true">When I sent the (correct)&nbsp;command locally the body of the email contained</P>
<P mce_keep="true">SUBSCRIBE external</P>
<P mce_keep="true">and nothing else. Watching the core module shows mail from greenman@apsarchaeology.co.uk being delivered to maiser, and then maiser will&nbsp;respond with the error. Also, I thought that command processing would stop when a blank line was encountered.&nbsp;You mention a send message option in Mercury - I don't understand what you mean here. I've looked through the options for the mailing list but cannot find it.</P>
<P mce_keep="true">[/quote]</P>
<P mce_keep="true">&nbsp;</P>
<P mce_keep="true">Adding "exit" is just a sure way to avoid confusion (for instance, no signature will get in the way).&nbsp; It isn't strictly necessary; as you say, a blank line will do.&nbsp; Make sure there's at least one before the end of message, just in case Mercury reads an incomplete line (some mailers don't finish with a&nbsp;blank line for some obscure reason).</P>
<P mce_keep="true">&nbsp;</P>
<P mce_keep="true">Look on the File menu of Mercury for the "Send Mail Message" option.&nbsp; It's described in the help system; it's on the index as something like "Sending mail messages from within Mercury".</P>
<P mce_keep="true">&nbsp;</P>
<P>[quote user="Greenman"]</P>
<P mce_keep="true">&nbsp;[quote user="Sebby"] </P>
<P>Tip: don't forget the HTTP server, MercuryB.&nbsp; It has limited, but useful, mailing list support.</P>
<P mce_keep="true">&nbsp;</P>
<P>Cheers,</P>
<P>Sabahattin</P>
<P mce_keep="true">[/quote]</P>
<P mce_keep="true">&nbsp;</P>
<P mce_keep="true">We thought about this, but because we do not host our domain, we setup an&nbsp;A Record to point&nbsp;mail.apsarchaeology.co.uk to our IP address. This was to stop 550 verification errors when sending mail as apsarchaeology.co.uk.</P>
<P mce_keep="true">[/quote]</P>
<P mce_keep="true">&nbsp;</P>
<P mce_keep="true">Sorry, not quite sure how that works ...&nbsp; Verification probes (of the does-sender-exist type done by Exim) call the authoritative MXs to do the probing.&nbsp; That would mean your antispam service, which is your MX for the primary domain (Message Labs).&nbsp; The mail hostname presumably isn't used on the net at all except by that service and when your relaying outbound on your own box.&nbsp; Since you won't use addresses like <A href="mailto:somebody@mail.apsarchaeology.co.uk">somebody@mail.apsarchaeology.co.uk</A>, I'd guess we aren't actually talking about the same thing.&nbsp; Can you recall the particular kind of verification?</P>
<P mce_keep="true">&nbsp;</P>
<P>[quote user="Greenman"]</P>
<P mce_keep="true">&nbsp;If I type http://ipaddress or http://mail.aps... then the username and password prompt for the router will appear, which is actually very convenient. Any attempt to add /mlss to this results in a 404 error. My colleague was saying that when he was testing Mercury32 he managed to move the interface to another port, but cannot remember how this was done.</P>
<P mce_keep="true">[/quote]</P>
<P mce_keep="true">&nbsp;</P>
<P mce_keep="true">Of course, changing port is your only option - either of the router or&nbsp;of MercuryB.&nbsp; You'll need two distinct ports; whichever you use for MercuryB would get forwarded to the server.&nbsp; That port can be configured in the MercuryB dialog if I recall.&nbsp; You'll then have to update your HTTP URLs to include :portnumber after the hostname (EG <A href="http://mail.aps...:8080/blah">http://mail.aps...:8080/blah</A>).</P>
<P mce_keep="true">&nbsp;</P>
<P mce_keep="true">Good luck!</P>
<P mce_keep="true">&nbsp;</P>
<P mce_keep="true">&nbsp;Cheers,</P>
<P mce_keep="true">Sabahattin</P>
<P mce_keep="true">&nbsp;</P>
