> Ok, so you then add the "domain" that is used for the mailing
> list to the sendmail.cw file or it's equivalent (domains I
> accept mail for).
>
> Would the secondary/third servers then then try to deliver
> it locally? That is where I get confused :-)
Yes. The sendmail.cw file specifies
> Does anyone on the list know of an RFC or, better yet, an "official"
> algorithm to use for the creation of a message's Message-ID: header value?
> I'm gating web forums to Mailman lists and need to generate Message-IDs for
> messages created via the web interface. I need to insert the ID in
On Feb 28, Clark E. Morgan wrote:
> foo: "|/home/mailman/mail/demime.pl - |/home/mailman/mail/wrapper post foo"
>
>- Transcript of session follows -
> sh: cannot use | in command
> 554 "|/home/mailman/mail/demime.pl - |/home/mailman/mail/wrapper post
> shaka"... Service unavailable
>
> I ran into some problems a while back where the Web server didn't have
> the Python crypt module installed, but the mail server did. The upshot
> was that Mailman used crypt() to create passwords on the mail server,
> but then couldn't authenticate against them on the Web server. :)
Actuall
> When I get my email that the list has been created, this is the password
> it shows me.
>
> But, when I go to the admin page and try to login using that password (I
> cut/paste from Emacs to Netscape it so I know it's right), I always get
> "Authentication failed".
>
> I have to log in with th
> When people subscribe, using the web, and mailman sendt the mail with
> the secret to prove your identity, it sends it without any Message-Id
> line. I process mails using SMTP to my local qmail installation (so
> SMTP to localhost) and qmail does not add any Message-Id either.
If qmail doesn't
> I've got a user on one of my lists who's subscribed himself with the email
> address with a form of "myname@home"@isp.co.uk.
>
> Of course, this address is completely undeliverable, and every mail out to
> the list bounces. So I'd like to remove this guy. But I can't figure out
> how!
It *i
> Unless the vacation program quotes back the message it is reponding
> to, it is difficult for Mailman to distinguish between a vacation
> loop and am active poster. That said, implementing something like
> Formail's MsgID cache for Mailman, except instead of cacheing
> MessageIDs cacheing MD5's
> Always wanted to have a mailing-list handler that could optionally use
> PGP :)
>
> * So that users subscribed could (optionally) send in their public PGP
> key, and have all emails delivered to them from then on encoded.
>
> * Ask the server for its public key so mails could be sent to the li
> We are using your script on our live lists with great success.
> I'm sure many lists will find this useful and I'm hoping to see it
> in one of the future Mailman releases as a built-in feature. A
> 'confirmed unsubscription' similar to this but with a 'pending
> unsubscriptions' db and random n
10 matches
Mail list logo